Hi,
I have SG Create installed on both my remote (work) desktop where I VPN in and also on my home laptop.
When I look at a shot on SG Create on my remote desktop, it opens the shot at frame-1 and says the shot has 1148 frames which is all correct. (attached image CorrectFirstFrame_RemoteDesktop.jpg).
But when I review the same shot on SG Create on any computer outside of studio, it shows a Slate instead of frame-1 while the last frame is still 1148. Essentially, in this scenario, SG Create is missing frame-1.
It seems like one of your sessions is showing you the content of the result of the Shotgun transcoder and the other one show you the result of the path_to_frame field of the version.
I recommend you to read this post to have a better understanding of what’s happening.
Hi Kerby,
Thank you for the reply.
I have a new problem where the version doesn’t show up in SG Create any more even though the status is set to Pending Review, and I am the Reviewer! For some reason it just disappeared from my Reviews.
Btw, I had to remove previous images because of confidentiality material. In the attached image, I have blurred out the content.
In order to appear in the “My Reviews / Pending Review” tab, (on top of having the Version status set to “Pending Review” as you mentioned it is already) the status of the Task associated to the Version needs to be part of the “Upcoming” or “Active” status group, as defined in the Shotgun-Create manage apps settings.
I wanted to piggyback on this that the latest version of Shotgun create seems to ignore the “movie_has_slate” field value and play the slate frame.
Is there a way to make it not do that just like the overlay player?
Unfortunately Shotgun-Create is currently not honouring the “movie_has_slate” field and therefore will not skip the slate frame. There is currently no workaround.
(bump)
I assume @Michel_Eid is no longer on the support team now, so can someone else at SG (@DavidMason , @Jordan.Giboney ?) confirm if this bug will be resolved any time soon?
Have made a note on an internal ticket about this, there did seem to be a workaround for the one they are tracking, if the “first_frame” value is populated it may work? Can you confirm at all? Apologies as I no longer work with the support team either.
Failing that I hope that @desruie may have insight into this in lieu of @Michel_Eid
