CC 2020 Timeline Clips Shifts After Moving Project / Relocating / Relinking
We have several users of BRAW Studio experiencing timeline shift after moving their projects between computers. Sometimes it even goes back to the first frame.
If this also happens to you please tell your story in Adobe Community Forums : https://community.adobe.com/t5/premiere-pro/cc-2020-timeline-clips-shifts-after-moving-project-relocating-relinking/m-p/10923880
Happens only with CC 2020 (both 14.0.0 and 14.0.1), both OSX and Windows, all framerate (23.96 fps and 25 fps for example).
Apparently happens with others formats than .braw : https://community.adobe.com/t5/premiere-pro/linking-media-losing-in-and-out-points/td-p/10922669 "I have this problem on every file type I have tried; R3D, BRAW and CRAW"
Attached is a zip with the two .prproj from a user editing with .braw and you can see what's changing inside <MediaFrameRate> and <TimecodeFormat>, also the timecode changes from 01:43:25:03 to 01:43:31:16000
Please investigate and fix this issue it is very annoying and preventing users to edit in good conditions with Premiere Pro it is quite urgent
Update of our relocation panel, update available here https://www.autokroma.com/BRAW_Studio/Download
Bug fix : "Correct 2020 PPro Shift" feature for big projects, it's also more performant and better suited for Mac OSX when files are from different disks
Jan Holthaus commented
ok ****. that's a few dollars working hours. what a bug adobe, thumbs up!
"The correction panel only relocates the footage so that Adobe doesn't relocate itself the footage. Once the shift has happened the panel cannot do anything. Since we're not Adobe we're not sure what the shifts does exactly and if it reversible "
The correction panel only relocates the footage so that Adobe doesn't relocate itself the footage. Once the shift has happened the panel cannot do anything. Since we're not Adobe we're not sure what the shifts does exactly and if it reversible
Jan Holthaus commented
when my project is shifted allready, can i fix it afterwards?
I purchased the autochroma v2. "First move your file, then open your old project in the Panel, then relocate the footage, open the new corrected project." I habe no clue. I did relocate it, but nothing visible happens.
First move your file, then open your old project in the Panel, then relocate the footage, open the new corrected project.
If you open a project with files not at the right place => shifting occurs; So you need to first move the footage, then correct the PrPro project then open the corrected PrPro project where no relocation (hence no shift) will occur
Johnathon Karalis commented
Could you please clarify if you would have to conduct this 'Shift Issue' fix prior to moving the footage (preventative?) or after the the issue has occurred?
I find myself in the position where i have multiple file locations and i am shifting them to a new location. How would i best approach this scenario?
Thanks in advance.
We're glad it worked for you Glen !
Glen Gilespie commented
Antoine Autokromo, the "Shift Issues" tab in the panel worked for me! It took a bit of time, but it corrected two projects for me. What I don't understand is that this issues just came up out of nowhere earlier this week.
Ofentse Mwase you are avoiding the bug by having the right filepath at PrPro startup = no relocation. This solution cannot work for everyone because some really need to relocate their files when moving data and project around
Ofentse Mwase commented
Hi. I figured out the problem. It's Hard Drive Drive letters. So if you working on the project, and the drive you working on is Drive E: , wherever you move your footage to, the drive has to be E: as well. Usually drive letters change if you are using an External Drive, so this will cause this bug. So just change the Drive letter until you get to the one that works. I've had this problem twice and this is how I fixed it on both occasions.
We have a new automatic correction panel to try to relocate your footage and fix your issue in BRAW Studio Panel
Could anyone try it ?
"New Feature, Auto Correct Tool for "PrPro 2020 Relocating Shift Issue" in our Panel :
This issue is happening when files needs to be relocated and others files than .BRAW can be concerned, more info here https://www.autokroma.com/blog/Premiere-Pro-Timeline-Shift-First-Frame-After-Moving-Project-Relinking
We now have a new way to auto-correct your .prproj (Premiere Pro project file) directly, by relocating the files inside (any extension)
This new tool is in the "Shift Issues" tab of the BRAW Studio Panel, you will find there instructions to use it"
Chris Cool commented
Same issue here. I moved a project from my work computer to my home computer and my entire timeline is screwed up. Please fix this Adobe!
If you're suffering from this issue (which is NOT linked to BRAW it can happen to any type of footage apparently) we have a first version of a script to relocate easily your footage of a Premiere Pro project, contact us if you want to test it ! https://www.autokroma.com/contact/
Austin Berry commented
Bruce, has there been any progress on Adobe's side for fixing this? BRAW is such a commonly used format that this absolutely needs to be fixed.
Cynthia Barker commented
I opened up an older auto-saved project file and it wasn't affected!! I'm back in business! With that being said Adobe needs to fix this crippling bug ASAP!
Cynthia Barker commented
I simply renamed the master folder for my project file on Windows 10 and now all 57 of the timelines that I have cut for my online course are screwed up. Every clip is out of sync with my audio. Two weeks' worth of work down the drain.
Overit Media commented
Adobe...this is a plague of an issue...I know you have your little rivalry with blackmagic but the point that this is not yet fixed gives me more favor with blackmagic and less with Adobe...
Please fix this!
Sorry about your lost time Jordan ! Could you tell us what are the formats of your video and what framerates ?
Jordan Spalding commented
This is INSANE, this happened to me a few times and before I had found Antoine's workaround I just swallowed my sadness and started over from scratch. The latest time, I lost a week of work on an edit. Thank god I was feeling frustrated enough to go digging into the internet until I found the solution. Please fix this adobe! It's unfixable on our end, it populates through all your autosaves, it can't be undone or accounted for.
Kyle Gentz commented
THIS NEEDS TO BE FIXED! Yes im yelling because this is stupid.