BUG: Modify Clip Timecode for current frame not working correctly in any version past 13.1 and above
Modify clip - Timecode
Modifying the clip timecode for the current frame is being applied to the start of the clip and not the current frame. Had to go back to version 13.0.3 for this to work correctly. Its an absolute necessity for us since we do multicam shoots on dslrs with a digital slate and input the timecode on the clips in post before editing.
David Maddox commented
Same problem here. My workaround, which is not ideal because you have to Modify Timecode twice for each clip, but it's better than nothing:
1. Go to the frame where you want to change timecode.
2. Modify Timecode from "Beginning of File" (since that's the only option) to the timecode for the current frame.
3. Step back one frame, mark an out point, go to the beginning of the clip, mark an in point.
4. Select Modify Timecode again, type minus and whatever the in/out duration is. (So if the in/out duration was 3:10, type in -3.10)
Deverge Admin commented
This is still not working on 22.2.0 M1 or intel. Very frustrating! Adobe, please provide an update. This is core NLE functionality. How can this be broken for so long?
206063528 Ryan commented
Currently unable to set timecode to current frame. The tick box for that option isn't available to click, even though it is there in the window. The only thing I can do is zero at the first frame. This does not help at all when trying to sync multiple cams.
Jack Bellomo commented
when is this going to get fixed?
Jim Perry commented
This is happening to me as well. I am doing a tutorial, and it will not modify the timecode like shown in the tutorial. version 22.0.0, (2021)
Mike Abbott commented
This feature still seems to be broken in 15.1.0
If you want PrPro to be considered a professional level product, you need to fix fundamental professional level features like this.
Tim Dawson commented
Still having this problem in 2021, with version 14.9. Fix on the way? Or workaround suggestions?
Chris Linke commented
I really need this to work, too. I edit a lot of two-camera shoots where the timecode isn't slaved. I have to mark the clapper and then modify the timecode of one clip to match the other. I have to do it three times to get it to stick, but next time open the project, it's gone and I have to do it all over again. Obviously, this wastes a great deal of time.
Robert Combs commented
I'm suffering from this bug too! What exactly does "under investigation" mean? Today is December 15th, 2019. Do you guys really intend on listening to users? I still can't even sort sequences by their creation date (I can't imagine that's a terribly difficult thing to implement). Every time I research a problem I see proposed solutions and Feature Requests that date back for years. How big is your development team? I'm starting to get the impression it's not very large. Production schedules are very demanding. It takes time to write feature requests, please show this community that it's worth our effort.
John S commented
Still broken in v14.0 ... does no one use timecode for their work?
ahmet erdal commented
I have tried version 13.0.3 but it doesnt work. I cant select curret frame.
Trent Happel commented
Thank you for this report! This has been reproduced and is under investigation.
I did notice that if you open Modify > Timecode a second time, the Timecode value is retained, so if you select Current Frame and click OK button, the Current frame is correctly updated to the Timecode value. I know this is not ideal, but might be a possible workaround until this issue can be addressed.