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

[lucag98282318]

Hi community! 

I have noticed this bug with this workflow.

Import and transcaribe my interview.

Send the transcription to the producer and get it cut.

Remove from my transcriptions the parts not wanted and build my timeline.

Send the project and original footage to the editor.

When they relink the footage the cuts on the timeline are corretc, but the sections of clips selected are all over the place.

You can see attached the timeline before and after re-linking the 2 clips.

Am I doing something wrong?

[Stan Jones]

See this post for the problem and the workarounds.

https://community.adobe.com/t5/premiere-pro-bugs/known-issue-text-based-editing-clips-reset-to-first...

Once the project file is relinked and saved, it will not work. You must work from a backup copy. The file you have that you sent them should work.

Stan

[lucag98282318]

Thanks a lot.

I did a search but had no idea how to identify the issue so couldn't find any discussion.

I thought it was a Beta bug but witht he full version out still has it so I kept doing my XML export as explained in the post.

Thanks for your answer

[Pelle Asselbergs]

The beta or downgrade to 23.3 will work. But only with a 'not infected' auto save for the project.

I work in a Premiere Production workflow, with over 500 hours of footage and 100+ hours of archive footage. This is spread over 20+ projects and countless sequences. It's unacceptable when such a bug creeps in and damages your project and thus the overall production on tilt. A swift permanent solution is needed.

[Khue5FBC]

Hi, I have a large project with about a dozen sequences, and everything has been working perfectly until I opened the project today. All of the extracted audio clips (that I edited in Audition) have reset to the beginning of the audio file, making them completely out of sync with their video clips.

Here's an example of the issue: Audio Issue.mp4 (I also attached it)

In this clip, I used the same extracted audio .wav file and linked it to the video, and edited it. Each audio clip was supposed to be a different part of the same .wav file, but now all of them start at the beginning of the .wav file. This issue applies to every sequence that uses extracted audio that I edited in Audition, but none of the clips that use the original video's audio. 

The only thing that has changed since the last time I opened the project is that I moved the project folder and renamed it, but Premiere had no trouble re-linking everything, and I actually tried moving everything back to the original location (and quitting without saving) and it still had the same issue, even on an older version of the prproj file.

I use Premiere Pro version 23.4 (as of now the latest version) on macOS Ventura 13.3.1, using an Apple M1 Max.

[Musicpham]

I have the same issue. I'm also using PPro 23.4. I checked it on my surface pro (Win11) and on my macbook pro with intel chip on macOS Ventura 13.2.1.

I have multiple projects with this now and also need help urgently.

Thanks and best regards

Musicpham

[MyerPj]

Hopefully you didnt save a project in that state. There is a problem  with v23.4, check out this thread.

https://community.adobe.com/t5/premiere-pro-bugs/known-issue-text-based-editing-clips-reset-to-first...

[RyanSalyer123]

I'm not sure how else to phrase this... I had an interview edited and completed on a spinning hard drive. It was really, really slow to edit and export so I got an M2 SSD and moved the whole project folder to the new drive, verified it moved, and deleted the old one. The client wanted a change to the interview, so I opened the file, it recognized the new location for the media... and everything is broken. I still have all of the clips laid out and cut up, but when I play it it is just repeating the same section of the file over and over. I've cut up one big interview clip and used b-roll to splice different segments of the interveiw together, but when it goes to the next 'splice' it just repeats the very beginning of the original file. 

What happened? I cleared the cache and nothing happened. I have never had this happen to me before. Beyond that, some of the clips have completely different color correction now.

[RobShultz]

The proper way to transfer the project is  with Project Manager. If it's not too late I'd try again while working with Project Manager, while working with the previous project, and see if you have better results.

[RyanSalyer123]

Yeah unfortunately it is too late. I’ve moved project folders hundreds of times like this and never ran into this I'm just baffled. This is the first even hearing of project manager

[James5FC9]

