Copy link to clipboard
Copied
I'm experiencing some difficulties. My premier pro auto saves which is totally normal, but now its creating new files any time I save manually as well. (Named save1, save2 etc.)
Now when I save manually the program closes my timeline and deletes it. (which I cannot re-find)
Then when it loads after going blank my timeline file name is from a previous save and then project name is the file I'm working on.. Does this make any sense?
I also just did the newest update and that seems to make it crash even more.
The is an image of 3 files that are all containing the same thing. Why is it doing this??
Copy link to clipboard
Copied
I am having the same problem. I build a timeline and then I manually save it and when I close the program after that, Premiere asks me if I want to save it and before I can click anything in response, my timeline goes blank, all my work disappears. Then, if I click "save" in the box or "cancel," either way, my work is still gone and I can only get a portion of it by opening up the last auto-save.
Copy link to clipboard
Copied
What I do is reopen the file that you were working on and then if the timeline is missing I then click on the last clip I added to the timeline (In the library) . It should bring up all your work again in the timeline bar
Copy link to clipboard
Copied
Thank you for the tip. I will try that.
Copy link to clipboard
Copied
This happened to me too. In the media browser look for the file called 1-1 ( may be called something different but it's the largest file in the list). Double-click that file and the timeline re-fills.
Copy link to clipboard
Copied
Thanks for the fix as this was killing me! I recreated 2x project timelines timelines before I found this fix!
I experienced this same issue twice with the latest build of Premiere Pro CC v12.0 on 10th February, 2018
The problem arose for me on 2x occasions when doing a manual 'Save As'. The file appeared to save on both occasions, without issue, but once done, the timeline is cleared.
I don't know how this bug slipped through testing on a major release...perhaps Adobe consider it a 'feature' 😉
Cheers,
Jim