Skip to main content
Francis-Crossman17221443
Community Manager
Community 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
  • 45539 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

165 replies

Francis-Crossman17221443
Community Manager
Community Manager
May 24, 2023

@michaelm11605974 did you ever open this project in 23.4?  If you open in 23.4 and save, the damage is done and you can't fix it by going back to 23.3.

michaelm11605974
Known Participant
May 24, 2023

I'm using 23.3, and I'm seeing this issue. 23.3 does not solve this.

 

See attached screen shot 23.3.0 - Audio waveforms are identical for each audio edit.

 

SilviaLozzaVideos
Participating Frequently
May 24, 2023
I'm passing an edit to another editor.
When he opens it, the sequence is messed up, the speed ramps are no more there and the edit is all jumbled.
What we tried : relinking on his side, consolidating (the consolidated sequence opened incorrectly also on my computer), "save as" (worked on my side but not sure it will on his, as it's a copy of the original sequence that didn't work on his side.), consolidate and tanscode to Prores (worked on my side, didn't work on his side).
When opening the consolidated version on my side, I see exactly the same thing he sees on his side when opening the original (correct for me) sequence.
I tried making all the footage offline from the "working" project, and then relinking it from another folder (the consolidated one since it was already copied in a new location), and it changed the sequence before my eyes!!!
We run the same version of premiere (23.4.0 build 56).
We are sharing the whole folder/assets/projects through Dropbox, downloading them and working from our own individual hard drives. 
The other editor has the rushes, and sent them to me on dropbox, so we're both working on the same assets.
No "interpret footage" has been used, no plugins or external luts. 
We can't move forward with the edit without a fix. 
Inspiring
May 24, 2023

This is a known issue at this point. The devs are hopefully working on it.

Please check this thread for a quick workaround until the bug is resolved. And please upvote the bug report (top left corner) so it gets more traction.

 

In short: Export as XML > Send the XMLs to the editors > Import XMLs, that should fix the issue for now.

SilviaLozzaVideos
Participating Frequently
May 24, 2023

Thank you, I couldn't find the original post (I'm coming from the Premiere Editors facebook page where this has been discussed yesterday in depth). Fingers crossed for a fix

Participant
May 5, 2023

Edited an interview - had to jigsaw a lot of ums and uhs and make a fluid track.

 

Everything is fine and dandy. Render is looking good for a rough.

 

Do a little project cleanup - so I have to relink a single audio file - this file is the main cut track for the main interview. So in my timeline its cut many times over the video.

 

Relinking the source audio, makes every instance of the cut clip play from the beginning - not where its been cut.

 

E.g: If the clip begins with the words 'What the hell is happening' - every cut of the edit is saying 'What the hell is happening'.

 

What have I done wrong, anybody experience this?

Participant
June 5, 2023

I'm having the exact same issue - haven't figured out a fix yet.

Participant
April 11, 2023

Hi I want to ask something

 

I find something weird that happened in Premiere Pro and only happen when i work with 2 different PCs.

Let say PC A and PC B.

 

I tried to edit a video in PC A, because i shot audio and video from different source i do a sync process first by align the video and audio, and it works good

So i continue to cut and clip process and other basic stuff

 

Then when i want to do color grading, i move this project to my other PC B, open it there, and just to find out all my clipped video and audio are out of sync.

 

So i tried open it in my PC A where i edit this file in first place, and everything WORKS FINE, then check back again to my color grading PC B, and in OUT OF SYNC again, 

 

I have been desperate on what is going on, maybe you guys have some insight on what to do?

Thank you

Participant
April 11, 2023

I am sorry forgot to add another information

 

I also realized, when i open in PC A audio source let say started on 1st second, but when i open in PC B it started on 2nd second

 

I didnt do anything, it just happened when i open in PC B