I’m curious to know if any of you guys have had a chance to try out Draft yet, since we haven’t really gotten any feedback from it so far. For those who are interested in trying it out, but haven’t gotten a Draft beta license yet (it’s separate from the Deadline one!), let us know and we’ll hook you up
If you’ve been waiting patiently for the Mac/Linux versions, those should be along fairly shortly, we just have to do some more internal testing and tune-ups first.
Couple things. First, the import path should be fixed in the next iteration of the Draft plugin; for whatever reason, setting the Startup directory to be the Draft folder works on my machine but not elsewhere >_<. So we’re going to add a Draft path setting in the event plugin (similar to executable paths in other plugins), defaulting to the usual locations.
Second, for testing purposes, it might be more useful to try out some basic stuff in the python interpreter first; that’ll allow you to go “line by line” and see what might be causing issues. It’s also probably faster than modifying the script and re-submitting to Deadline every time you want to try something different
Third, the error you posted in your latest post ("[IMGUTILS @ 000000000021EB90] Picture size 0x0 is invalid") only occurs for me if I have width/height = 0 when creating the Encoder; can you double-check to make sure those values are non-zero (maybe by doing a print of the two variables before calling the VideoEncoder constructor)?
As for the Shotgun stuff, I’ll have to look into that error message you’re getting (just tested and it worked for me ). And yeah, the sample scripts I’ve posted expect ‘username’ and a couple other params to be passed to them. Some of them are only submitted if you have Shotgun data by default, but you can always specify them in the “Additional args” text box (e.g., you could put ‘username=“Jon Gaudet”’ in there). The ‘username’, ‘entity’, and ‘version’ arguments are pretty much just for specifying text that the Template could overlay on top of the frames (at least, in the sample templates; you could conceivably do other stuff with it I guess).
Cheers,
Jon
EDIT: Looks like you squeaked another post in while I was typing this out . Most of it still applies though!
Just as an additional note, I can see that the ParseCommandLine stuff in the DraftParamParser helper script we include might be a bit unintuitive. Maybe I’ll look into simplifying it a bit.
It should work… Can you post the values of the arguments (kbitrate, codec, etc) you are using to create the VideoEncoder, so I can try to replicate?
As for forcing 32bit, you can do it outside of Deadline just by starting a 32-bit python interpreter, then importing the 32-bit Draft library. To switch it inside of Deadline, you’d have to modify the Draft plugin to always start up the 32-bit python interpreter, instead of switching it based on the system.
Try importing the Python module with “import Draft” (instead of “from Draft import *”), and specify “Draft.Image” instead of just “Image”. Hopefully that should fix it
Yeah, Python’s a bit weird in that “import Draft” and “from Draft import *” are not quite equivalent (thoughsometimes it looks like they are). Among other things, “import Draft” makes you use the module name before static functions and stuff (hence Draft.Image vs just Image); but I find “from … import …” to behave a bit unexpectedly sometimes…
). And yeah, the sample scripts I’ve posted expect ‘username’ and a couple other params to be passed to them. Some of them are only submitted if you have Shotgun data by default, but you can always specify them in the “Additional args” text box (e.g., you could put ‘username=“Jon Gaudet”’ in there). The ‘username’, ‘entity’, and ‘version’ arguments are pretty much just for specifying text that the Template could overlay on top of the frames (at least, in the sample templates; you could conceivably do other stuff with it I guess).
but like I said I get: