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 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 Download Premiere Pro beta version 23.6.0 build 02 or later Open in beta, reconnect the media, and ensure the sequence looks correct. You may choose to just work in Beta –or– save and open in 23.4 Workaround #3 – XML Export XML (File > Export > Final Cut Pro XML) from the original system that has properly connected media. 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 Open Creative Cloud Desktop app Click on All Apps Find Premiere Pro From the three dots on the right, choose “Other versions” Choose 23.3

Francis-Crossman17221443

Community Manager

Answered

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

Forum|Forum|2 years ago
April 11, 2023
165 replies
45551 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

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

Download Premiere Pro beta version 23.6.0 build 02 or later
Open in beta, reconnect the media, and ensure the sequence looks correct.
You may choose to just work in Beta –or– save and open in 23.4

Workaround #3 – XML

Export XML (File > Export > Final Cut Pro XML) from the original system that has properly connected media.
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

Open Creative Cloud Desktop app
Click on All Apps
Find Premiere Pro
From the three dots on the right, choose “Other versions”
Choose 23.3

Correct answer Ann Bens

Known issue: Text-Based Editing - clips reset to f... - Adobe Support Community - 13814912

Show previous replies

Stan Jones

Community Expert

@John30219240o8y7,

Good questions. My understanding is that an Autosave from before corruption should not be a problem. But I do not know if a bad project that is auto-saved will have bad autosaves. Backup any autosaves before you open them. Although I think that there should be no problem as long as you don't save them. I would look at autosaves from before version 23.4. Did you have version 23.4 installed when this project was in use.

This was a bug with an identifiable cause that was fixed. It is not being reported by many users. And some of the users reporting it now are experiencing the old bug - they're using a file that was previously relinked and saved.

There's always the odd corrupt file.

As you are doing, I would try to understand whether it may have been previously corrupted. And if you're convinced it is not, I would file a new bug report with full details. For example, "I closed it last week, and it was working, I opened it up today and it's messed up." When you closed it, what version of PR was that? And when you opened it, same version?

I don't see a description of your symptoms that point to this bug. Were the assets that have bad in points transcribed?

Stan

J

John30219240o8y7

Participant

And that's under the assumption that one of my other workers saved the file when I was out of office. Because when I saw this error, I was sure not to save it in my project.

J

John30219240o8y7

Participant

Yes, I understand that, but why would opening the original file and saving it affect any of the past Autosaves? they're separate files, aren't they? Because the way it stands now, I have 100's of autosave files, from many hours, even days before this error occurred, yet when I open those autosave, they are also all reset. Why is a file that hasn't been opened since before the error occurred also corrupt? IDK. I'd open more autosaves to keep checking, but after 10+ files going back days, I assume they're all messed up.

MyerPj

Community Expert

Keep in mind, the fix is so it doesn't happen anymore. Once a project was rearranged, if it was saved in that state, then that's the way the project is now. <<I want to have a few untouched good files in case this gets fixed.>> Have as many as you like, just make copies of them if you have a good one. Put them on multiple drives -- I have my AutoSaves an a different drive. So, the fix being in, means it doesn't happen anymore. But the projects with that error that are saved are not going to be set back to what they were.

J

John30219240o8y7

Participant

To my knowledge, no changes happened to the computer itself. I did not update any software until I ran into this issue. I tried opening it in v23.3, v23.6, v22.6.4, and I downgraded the project and tried it on v15.4.5. It also seems to have affected all of the most recent autosaves (or the four most recent files, I want to have a few untouched good files in case this gets fixed.). According to my co-workers, the hard drive was not taken out of my computer, although I do know that someone else found this error when I was out of the office, and there are a solid 5 days where I can't be positive it wasn't taken out of the computer or anything.

J

John V Knowles

Community Expert

What changed on your system between then and now?

-------------------------------------------------------------------------JVK | Editor/Designer/Software Instructor. Pr, Ae, Ch, Ps, Ai, Id

J

John30219240o8y7

Participant

Issue is NOT FIXED. This project-breaking error is quite awful. It's already awful when you lose a day's worth of work because of a bug; it's another thing to corrupt a file like this, and lose weeks' worth of work. None of these suggestions have worked for me. I am on a Mac Retina 5K 2017, MacOS Monterey, and I ran into this error on PremierePro version 23.6; downgrading to 23.3 did not work, nor did exporting an XML. To my knowledge, the project files and media clips have never moved from their original spot, nor ever needed to be relinked. Truly, I closed it last week, and it was working, I opened it up today and it's messed up. Any help would be greatly appreciated.

E

Ethan Copage

Participant

Pr - 23.5

OS - Ventura V 13.4

More than likely brought froward as this project was handed over from a freelancer. It works perfectly fine on my office Mac, but the issue is on my home Mac. Both are running the same Pr versions.