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
  • 45940 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

Randy Warren
Known Participant
June 16, 2023

Crazy workaround. Found & downloaded the Beta on PC - didn't work.

Installed 23.3 on PC - didn't work. Installed on the 23.3 on Mac and it worked.

Moving that same project to PC/23.3- became unsynched again. 

Went back to Mac/23.3, exported XML, imported into PC/23.3 and it worked.

Insane. 

Randy Warren
Known Participant
June 16, 2023

Please advise where to locate the download for public beta 23.6 build 02.

I don't see an option in the Creative Cloud desktop app.

edit58989569
Inspiring
June 16, 2023

What were you able to do? I had to trick the computer and move everything back to its original drive. Only thing that has worked. 

edit58989569
Inspiring
June 16, 2023

I wasn't even using text-based editing. I just moved a project to a new drive, and the SAME disaster happened. 

edit58989569
Inspiring
June 16, 2023

NONE OF THESE SOLUTIONS WORKED. What do we do? 

Participant
June 16, 2023

sorry it's not fixed. infact you need to open an autosave version that hasn't touched 23.4. so really you end up loosing work. now.. ask me if i opened autosave versions when this problem first appeared. baking in the error into all my autosaves.... THIS IS A MASSIVE PROBLEM. and a MASSIVE let down for a full time editor. Can adobe explain this issue to my boss? 

Participant
June 16, 2023

I'm so very done with Adobe. I mean this is disasterous and there still is no fix...  

 

[profanity removed by moderator]

Participating Frequently
June 16, 2023

I found out while installing beta on Windows, but it doesn't support gtx980.

MyerPj
Community Expert
Community Expert
June 15, 2023

Had you saved the project with all the scrambled timecodes? It doesn't undo that. Try an autosave version if that is the case.

edit58989569
Inspiring
June 15, 2023

So then, what do you do? I tried beta, and it didn't solve the issue.