SOMETIMES… if I set the start frame on all the segments in my edit (to 1001), and then match out the media to the library, all, or some of the start frames reset themselves to the original, TC based start frame (1535440 - or something mad).
The fact that this bug only happens sometimes and not always is very confusing. Yesterday I did this on one edit and everything landed in the library with 1001 start frames, today nothing keeps the start frame I set. On other pojects I’ve had some keep the 1001 start frame and other clips revert (in the same match out).
It makes using start frames unreliable and unusable.
Is everybody else seeing this same behaviour? (I’m on 2025.2.0.2 Linux)
The setting at project setup only determines your batch start frame though. Imported clips come in with start frames based on their timecode until changed manually.
Matching out reverts to the frame number of the source clip. If you exported the shot to the server with a frame number starting 1001 and imported it then you’d fix it. As far as I can gather the new way makes it more able to fit into pipeline automation.
If matching out isn’t the way then we need another way to extract a clip from a timeline and keep the start frame as set. Otherwise what is the point in being able to change it at all?
You have to right click the source timeline and set the frame number if you don’t export/write out and import. It’s a definite change to old habits. I was not content when I first discovered it.