We’ve just been looking into using your Shotgun integration and I’m not sure the filtering is working. The project dropdown is populated with everything we’ve ever had on Shotgun, including archived projects. And when I click through to an Entity (which seems to be OK, although may also not be filtering for status) I get no tasks in the dropdown list. Any thoughts on what might be wrong or how to debug this? I’ve attached a screengrab of the submission window from Houdini to show what I mean but it doesn’t seem to be limited to this application.
They are in the number of different states from in progress to in review. This also wouldn’t resolve the projects issue where it’s showing all the archived projects as well as the active ones.
Yeah I’ve been trying it out, I have quite a lot of tasks assigned to me at the moment so I was hoping the advanced method worked similarly to the submission options in RV which allow a bit more control when submitting. I just don’t think the filtering is working.
So, I guess the big question is do we need to fix filtering when using the advanced workflow? I’m feeling that answer is “yes”, and I should pass it along to the dev team.
We’re not a huge studio and currently I’m working on an 18 month project, as usual I’m assigned to about 50 open tasks across various parts of the project on assets/shots/animation etc. I also inevitable end up having to pick up other peoples tasks when there’s an issue. If I’m submitting I find it’s much easier to be able to specify the project, entity and task manual rather than have it picked up from Shotgun automatically for me. It may be that we need to be smarter on updating our tasks statuses so that the simple method works better but I always find it useful to be able to navigate through and pick up the task I want.
We’re continuing to test this with the non advanced mode. It seems pretty good so far, there are a couple of issues we’ve come across so far:
One of the users has got a persistent error coming up:
Not sure quite what the error is. Or whether it’s picking up from one of his non shot tasks…
Controlling the sticky settings on the gui. We’d like to enforce using quick draft, creating a film strip and define the output settings etc. Is it possible to control all these settings?
I’m not sure the film strip works if the output is a movie.
I think someone mentioned it in a separate post but picking up the frame rate automatically from the output would be very useful!
The integration Script in the Monitor doesn’t include the Quick Draft functionality and if I try to use the Draft script I can’t use the Shotgun submission with Quick Draft! It would be good to have the same system within the monitor as you do in the individual apps.
It’s pretty close to what we would want but I’ll keep you posted on anything else we discover!
Just based on the “sg_episode doesn’t exist” error, it’s complaining there isn’t an episode to tie the shot to. Is there something different about their workflow? I’m not really an expert with our Shotgun integration, but I’d start there and we can do a deeper dive if running the same steps as others comes up with the same issue.
Sticky settings aren’t built-in at the moment, and 8.1 has completely overhauled that system in ways I haven’t dug into yet (mainly the SG/FT/NIM and Draft code has been factored out into pop-up dialogs). You can always play with the Python code, but I don’t believe it’ll be sticky just yet.
I’m not sure on this one, but I’ll see if I can have Charles take a look here. He’s got more SG experience than I do.
What would the best way to grab the frame rate? I guess from the QuickDraft settings?
Agreed that integration should match. I know we’ve brought this up with the dev team before, so I’ll send a message to the head of integration to see if that’s already been addressed in 8.1 or if we need to put that on the roadmap.
Yeah, never hesitate to throw things our way. I’m a bit concerned that these topics are going to get a bit jumbled, into sub-discussions but we’ll see where this goes. Thanks for reporting 'em, I always appreciate it.
The call doesn’t look like a shotgun one, more like your internal code. The tasks itself doesn’t have an episode but the shot definitely does.
Sounds interesting, it amuses me that 90% of the time we post a request and you’re already working on it for the next release!
This is from After Effects if that helps, it was when I first tried it and I wasn’t using Quick Draft. I’ll be honest and say we’re probably moving away from movies from After Effects anyway.
I’m not sure with the framerate what the best solution is but we’re using it in After Effects so it should be able to get it from the output settings for the comp, I know this could throw up all kinds of issues considering you can submit multiple comps… It’s one of those things that can cause serious confusion later down the line and is easy to miss.
Sounds good. Sometimes we’ll submit multiple jobs from one After Effects, Being able to retrospectively upload these in the same way would be useful.
I look forward to seeing the development, would much rather have you guys develop the integration rather than me, it’s certainly easier for us if there’s a standard method across applications!
I got this same error in Nuke too.
Its indeed when using a Shotgun template without and episode in it (since its just 1 episode).
Overall it indeed seems that movie creation to shotgun doesnt work atm or maybe it breaks when hitting the filmstrip option (I kinda always hit all of the checkboxes )
the sg_episde error is from not having an Episode Entity in the project. I can re-create this error by removing it. To add the episode entity you need to Manage fields and add one (Screen Shot 1).
I don’t think it’s that simple, there is already an episode entity on that project, and an episode assigned to that shot. It may be that he’s assigned to tasks that don’t have that field though and it’s trying to populate the drop down with those tasks? The drop down shows all tasks, ie shots/assets/images etc. Is that what’s triggering the error?
That could be possible. When you created the Episode did you tie it to a Project or Shot entity? I used Project and it seems to cover everything. I’ll see if we can not force the user to specify an episode entity. This should solve the problem completely.
I’ve checked this with our Pipeline Dev and he’s said we have the shotgun episode field (code is sg_sequence) linked to the shot entity, we don’t have one at a project level? I guess if you’re not forcing an episode entity hopefully that will solve it.
Well, we’ve got both the filmstrip as well as the episode logged to be fixed. I’ve marked them both with this thread so we can circle back when they’re closed.
)
