TX for explaining your workflow. So if I understand well, you use the SG “First Frame” field to overwrite the media source time so that any media starts in the timeline UI at 1001 instead of the actual media timecode. Am I understanding well?
SG-Create is honouring the media source range (timecode) in order to deal seamlessly with the multiple representations of the media (file sequence, movie and streaming) of potentially different frame range. This allows to switch between the EXR, MOV and MP4 (streaming) representation and ensure that the annotation falls on the proper frames regardless of the representation used. This also ensures the right frames are in sync when comparing 2 different versions with different source start time.
All this to say that interpreting the “First Frame” SG field to overwrite the media first frame might be difficult in the context of multiple representation support.
I will bring back to the engineering team your workflow around the use of the SG “First Frame” field to see if we can find any workaround.
Note that if you do not set the “First Frame” field in SG, SG-Create will infer the “First Frame” from the media first frame (timecode) metadata. But this would not really help you since, even if now the media will not show any more static frames, the clip will start in SG-Create timeline UI at frame 879618.
RV is honouring the media first frame (timecode) metadata. Loading your clip in RV and you should have the RV timeline starting at frame 879618. The particularity with RV is that it honours “partially” the SG “First Frame” field. If larger than the actual media first frame, it will adjust the window on the media accordingly (as in SG-Create). If smaller, it will not. Instead it simply slips the clip to the specified “First Frame”… which is the behaviour you are looking for if I understand right.
Sorry for the long wordy reply… Hoping that it clarifies a bit the situation.