Relinking Clips After Changing Filepath Moves Clip to Start of the Clip, not the Edit Point

[Bike Guy]

Cutting a video consisting of many clips from interviews. Cutdown sequences copied to create more cutdown sequences. A lot of work. 

Put together a rough and exported it. All is fine at this point. Then, while doing some housecleaning, I changed the name of the project folder without thinking. Later, I went back to the project and realized I needed to relink all the footage. Did so with seemingly no problem.

Now, EVERY single clip in every sequence I created throughout the entire project starts at the beginning of the source video. The sequence shows all the edits as being right, but the material displayed isn't anywhere close.

Never seen this before. Please advise. Thank you!

[Bike Guy]

Correction - Havoc after renaming project FOLDER.

[Kevin-Monahan]

Hi Bike Guy,

I read your message and I can understand what a nasty situation that can create. I have seen a number of cases around the same issue. I will move this discussion into the Bug Reports forum and will let the team now. I hope the devs can address this situation soon. For now, I have heard the workaround is to revert to an earlier version of Premiere Pro. You may want to try that for now. I apologize for this situation.

Thanks,
Kevin

[Bike Guy]

Reverting to the previous version of Premiere solved the issue for me. Thank you for your help!!!!

[Smokey118]

I had the same problem.  After renaming the project folder, every linked clip in the sequence started at the head of the source file.  I tried reverting back to earlier versions of Premiere without luck.  I reset my preferences as well. Nothing.  THEN, while in Premiere Pro 23.2, I renamed the project folder to its original name, relinked the files and everything seams to be normal.  I saved the project, updated PPro to 23.4 and the project opened cleanly. 

[Sami Succar]

This is a known issue at this point, they're working on a fix. There are a few workarounds you can try in the meantime, they're mentioned in the link.

[Fergus H]

Hello, 
This issue is fixed in Premiere Pro v23.5, which will be available the week of June 17. 

Regards,

Fergus