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

[Francis-Crossman]

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

[Marcos D.2530578685id]

Hi Kevin, 

I guess the footage was shot with something close to a Sony FX6, but I can´t tell 100%

The Apple sistem info is the next one:

Macbook Pro, M1 Pro, 32GB Ram

It´s a weird issue because for me it seems like premiere is interpreting wrong the media somehow, in the next two pictures I´m attaching you can see the Synced Timeline, where everything was perfectly on time, but in the next picture, when I zoom in, you can see Premiere is displacing the clips randomly either right or left.

The weird thing is that even when I try to open like the first back up, it´s all desync, wich results in a strange situation because I worked two weeks ago in this project and everything was on sync and working smoothly. 

Hope you can help me Kevin,

Cheers.

[Marcos D.2530578685id]

Kevin? 😞

[Kevin-Monahan]

Sorry about that, Marcos. You'll have to "@" my handle to get my attention as I am watching dozens of posts at any one time. I'm sorry that I don't have a solution for you but you might try the new version of Premiere Pro (23.3), which should be available for most people by now. If not today, then check the Creative Cloud app tomorrow. Run a test and report back, OK? Hope the advice helps. 

BTW, I do not provide one to one tech support over the forums, I'm more of a moderator type here. You can contact our agents here, though. Ask for the "video queue." 

Hope that helps,

Kevin

[Stefan P]

Hi. On your screenshot I see that you use "mp3" audio. Years ago I face this problem but desync was only couple of frames.

In my case the problem was additional audio-video codec pack that I was install. For example in mp4 or mkv container there is information about audio-video relate sync and if Premiere or plugin not read-understand this there will be desync.

For test:  on PC A convert one mp3 to wav and sync with video file, than open same project on PC B and check if it in sync.

[perfect_multitalent00824]

Did you ever find a solution for this problem?  We are having the same issue at our offices.  We use a shared server between all our edit bays, but when some of them open the same project (with the same footage on the same networked drives with the same drive letters), the audio will be wildly out of sync (by many minutes).  We have confirmed that all of our systems are using the same version of Premiere (23.2.0).  This has caused our production to grind to a full stop.  

[Marcos D.2530578685id]

Hi guys, 

I´m sorry, I tried everything possible and the solution for me was re-editing all the sequences following one of the WIP renders I fortunetly had. 

Maybe you can try to go to an old premiere project back up, export an XML or EDL file and try to import it in another editor like DaVinci.. Maybe you can be lucky.

I can´t believe Adobe is not informing about this issue or giving people solution. 

Hope the best for you guys, I´m sure you will make it.

[George22115708x5xk]

I'm working with another editor on a project using the clip level transcription tools in premeire pro. We're both using Premiere Pro 23.4. He's on Mac OS and I'm on Windows 11. 

Due to the size of the project we generated proxies for everything. All has been working well until we tried to relink to the full resolution media and that's when the problems started.

When trying to relink to the original files the clip's timecode shifts or goes to the first frame of the source clip for all the clips in the timeline. 

I did some digging on Adobe's site and found that it is indeed a bug in version 23.4

Has anyone esle run into this problem? If so, what's been your workaround? I'm hoping it isn't as painful as manually readjusting every clip in the timeline. I've tried the workaround suggest by Adobe (create an xml, revert to previous version of Premiere), but it still isn't working.

[John V Knowles]

https://helpx.adobe.com/premiere-pro/kb/known-issues.html?fbclid=IwAR3dAa2uFLaEgx3krV6UP_9_a-UW0XGX8...

Only current workarounds are to export XMLs when going back and forth or revert to 23.3. Hopefully this is patched soon.

JVK

[George22115708x5xk]

That's what I was afraid of. Hopefully its fixed soon indeed! Does anyond know if its just related to transcriptions at the clip level or as a whole (sequence and clip level)? I have yet to do more testing to see if both methods are affected.

Side note: I would love to know if there are any good resources out there for best practices for air tight proxy workflows. I've done a little bit of digging online, but haven't had much luck in finding any good info on best practices for smooth proxy workflows.

[Ali Jaber]

If I remember right, it's fixed in the Beta version. But if you already saved the project after re linking the clips, then you can't recover that project.

[George22115708x5xk]

Thanks for the suggestion Ali Jaber. I'll update this post if it ends up working. 

[George22115708x5xk]

That did it! So much time and many headaches have been saved. Thank you!

[James5FC9]

I'm flabbergasted this is fixed in the Beta but Adobe seems fine to just slow roll it out with the regular release schedule. This is a critical bug and you’d think they’d push out the fix as soon as they could, but nope for some reason.

[Ali Jaber]

I completely agree, this is a very serious bug and should be fixed ASAP.

[George22115708x5xk]

My guess is they haven't completely ironed out all the kinks for the patch. It worked for me and my media on my machine but who's to say someone else doesn't have success.

[Matthew24027729osum]

I have had this exact problem. Transcription will not work with connected proxy files but if i link to the original files the transcriptions work perfectly. They are extremely sluggish linking to large files on a NAS but that is the only way it works. I hope this is fixed soon. 

[Karen5C82]

Same boat here - relinking full res media after using proxies and ran into this problem. I just tried opening an auto save of my project before the problem cropped up in Premiere Beta (where they've rolled out a fix) and everything linked back up fine. After saving in Beta, I opened it back up in 23.4 and all looks good. Luckily I haven't lost too much work with the auto-save file.

[Daniel27282893fkwo]

PR version 23.3. I finished ediitng a whole 4h course on premiere pro on a mac (i work off SSD drives). I did use the text based editor for some scenes. I was wrapping up some more edits on the last section on my pc (after transferring everything and relinking the footage on my PC). Then i experienced the issue of the audio not matching up with the cuts. 

I found my auto save for when i was on mac (still unlinked) and opened it up on the pr beta and that worked like a treat.
There needs to be a better way to find this forum cos i almost didnt find it and launched my pc out the window.

[ThomasWilliamson]

Oh wow I was going nuts wondering why my footage kept going out of sync. Hopefully this gets resolved soon.

[SilviaLozzaVideos]

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. 

[Sami Succar]

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]

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

[Pelle Asselbergs]

This is a terrible bug. I just ran into it on a massive project. 

[AndricTeng]

how long can we expect a bug fix?

[danield25437812]

1. 23.4.0 (Build 56)

2. Windows 11 Home 22H2 Build 22621.1702

3. Put together a timeline with many cuts and clips. Then in the windows explorer, move the video file used for the project.

4. Expect the media to reconnect correctly, but when Premiere reconnects media automatically, every cut on the timeline reverts to 00:00:00:00, totally ruining the project irrevocably.

This has happened on several projects now. When I finish a timeline and happen to move the files in the file explorer into a different folder, all of my cuts irreperably slip way out of sync. They all start at the beginning of the media file, lose the timecode. It destroys my project. I've attached a photo of what it looks like.