We have a problem with creating quicktimes from EXR sequences.
All colors that are not legal (that´s my theorie at least) look funky. Also the gammy seems to be way off…
Any ideas?
This happens with ProRes and H264.
Thanks,
Timor
Your theory is correct, but that should have been fixed in the last Draft build… Have you updated to the Draft Beta 7 build?
Cheers,
- Jon
yes, we are running 7…
I may have posted the wrong binaries, then. I’ll download the ones on the forum and double check.
Cheers,
- Jon
So I downloaded and tested the latest Draft build posted to the forums, and I’m not getting this issue. Could you double-check that you’re on the latest version by entirely deleting (or renaming to something else temporarily) the Draft folder in the Repository, and replacing it with the latest build in the build forum?
If there’s still an issue after that, I wonder if there’s just an old build of Draft lingering around on the slave machine that’s mucking things up. Add the following line to the Draft script that you’re using:
print "Draft Version: %s" % Draft.LibraryInfo.Version()That should print out the Draft version that’s currently in use. The latest version should be 1.0.0.46224. If it’s anything else, or if that line breaks (complaining that ‘Version’ doesn’t exist or something like that), then it’s grabbing an old version of Draft from somewhere…
If it IS printing out 1.0.0.46224, however, and your output .mov is still wonky, could you upload a copy of that .exr you’re using, along with the settings you use to create the VideoEncoder in Draft?
Cheers,
- Jon
sorry, was too busy and couldn´t find the time to do it…
unfortunately the error still exists, even though i seem to be on the latest version.
attached you´ll find an example EXR and a screenshot, showing the clipping, the slave log and the EXR in RV player.
hope this helps,
timor
DL_draft_error.zip (626 KB)
I also noted another strange thing:
Draft doesn´t enter the shotgun values into our slate anymore (it all states “undefined”) AND it doesn´t upload to shutgun anymore (even though we ticked the checkbox).
It might be sth. we did, but you might want to have a loook at it in case it wasn´t on our end…
Thanks,
Timor
So I finally figured this out. Turns out the overflow on colours is happening during composition, not during video encoding (which is what I had fixed in the latest build). Looks like I’ll have to clamp values before comping for now…
Cheers,
- Jon
cool!
…can you please also look at why the SG data is not transfered to draft anymore (at least that´s what it looks like…) ?
Thanks,
Timor
Could you be more specific as to how you’re submitting the Draft job? Which submitter(s) are you using?
I tested Nuke, AE and directly as a post script from the monitor.
I use the same template as always, so that can´t be it…
Task, Version, Artist is “undefined”
Frames are listed though…
Alrighty, I’ll have a look at this today and see if I can’t pin this down.
Cheers,
- Jon
Hmm, I haven’t been able to replicate this at all over here.
Is the problem happening in the submission forms themselves? That is, when you click the “Use Shotgun Data” button, does the User/Entity/Version show up as “undefined” then? Or is it only in the output of the Draft job that they show up as “undefined” (in the frame annotations for example)? If it’s in the Submitters, can you try changing the Shotgun Task that the job/scene is tied to, just to see if that fixes it?
Did this stop working right after you updated to a new version (of either Draft specifically, or Deadline)? I’m rather confused as to why it would suddenly stop working, since we haven’t changed anything with how Draft interacts with Shotgun data in a while…
Also, any extra details you can think of in addition to this would be awesome!
Cheers,
- Jon