Modifying Timecode in 2023.6

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?

Stan

Hi Stan. I'm also struggling with this issue.

Any idea on when will version 24.4 be available, with this bug solved? 

I don't recall a post saying this was fixed. The bug is present in release 24.2.1. It appears fixed in Beta 24.4.0.14.

Report re 24.2.1 here:

https://community.adobe.com/t5/premiere-pro-beta-discussions/bug-source-clip-start-timecode-can-not-be-changed-anymore-changes-are-not-applied/m-p/14495792#M8927

Stan

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.

Adobe hardly ever says when something will be fixed.

Try the beta.

This still persists in 24.0.3 (Build 2). Do we have an update on when a fix will be released?

System specs:
macOS Ventura 13.3.1(a)
Adobe Premiere Pro 24.0.3 (Build 2)
Macbook Pro 16-inch, 2019
2.4 GHz 8-Core Intel Core i9
64GB 2667 MHz DDR4
AMD Radeon Pro 5600M 8GB
Intel UHD Graphics 630 1536MB

@Stan Jones @daapap @Kim278279257ndf Here is the update the issue will be raised and will be resovle soon.

thank you,

Suraj.

 @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'll keep you all updated as well.

thanks,

Suraj.

@Suraj5EBF and others,

I see a new report of this bug:

https://community.adobe.com/t5/premiere-pro-beta-discussions/bug-source-clip-start-timecode-can-not-be-changed-anymore-changes-are-not-applied/td-p/14142731

I also did a search and see earlier bug reports that are different, but I wonder if they may be related ort share similar issues:

https://community.adobe.com/t5/premiere-pro-discussions/modify-timecode-of-clip-to-start-at-zero-issue/td-p/10705317

https://community.adobe.com/t5/premiere-pro-discussions/bug-have-to-reset-clip-to-original-timecode-twice-for-it-to-stick/td-p/12527553

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

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.