FTrack Event Update Thumbnail

[nope]

Hello,
I’ve found three issues with the FTrack event so far.
The first problem is in [Deadline Repository]/events/FTrack/FTrack.py. In updateThumbnail on line 240, it’s choosing the wrong frame for the thumbnail. I was trying to render 1001-1060, but it thought the first frame was 0001. I was able to fix this by changing thumbFrame = job.FramesList[0] to thumbFrame = job.JobFramesList[0]. But after fixing this, the next error showed up which was at line 249. The error was FTrackError: Invalid file type. The file type was exr. I’m not sure how to deal with this error other than comment out the updateThumbnail call, which isn’t a real solution.
The third issue I’m getting is line 92 in createComponents. Right before it fails it logs: INFO: Creating Component for Deadline output ‘V:\PROJECTS\Erik_Tests_WORK\FA_010\2D\comps\renders\FA_010_test\FA_010_test.%04d.exr [1001-1060]’…
And the error ProtocolError: <ProtocolError for eightvfx.ftrackapp.com//client/: 500 Internal Server Error>. I don’t know how to deal with this one either.

EDIT: I tried again today and the third issue stopped happening, but the first two are still a problem.

1. Deadline Version: 7.0.0.25 R (79978a431)
2. Windows 7
3. ftrack event submitted from Nuke
4. Enable ftrack events. Create a Nuke script that writes an exr sequence. Open the Deadline submitter in Nuke. Do all the ftrack connecting and setup, then submit. Wait for the render to finish, then it should start an ftrack event which will error out.

[jgaudet]

Hey there,

Good catch on the Frames List bug, I guess I was always starting on single-digit frames while testing, so it happened to work. I’ll get that fixed.

The error you were getting when uploading the thumbnail is just because ftrack doesn’t support using .exr’s as thumbnails. We definitely plan on adding code here to convert them to PNGs or something automatically (using Draft) before uploading them. I’ll probably try to get to this shortly after Siggraph

Either way though, the upload failing shouldn’t affect the rest of the process (aside from printing out the error message). Is it actually preventing the components from getting created for you?

As for the final error you were getting, I’m not sure what’s going on with that one… Which version of ftrack are you using? It’s possible that it’s slightly different and not-quite-compatible with the API we’re shipping. You might have to download the python API from your ftrack server, and replace the one we’re shipping in ‘events/ftrack/API’. I guess since it’s no longer happening it may have also just been a one-time thing. If it keeps coming up again, definitely let us know

[nope]

Yes, the asset still gets uploaded, but I thought I should bring it up since exr sequences are pretty standard.
I think the last issue isn’t actually a problem since it hasn’t happened anymore. Sorry about that. Don’t know what happened.