Are you using 23.4? If so it's proably be realted to this bug https://community.adobe.com/t5/premiere-pro-bugs/known-issue-text-based-editing-clips-reset-to-first...

I also move my projects like you do and have never had a problem either so I'm thinking it was that relink bug. 

[Stan Jones]

@RyanSalyer123,

As @James5FC9 links to below, it is almost certainly this bug in 23.4.0:

https://community.adobe.com/t5/premiere-pro-bugs/known-issue-text-based-editing-clips-reset-to-first...

(Your post has been moved to that thread.)

This is fixed in the Beta. A fix will probably be in the next release update, but we don't know when that will be. Hopefully soon, but in the meantime, you need to keep working.

Once you relinked and saved the project, that project file was messed up. You cannot use that file anymore.

To use workaround #1, copy the files from the SSD back to the original location (keep them on the SSD also, and see below).

Make a copy of your most recent autosave/backup file from before the relink. In this type of situation, I always keep an extra backup copy of everything. Open it on the old drive. If it works, just suffer through the slow work!

Variation on #1: redesignate the drive letters and make sure the SSD uses the same path as the original. That may not be possible if it is your C drive. But if it is, try opening the backup project there. This might work. If so, you can finish the project on the new drive.

If neither of those work, see workarounds #2, 3, and 4.

Stan

[jschwartz567]

Lost an entire day to this re-syncing a bunch of social ads I was cutting that were on a tight deadline. Didn't have time to troubleshoot this far. This isn't even a bug. This ruins your entire timeline. Insane.

[Invitado]

通常通りカット編集をして保存して閉じた後、再作業のためにプロジェクトを開くとカットポイントから素材の動画が全て頭出しになります。音声は問題なく、ビデオのみ。

保存する前に作業している段階ではそのような異常はないのですが、一度終了してまた開くとこのような状態になっていることがあります。ちなみにオートセーブしているものも全て同じ状態なので、せっかく編集したものが使い物になりません。

現状、ビデオ以外の編集はちゃんと保持されているので未編集の素材に入れ替えてテロップに合わせるなどして再度カット編集しています。

このバグは大変困るので早急に対応をお願いしたいです。応急的な対策でもいいので提示していただければと思います。よろしくお願いいたします。

[R Neil Haugen]

I believe this is on the current "known issues" list ... and yea, it's a pain for those it hits.

[edit58989569]

So then, what do you do? I tried beta, and it didn't solve the issue. 

[MyerPj]

Had you saved the project with all the scrambled timecodes? It doesn't undo that. Try an autosave version if that is the case.

[CH30515061nsam]

I found out while installing beta on Windows, but it doesn't support gtx980.

[kimj13227143]

I'm so very done with Adobe. I mean this is disasterous and there still is no fix...  

[profanity removed by moderator]

[k_pop]

sorry it's not fixed. infact you need to open an autosave version that hasn't touched 23.4. so really you end up loosing work. now.. ask me if i opened autosave versions when this problem first appeared. baking in the error into all my autosaves.... THIS IS A MASSIVE PROBLEM. and a MASSIVE let down for a full time editor. Can adobe explain this issue to my boss? 

[edit58989569]

NONE OF THESE SOLUTIONS WORKED. What do we do? 

[edit58989569]

I wasn't even using text-based editing. I just moved a project to a new drive, and the SAME disaster happened. 

[edit58989569]

What were you able to do? I had to trick the computer and move everything back to its original drive. Only thing that has worked. 

[Randy Warren]

Please advise where to locate the download for public beta 23.6 build 02.

I don't see an option in the Creative Cloud desktop app.

[Randy Warren]

Crazy workaround. Found & downloaded the Beta on PC - didn't work.

Installed 23.3 on PC - didn't work. Installed on the 23.3 on Mac and it worked.

Moving that same project to PC/23.3- became unsynched again. 

Went back to Mac/23.3, exported XML, imported into PC/23.3 and it worked.

Insane.