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

Participating Frequently
August 7, 2023

This is NOT fixed. I just lost a VERY urgent work thanks to this issue. I would recommend to anyone using this method to simply stop using it.

Inspiring
July 27, 2023

Adobe should really have created some sort of tool to delete transcription or whatever offending project data out of project files. They moved too slowly on this one and caused a lot of problems and will continue to cause a lot of problems if anyone happens to be using 23.4 

Inspiring
July 21, 2023

@alexy21 

 

My "workaround" only works if you are able to put your media back to its original file path and haven't overwritten the project yet. So if you can get an auto-save and get your media back to the original file path then my steps can work. 

 

My problem specficially came about because I wanted to move a proejct, but saw that the re-link curse still existed even in 23.5 if at any point the project was saved in 23.4 with transcription. So I was able to quickly *not save* keep the media in the same place, re-transcribe, and then save again and reopen at a new location without the curse. 

 

Not sure if that makes sense my case was pretty specific. 

alexy21
Participant
July 21, 2023

@Scott.C. I'm mostly following you but I think I'm getting tripped up somewhere. When I follow your steps, after re-transcribing I am noticing that the transcription is actually in line with the video preview... however, the audio is still messed up. Any thoughts?

Participant
July 11, 2023

@Fergus H @Francis-Crossman17221443  I'm having this issue still in 23.5 across multiple different edit suites. On wavs, if that makes any difference. Rolling back to 23.3 hasnt stopped the issue from occuring. I've also had it happen in 23.0. I managed a workaround of "replace footage" rather than "link media" which worked twice, then stopped working altogether. Seems like potluck. Holding up an urgent edit, any advice or additional light you could shed would be much appreciated. Thanks. 

Participant
July 3, 2023

So what if you have already saved the project? Any work around?

Participant
June 30, 2023

We also got hurt by this issue. Adobe should be more proactive in alerting people about this. I'd rather be told via email, text or AI that my version of software has a critical error then have to struggle through it and find the solve on my own.  As we are moving enterprise post from Avid to adobe incidents like this are hard to forget. 

Inspiring
June 29, 2023

OK, I think I found a workaround that can remove the "23.4 curse" from your file. Since it's rooted in the text-based editing function of the project, and there is no way to remove the transcript once it's there, you have to tell premiere to re-transcribe all the clips and then  the offending project data is overwritten in your project file. 

 

Steps:

 

  1.  Open a cursed project in 23.5 (One where the media is still in its original file path, so this won't work if you've already been forced to re-link )  
  2. Select media in bins (if a multi-camera, you will have to select your raw audio / video files)
  3. Select Re-Transcribe. (This will take awhile if a big project, but worth not having to start over) 
  4.  Move project
  5. Re-link and the curse is lifted, your media is not reset to the in point. 

 

 

Once I did this and unlinked and then re-linked the media I didn't have any drift! Hope this can help others. I tested it a couple of times and I think I'm finally out of the weeds. 

 

Adobe I'll be awaiting my  check in the mail. 

Inspiring
June 28, 2023

I would do this but XML doesn't work for multi-cameras.... I guess I could flatten everything but pretty annoying. 

Inspiring
June 28, 2023

I tried opening autosave with correct timecode, saving in 23.3, and then wholesale importing the project into a new project in 23.5 and then moving the folder and everything is still dropping out of sync on the re-link. Not sure what workaround is supposed to work but coming up with nothing. How are we supposed to archive projects from the last few months?