Also am I going crazy or does the height number for the Resize function do absolutely nothing when you read in an image.
Yeah, non-uniform scale seems to be a no-go. It seems to use the height for aspects <= 1.0 and width for aspect ratios >1.0.
Feature Request?
Will have to look into this a bit. Could you try going to your Draft Install folder and opening up permissions on type.xml? I wonder if we just shipped the file with the wrong permissions…
Fixed! Good catch 
You’re right, it seems to always preserve the aspect ratio. Feature request noted!
Cheers,
I tried every possible variation on the xml file. No dice.
I deleted it and created a new one with the contents. Seemed to work.
I’ve discovered another minor annoyance. It does positioning of text different depending on the text has any lower case hanging letters such as “j,g,p” etc.
So if I attempt to align my text based on SouthWestGravity the text will bump up based on the contents. Is there a way to over-ride that behavior so that my text is always horiztonally on the same line. I thought about using a North gravity but then if I use all lower case I’ll be back in the same position. (Although perhaps admittedly less frequently except that one of our artists usernames is gpaquin which would then be too low,)
What is the codec flag for h264 quicktime?
Edit: Oh. “RuntimeError: H264 codec soon to be supported!.”
How soon?
Also I need to enable “Fast Start” for streaming? Is that flag in there somewhere?
Cool, I’ll still look into why that might have come up in the first place. Good to hear you got it working though.
I’ll look into if that behaviour can be changed; I’m not sure if I’ll be able to change that, though. A holdover solution might be to prepend a label before the user (e.g. "User: "), so that there’s guaranteed to be an uppercase in there (and then use North gravity, as you mentioned). I understand that might not be desirable, however.
These are both things I’d have to look into; we’re using a third-party library to do our video encoding, and unfortunately I’m not that familiar with its capabilities 
Cheers,
Hmm, I suppose for this instance I can write a little function which does a string search for jgypq and shift the position by pointSize/5 or something up.
But yeah, H264 would be our top priority for feature requests (and the fast streaming header)
By the way, my type.xml stopped working again…
Out of curiosity, are you changing the current working directory (os.chdir) at all? I’ve just discovered that to cause this error. If not, could you try adding the following to your script (right before you make the call to Image.CreateAnnotation()):
import os
print( os.getcwd() )Then let me know what that ends up printing out; if it’s not the Draft folder for whatever reason, that’s probably the issue.
Either way, try creating “.magick” directory in the %USERPROFILE% directory (in windows 7 it’s C:\Users[username]), and stick the type.xml file in there. You might have to create the folder from the command line, since explorer doesn’t seem to let me create folder with a leading period:
mkdir %USERPROFILE%\.magickAnother alternative would be to add an environment variable called MAGICK_CONFIGURE_PATH that specifies the path to the Draft folder. I think this is probably what we’ll do under the hood through Deadline for upcoming releases.
Cheers,
Ok I’ll give that a try the next time it breaks. Recreating the file from scratch worked again. 
Also is there going to be a way to extend what information is universally passed to the Draft templates? So for instance if I want the project name passed or the render job’s source file when available how would I modify that universally so that I don’t have to update the Max, Nuke, Monitor etc plugins?
If it’s information that’s stored in the Job’s properties, you could modify the Draft Event Plugin to append it to the arguments. So, for example, if you wanted to add the Shotgun Project name (which is stored under the job’s ExtraInfo1 property), you could add something like this line:
scriptArgs += 'sgProject="%s" ' % job.ExtraInfo1to the section that’s building up the Draft arguments.
If it’s information that’s not already available on the Event Plugin side of things though, you’ll have to modify the submission scripts as well
Cheers,
hi there, we would like to start on draft too, but i would obviously like to wait till all the bugs that have already been pointed out are fixed (thanks gavin!).
when do you think can we expect a new version (alpha 2?)?
thanks,
timor
I’ve made improvements to the Draft plugin for Deadline, so that the Environment variables will be properly set up; that should hopefully prevent the “type.xml” error, and any “library not found” errors when using Draft through Deadline. That will be in the next Deadline release (which should hopefully be soon).
As for the h264 codec, we’re being limited by the third party library we’re using right now. We’re currently considering alternatives that would allow us to do add that codec to our supported list. Unfortunately, I don’t have an ETA right now for the next release of Draft. We’ll definitely keep you guys posted, though!
Cheers,
Are you updating the command line parser functions as well?
params[‘inFile’][‘value’]
is more awkward than:
params[‘inFile’]
As well as some robustness in missing shotgun info?
Yup, it’s on my laundry list. I just figured I’d mention the stuff that was actively being worked on instead of summarizing the entire thread
Just making sure. 
By the way for anyone that’s curious what I’ve been working on here is an output of our draft template:
Output:
I’m thinking about also making a little XML file for each render folder as well which has all of the slate info in it and zipping up the Nuke file (if it’s a nuke comp).
Tracking_Shot_Thumbnail.zip (2.05 MB)
I have made some changes that will allow you to align text images from generated from different fonts and pt sizes. The result will be available soon, but in the meantime a teaser image! 
Badassery.
Hi Gavin,
loving you slate setup, really nice.
I was wondering one thing: If you use rv player and switch between frames and the .mov (in shotgun), how do you manage to keep both in sync if your .mov has a 25 frames long slate in front?
Thanks, really appreciate your help on this,
Timor
