When i change a clip's timecode to any time (1:30:00 for instance) it always shows up as Media Start 00:00:00:00 in the bin. Not even closing and reopening the program helps, i have to "replace clip" with itself or delete and re-import into the project anew.
Same machine with PPro 2022: Everything (sorry: this ...) works.
Thanks for answering, but that's not what i want to do.
I have a bunch of clips all starting at 00:00:00:00, i want to set them INDIVIDUALLY (Modify -> Timecode) to the recording time i read from the clip's metadata to build a timeline representing the day of the shooting.
And even if this was what i was looking for: It would not explain why it works in 2022 but not in 2023.
Do you want to arrange the clip's start timecode to be in order?
Select "Start Timecode" option from the Timeline Humberger menu, then change the Timecode value to a desired value. If you open the sequence on any monitor or export a clip, the start timecode value will be visible.
No, i don't want to change the start tc of the sequence.
I want to change the start tc of clips. Pick a clip, right click "modify - timecode". enter a new start tc (for example the hour/minute from the recording metadata). Hit enter. Whatever you enter, it will result in "00:00:00:00" in Premiere Pro 2023, while in PPro 2022 the media start tc in the bin will show up with the new tc.
Something sure seems wrong. I only looked at 23.6.
Import a clip. Mine has a starting timecode of 3 minutes and change. This is displayed in the Media Start column. Open the clip in the Source Monitor; it starts at 3 minutes etc.
Right-click, modify, timecode, change to 5 minutes and leave the rest unchanged. "Alternate timecode" is now checked.
Media Start says zero. Open the clip in the Source Monitor it starts at zero. Modify still shows "Alternate timecode" active, but the timecode is zero.
Delete that clip, and then reimport. It shows the alternate timecode in the Media Start, in the Source Monitor, and in the modify dialogue.
Change the Alternate to something else, all is back to zero.
Thank you, @Stan Jones and @daapap for a more thorough explanation of the problem. I too saw a similar situation, in which Media starts to go to zero when the timecode is changed but doesn't update accordingly in Project panel; it only works when deleted and reimport the same media I will check and update if anything, but I have no idea why this is occurring.
Once you used the clips in your project you can not delete them anymore in your project, so do not forget about the option to replace them by themselfs (replace footage)!
Thank you for this wonderful tip, Suraj5EBF Too bad there are so many issues with Modify Timecode, a tool that worked perfectly well in the early years of APP, but for several years in all the updates despite lots of reports on this forum just doesn't get fixed.
I took a look at Beta 24.1.0 Build 48, and the problem is still there. Changing to an alternate timecode via Modify -> Timecode shows the new timecode and Alternate in the change box, but the Project Panel displays the old timecode. If you go back into Modify -> Timecode, "alternate" is checked, but it is the old timecode.
The correct alternate timecode is set and displays correctly if you delete and reimport the asset OR is you use Replace Footage and pick the same asset to import.
@Stan Jones Thank you for the information and you valueable responses, i will take note of it and try to get in touch with the development team to address this problem.
I'm having this same issue. When I try to modify the timecode in a Canon RAW video file I get the error warning that the file is busy and cannot be updated. I was able to change the the timecode on the proxy files created in camera. (But even that took one or 2 tries to get it to stick.) But I couldn't do it for the RAW files. I tried one, where I took the timecode corrected proxy and created a second copy of it in aother bit in the project panel. Then I replaced the footage with the RAW footage and it kept the corrected timecode. But that didn't work with the second file. It's very frustrating.
I'm working in Windows on either of the 2 most recent versions of Premiere Pro. 24.1.0 and 24.0.3
The best I can do with the second RAW file is to get the Modify Timecode dialogue to remember that Alternate Timecode that I give it, but whenever I select the "Alternate Timecode" button and click "OK" it just keeps the original timecode or 00:00:00:00.
Even though the Beta is 24.4.0, the next update is more likely to be 24.3. A poster yesterday referred to having 24.3, but I see nothing about it yet. Perhaps it was a typo. It's hard to tell with the staggered release of updates.
@jstrawn@Kevin-Monahan Do we know if this fix will be in the next update? Is 24.3 rolling out?
While waiting for the new version, I'm using another workaround successfully.
In my case, I need to go back to Original Timecode, changed to Alternate by the editor, before exporting the XML to Resolve.
I simply "make offline" all the clips with Alternate, then "link media" to all of them again and that's it. The Original Timecode is back and translates ok to the XML.
Not for me... Tested with 24.3 and the problem persists. Can't change from Alternate to Original timecode, unless using the above mentioned workaround.
Thanks. Yes, I see that, except I can switch back to Original, but can't get back to the Alternate unless I type in a new one.
My description of the original problem was "Changing to an alternate timecode via Modify -> Timecode shows the new timecode and Alternate in the change box, but the Project Panel displays the old timecode. If you go back into Modify -> Timecode, "alternate" is checked, but it is the old timecode."
That sorta works correctly now, but when I tried to change from Alternate to Original or vice versa it worked once - maybe - but once I got back to Original, I could not get to the Alternate. I could click the Alternate button, and it would show the previously set alternate timecode, but clicking okay did not change it in the Project Panel nor the Source Monitor.
Using replace footage did not get the Alternate to work.
I also tested in Beta 24.4.0.30. (The latest build available is now 34.) Same results.
28
Replies
AdChoices