Skip to main content
Francis-Crossman17221443
Community Manager
Principal Product Manager
April 11, 2023
Answered

FIXED issue: Text-Based Editing - clips reset to first frame after relink in 23.4

  • April 11, 2023
  • 165 replies
  • 45781 views

This issue has been fixed in 23.5 which is now available.  Please update to get the fix.

 

We are aware of an issue in Premiere Pro version 23.4: when transcribed clips in a timeline are taken offline and relinked, clips shift and reset to the first frame. Effects, transitions, and speed changes can also be removed or impacted.  Our engineers understand the problem well, and we are testing fixes internally right now.  We have put a fix into Public Beta and will get the fix into an official release ASAP.  I will update this post with more details as soon as I learn them.

 

If you are experiencing this problem:

If you get the media relinking dialog in 23.4 and you have previously used transcription, close and do not save the project. Make a backup of your project file just to be safe.

 

Workaround #1 – Restore media

  1. Put the media back in its original location so no relinking is required.

* There are many cases where this is not possible; try one of the following:

 

Workaround #2 – Beta

  1. Download Premiere Pro beta version 23.6.0 build 02 or later
  2. Open in beta, reconnect the media, and ensure the sequence looks correct.
  3. You may choose to just work in Beta –or– save and open in 23.4

 

Workaround #3 – XML

  1. Export XML (File > Export > Final Cut Pro XML) from the original system that has properly connected media.
  2. Import the XML into a new project on the new system and reconnect the media

* Please take note – not all aspects of the sequence will be reproduced by the XML

 

Workaround #4 – revert to Premiere Pro 23.3

  1. Open Creative Cloud Desktop app
  2. Click on All Apps
  3. Find Premiere Pro
  4. From the three dots on the right, choose “Other versions”
  5. Choose 23.3
This topic has been closed for replies.

165 replies

Participant
August 22, 2023

This issue is not remotely fixed. I have the same issue over and over again when working on different Macs. I have followed the recommended steps with no success. My music audio track is using the wrong in and out points across a project. Hours of work are lost. It's absolutely unacceptable that the issue is so present. One more reason that our studio is considering moving to Davinci Resolve if this is not fixed asap! 

 

Pr - 23.5

OS - Ventura V 13.4

Community Expert
August 21, 2023

If anyone is still having this issue, it's because you're opening a project that was converted to 23.4. Upgrading to 23.5 or .6 after that will NOT fix the issue once it's occurred; you have to go back and open a project file or autosave that was still in v23.3 or earlier.

-------------------------------------------------------------------------JVK | Editor/Designer/Software Instructor. Pr, Ae, Ch, Ps, Ai, Id
Participant
August 21, 2023

Months later - I am still having this bug. I've just inherited a drive from another editor and the media is incorrectly pointing to the wrong timecodes. I've tried opening it in previous versions. I do not know what to do at this stage... I have a client deadline this evening. Is there a real fix that works?

Participating Frequently
August 18, 2023
I can’t believe this is still happening. Following this since I had issues
and lost weeks of work 2 months ago and downgraded is enraging. Adobe,
figure this out! Completely unacceptable this was dropped on your users.
Participant
August 18, 2023

FYI, THIS ISSUE HAS NOT BEEN FIXED. I am on version 23.6 and it just happened to me on a project I have been working on for the past month. None of the workarounds work for me and I've spent the last 3 hours trouble shooting trying to fix it. I've put about 40 hours into the editing this project so far with 10 hours of interviews and I lost all my editing for those interviews which were cut down from 10 hours to 1.5 hours at the time the bug occurred and it looks like I will have to start all over with my client deadline in 2 weeks. I am furious and exhausted. It is unacceptable that this bug is still in a non-beta version of Premiere. 

Community Expert
August 15, 2023

Make a backup of your project before you upgrade it. Or create a blank project in 23.6 and import your older project into it. That will protect the original and if you encounter problems you can downgrade back to your old version.

-------------------------------------------------------------------------JVK | Editor/Designer/Software Instructor. Pr, Ae, Ch, Ps, Ai, Id
MyerPj
Community Expert
Community Expert
August 15, 2023

Understood. They said it's fixed, so, I think the chances are good. At least it's easy to spot, and close it out right away. Also, the problem when we don't know for sure what version # a person is referencing. They said 23.5 fixed it, and we are on 23.6 currently.

Participating Frequently
August 15, 2023

I'm just wondering when we will know when it's actually safe to update to the newest version. Some people report it's not fixed, but are they correct or not? I'm gunshy now but would someday like to take advantage of the new features. Can anyone confirm beyond doubt that this bug will not re-occur with a project that never touched 23.4?

MyerPj
Community Expert
Community Expert
August 15, 2023

It helps to be so kind as to include the actual version number from the About screen, rather than 'most  recent version'. If you've been thru it before, then you knew to not save the project in that state.

Participant
August 15, 2023

I just had this issue happen again. I'm on the most recent version of Premiere. Please help! I need to get something to my client tomorrow.