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

[Francis-Crossman]

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 will roll the fix out to Public Beta as soon as we can and will get the fix into an official release ASAP after that.  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

[michaelm11605974]

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.

[Francis-Crossman]

@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]

Hi,

I have not updated to 23.4 but unsure if the remote editor has done that who passed on the project. Premiere did not ask me to update the project file when I opened it.

Either way I think you need to clarify your post and is appears to suggest opening in 23.3 fixes the issues, which it does not.

If as your saying 23.4 does the damage then only new projects creators make going back to 23.3 will be unaffected as long as they dont update to 23.4

[Stan Jones]

Michael,

My understanding of @Francis-Crossman's post is that once a project is relinked in 23.4 and saved, "the damage is done and you can't fix it by going back to 23.3."

I understood the workaround to be AVOIDING the relinking and not saving.

23.4 is the same project file version as 23.3, so you won't get a prompt to update the file.

I would consider going back to the remote editor to see if they have a backup copy of the file before they did any relinking in 23.4. One user's workaround was to hook up the original disks to avoid relinking. (He was moving the project to an external disk.)

Stan

[Josiah29145786p5qg]

BETTER WORKAROUND: Put the media back where it was before it needed relinked, and then open from your auto saves. Everything goes back to normal.

[Francis-Crossman]

Fair point @Josiah29145786p5qg , putting the media back in the original location is ideal, but there are plenty of situations where this is not possible.

[Francis-Crossman]

This issue has been fixed in Beta as of version 23.6.0 build 02. 

[Clay5FC4]

This is a massive problem that has put me in an impossible bind.

[Clay5FC4]

Is that update vailable now?

[Francis-Crossman]

@Clay5FC4 Yes, the update to public beta is available to download now.