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
  • 45936 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
June 28, 2023

@Scott.C. this happened to me, but with a different bug where my Premiere would just become unstable and crash in a project created in 23.4 with extensive transcription. Autosaved versions of the project that had been working fine began behaving erratically, EVEN when downgraded to 23.3. I ended up starting the project over from scratch. Wish I had a better fix, but with my experience with 23.4 haunted project you will waste less time that way.

Randy Warren
Known Participant
June 28, 2023

It's important to export an XML of the sequence that has the correct sync, then import that XML in the other location... ON v23.3

Inspiring
June 28, 2023

I'm at a bit of a loss... 

 

I downgraded to 23.3 Everything opened with the correct link, saved the project to a new project file, tried to move the project folder and when I re-opened and re-linked everything drifted again....In 23.3. So it seems if 23.4 has touched your project file its cursed? 

Inspiring
June 28, 2023

@Fergus H @Francis-Crossman17221443  This is still buggy. Not sure if it's limited to Multi-Camera + transcription, but the bug from before seems to persist. See video: 

 

https://youtu.be/t2EP2pRXcuc

 

Steps:

 

1. Open project made in 23.3 (potenitally 23.4 not sure) in 23.5 with correctly linked files including multi-camera sequences. [Old file path]

2. Change the name of the folder where media files and project are kept. 

3. Premiere automatically relinks files

4. Rename folder or force a re-link.

5. Sync of multicamera files now very off, 2nd camera has lost it's original in point. 

 

Result - 2nd camera very out o sync with audio.

Expected result - normal relink without drift as seen in every other version of Premiere. 

 

MyerPj
Community Expert
Community Expert
June 28, 2023

@Scott.C. <<if you happened to save something in 23.4 without knowing about it>>

 

The problem with that, is there is nothing to fix. The saved project from 23.4 is as it is when it comes into 23.5.

So, don't save the project when (if) you see the timeline messed up in 23.4. (Find an AutoSave project if need be)

 

23.4 should just be sticken from the books and pulled as a possible update.

Randy Warren
Known Participant
June 28, 2023

I would strongly advise NOT upgrading to 23.5, even though they say it's fixed.

I was able to find roll back to 23.3, find a previously saved project file in my AutoSave folder that was in sync, and I have no plans to upgrade anytime soon.

Participating Frequently
June 28, 2023

It's shocking how bad Adobe is at delivering a bug free release. Shocking. Does anyone test these things? It took me less than a week to encounter this bug. Not to mention the myriad of other bugs that never get fixed along with the new ones they keep popping up. Maybe stop creating new features if you can't get the basics like relinking correct.

Inspiring
June 28, 2023

This is still a really bad bug if you happened to save something in 23.4 without knowing about it and have to re-link in 23.5. That part isn't really fixed. 

 

 

 

 

Participating Frequently
June 28, 2023

I have found a workaround if V23.5 is not giving you your solution.

My case was that I had to move my project to another harddrive because of coppacity shortage. Let's call the harddrive's HD-1 and HD-2.

So I copied my entire project from HD-1 to HD-2. Note that this project was all fine when on HD-1. But when opening my project on HD-2, there was one file which clips were reset to the start of the file. With V23.5 this was not resolved since syncing was still off (just like with other members here).

Here is my solution:
I opened the project on both HD's within premiere (so 2 projects at once) and I put the timelines above each other. Meaning that I had the good timeline from HD-1 and the flawed timeline from HD-2 next to each other. After that, I manually copied the clips from the HD-1 timeline and pasted them over the timeline of HD-2. Replacing the flawed clips.
I was worried that these clips (that were now on the HD-2 timeline) would have their source-file set to HD-1 and that I needed to re-link them, making this experiment fail. But to my surprise they didn't. Meaning that their source-file changed when being pasted from HD-1 to HD-2 (as long as the same files are on both projects).

I hope I explained this well enough. Of course I do not know how you could do this with two different computers. But maybe you can experiment copying your project to an external harddrive and following the steps above. Hopefully you then do not need to re-link when you get to another computer. 

Good luck

edit58989569
Inspiring
June 26, 2023

Sorry guys, this is still not working in 23.5 I moved a file, and the syncing issue returned.