Skip to main content
Francis-Crossman17221443
Community Manager
Francis-Crossman17221443Community Manager
Principal Product 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
  • 45944 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
    This topic has been closed for replies.

    165 replies

    Show previous replies
    Randy Warren
    Randy Warren
    Known Participant
    June 20, 2023

    @Stan Jones No, I exported an XML of the original "fixed" projects/sequence. 

    I assume exporting an XML of the damaged one would not work.

    I rolled back to 23.3 on the Mac, where I had first started the project, exported the XML, and was able to import that XML into PC running 23.3.

    S
    Sami Succar
    Inspiring
    June 20, 2023

    If your project is already saved with the "wrong" timeline, downgrading will not help. You need to locate a version of your project before you made the relink, you'll find one in your auto-save folder.

    S
    Sebastian Harnack iMac
    Participating Frequently
    June 20, 2023

    Hi. 

    Can u pls let us know, when this will be fixed? Even downgrading to 23.3 doesnt solve the problem for me and I urgently need to continue edit my project on another machine (with of course other footage destinations). Pls help!

    M
    mattharr0
    Participant
    June 20, 2023

    I booted up my software to find this, but after locating, these clips manually, they started from the beginning, they lost their attached media start code.

    Initially, I thought my issue was in regard to Premier not reading my external drive, as it had not been ejected properly beforehand.  But after enabling full disc access amongst a bunch of other fixes, I still can't fix the issue - I can't contact adobe support either because my software is licensed under my school admin, as part of a major project I need to sort this ASAP. 

     

    Peru Bob
    Community Expert
    Peru BobCommunity Expert
    Community Expert
    June 20, 2023

    This is a known issue.  Use the workarounds here:

    https://community.adobe.com/t5/premiere-pro-bugs/known-issue-text-based-editing-clips-reset-to-first-frame-after-relink-in-23-4/idi-p/13814912

     

     

    davidlarocque
    davidlarocque
    Participant
    June 20, 2023

    Looks like 23.5 just dropped and fixed this? Anyone else confirm? Fixed it on my end.

    edit58989569
    edit58989569
    Inspiring
    June 19, 2023

    Yeah they have known for a while, I could have been saved. 

    S
    Scott.C.
    Inspiring
    June 19, 2023

    I'm vaguely shocked they didn't pull 23.4 after this was discovered. 

      edit58989569
      edit58989569
      Inspiring
      June 19, 2023

      It's pretty bad. 

      E
      EOXDJ
      Participant
      June 19, 2023

      @Francis-Crossman17221443Downgrading doesn't help, IF the project was originally created in 23.4. Even if it is not broken YET. So if I have a file created in 23.4 that is perfectly fine now in it's place, once I move it and try to relink it (it doesn't matter if relink happens with 23.3 and 23.4) it breaks everything.

      Interestingly, files originally created in 22.x and then further processed into 23.4 do NOT seem to have this issue. I can relink them just fine in their new place.

      Stan Jones
      Community Expert
      Stan JonesCommunity Expert
      Community Expert
      June 17, 2023

      Randy, thanks for reporting what worked for you.

       

      My understanding is that once the project is opened in 23.4 and SAVED, it will remain unsynced with any of the workarounds. Were you using a "bad" file and the xml worked? Or was it a file that had no been relinked?

       

      Stan

       

        Show more replies
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices