AWS Thinkbox Discussion Forums

BETA 5 - Draft and Shotgun

Here comes my list for the beta 5 - primarily regarding draft (in order of importance to us):

  1. We need to have the template.py file to be sticky! The artists are super annoyed to have to search for the file for every single submit…
    I would also love to have a dropdown list with the last 4 templates being used.

  2. Why is the draft submitter so reduced? It would make sense to have the basic options that for example the QT submitter allows in there, after all, it can do as much (framesize, codec, etc…). Having a template.py only makes sense for special stuff like slates, etc…

  3. We NEED H264 asap. As the .movs get uploaded to shotgun MJPG makes the files unnessary large. And we cannot sent these files to our clients, they would think we are crazy :wink:

  4. We also need draft to create the thumbnails (i wrote this already in another post). This is probably very easy to implement, just wanted to stress the fact that we currently only get big “?” thumbnails because of the EXRs…

  5. We now get a “The shotgun plugin is currently disabled…” message when we submit (out of nuke). Funny thing is, it still works (and it is of course activated in the event plugin options)

Thanks for considering my wishes,

Timor

I thought I had went through all of them and did this… Looks like I missed Nuke :frowning: Are there any other submitters that you found didn’t have sticky Draft settings?

The idea is to handle that within the Template itself. Instead of trying to have options for every situation, since scripts are so flexible, we decided to go the route of expecting you guys to have different templates for different situations. Does that make sense?

We’re aware of the need for H264. We’re just sorting out some licensing stuff at the moment. The goal is to have that sorted out and have h264 into Draft before release.

I’ve already done this; should be in the next release =)

Interesting. Does this happen 100% of the time? Could you zip up and upload a copy of your Shotgun.dlinit file (located at ‘[Repository]/events/Shotgun/Shotgun.dlinit’)? You might want to strip out your Shotgun connection info from it before doing so, though, for security’s sake

Cheers,

  • Jon

I will have to check, we currently only use nuke with SG till the kinks are gone…

I can hear you. It does make sense for us too, but i would think that many companies that are using deadline are not so much intro scripting/python but still want to use draft with it´s basic options. I know that this is what the templates are for, i still think some basic image params are nice to have…

Sweet…

nothing fancy in th shotgun dlinit, it is attached and stripped with the connection info…

Cheers
Timor
Shotgun.dlinit.zip (859 Bytes)

Another thing i just noticed:

You where so nice to answer my request and put a “create shotgon version” in the scripts section, thank you very much, we use it a lot now. I told the artist to check their files for CQ prior to submitting to SG, so that is very handy.
One thing thats missing though is the draft option which is vital for the SG workflow. …and creating a separate draft job is really too much hassle (given the fact that it should have the same interface as in the submitters where this exists already).

Thanks,
Timor

Privacy | Site terms | Cookie preferences