omoandr hareem marsten

0 views
Skip to first unread message

Do Kieu

unread,
Aug 2, 2024, 10:03:23 PM8/2/24
to coicontucor

So when I was editing, I accidentally deleted half of my video and I didn't know so my project Autosaved and couldn't undo it to get the video files back. I was hoping you can open previous versions of your adobe premiere pro and go back to your project before 1-2 autosaves

There is an auto save folder that contains the auto saves. Pick one of them and see if the deleted video reappears. If you know the time that you actually deleted the footage you can narrow the auto save down more reliably. Then once you have it back, resave the file but give it a new name so you don't get confused.

This thread is super old and not useful anymore. There is an auto-saved folder now that is stored locally. You can find it in the working folder of your project. The auto-save folder has all the recent versions that were previously auto-saved. Hope this helps.

That's if you set it up that way. The location can be changed or set in the default location which I believe is the Documents folder. Look under FILE\Project Settings\Scratch Disks....

I was editing footage and I either didn't save it right or I just can't find it. However, the project still exists on my Adobe Premiere account. Is it possible to find the autosaves in Premiere instead of in the computer files?

You'll have to look at the autosave folder in the project dialog as you've done, and then navigate there in file explorer. Are you on Windows or Mac? I suggest you copy the autosave file to the same folder as your project is in before you open it.

Here's what happened. I was launching to Premiere Pro and I picked a video that I want to use for slow motion. In the time interpolation, I picked optical flow because it makes your video smooth. I started to render it, and then was done. I saved my project for tomorrow, but when I went back in I saw it has restarted previously to the beginning. This is terrible.

Ok. I opened a new project and imported the old (project saved from previous version). All of my files loaded into the project panel but nothing in the timeline. I went into the project panel files and found the sequence I had used for my project. It was a MVI_xxxx file (will be different for you) which will show it as a sequence if you hover over it. WITHOUT dragging it to the timeline, right click on it and select open in timeline. All edits reappeared.

I have a similar problem where I open my 2018 Premiere project file into the 2019 one and while I can see the video on my timeline, the audio has no waveform and thus I cannot hear it. I've tried every solution available in the forum regarding "how to fix audio" or "the waveform doesn't show" but nothing seems to work.

So I came to the conclusion that this is a compatibility issue within Premiere Pro CC 2018 and 2019 after trying to load the original files (the videos before I've edited them) into a totally new 2018 Project file and the video files would play normally being able to hear the audio...

I cleaned all my media cache files both from premiere (Edit > Preferences > Media Cache > Delete Unused) and from the actual file where there where saved on my pc (Find the location from going to Edit > Preferences > Media Cache and under Media Cache Files you can see the Location path). This was actually so easy to do and solved my problem straight away! Who would have thought! I saved a copy of the Media Cache folders before deleting their content on my desktop just to make sure if anything went wrong I would just copy what is needed back. I would recommend people to do the same and maybe delete after you make sure your projects work just fine!

I created new project, dragged and dropped the older project in the newly created one. I've Selected the sequence and double clicked on it. The entire sequence is the imported to the timeline, with all video files. That fixed.

My team has been working out of a Production workflow with a large number of organized and individual projects in it. We have been working inside of v15.xx and we decided to update to v22.0 when that released to be able to use some of the new features. When trying to open any project in the production in the new version of premiere we get this message:

"The projects in this production were saved from a previous version of Premiere and must be converted. A Copy of the production will be created for the conversions. The original production will not be modified."

When we choose to convert a window with "preparing for upgrade" appears with a bar and we have yet to have anything successfully happen (Premiere hangs and crashes quickly here) and a very small fraction of the projects are converted and there is no new production for the new version of Premiere to open..

Has there been issues with converting productions to the new version or is there a workaround possibly?

Thank you

I've never been able to successfully update a production. I've tried it in multiple facilities on both Mac and PC. I've tried it over the course of years with multiple different versions of Premiere without success. Importing the projects individually into a new production doesn't work either because everything just matches back to the old production. This is extremely frustrating and we need a solution to this. I'm currently dead in the water on a huge project.

I've used Productions for my one-person shop. All my projects are in that Production, organized by type of job, client etc within the folder structure used in Productions. And I make a new one every year that is built with the new major release cycle, but is based from the previous one. And never had an issue, but then my yearly work might easily be a smaller total asset list than your project here.

I know this is super old, but I thought I would post it in case anyone has issues migrating from v23 to v24. After troubleshooting for hours I figured out that I had to open each project in the previous version v23 and then perform the migration. Hope this helps!

Thank you for the quick response.

Unfortunately that was something we tried in one of our attempts of doing something different to see what would happen. New production created in v22.0, full AP folder structure copied over (all other assets are in other folders), and while the projects appear in the new Production tab, an "opening project" window pops up briefly, then no project is opened. Same for every project opened either in the regular folder structure outside of Premiere and also inside the production panel inside of Premiere. No dice there unless there was something I've missed or misunderstood in that transfer process.

Updating a Production is listed as a straightforward task. I've done it on my own and didn't have any trouble, to be fair. You can find info on how to update a Production in the doc's index at the back. I would say the only thing that can go wrong is if editors sharing the files have a project file open. Make sure all projects are closed. All editors should choose File > Close All Projects. Make sure everyone is also on the same version of the software, as well.

I figured it SHOULD be a straightforward task, so I'm definitely tryint to gather as much information as possible to figure it out. Worst case I can take the time to create a new production entirely and import and convert a few hundred projects individually. I have the time to do it, but of course would rather not.

Consulted the supplementary PDF also, thank you for the link. Had everyone close out of premiere and all projects. I went through the production tab and made sure that ALL projects were closed out of and also found a handful of prlock files still around from projects that weren't open and haven't been touched. Got rid of all of those. Attempted again as the only editor to have premiere open on the team's network and had the same crash happen and had only a portion of the projects placed into a new folder.

Did more digging and found that one of our editors didn't follow directions we set early on and was placing video and other assets in folders inside the AP folder structure and not outside that folder structure in asset folders we set up. Could that be where it's hanging up during conversion??

THANK YOU for the help guys, I really appreciate the attention to this.

One thing I do follow ... the documentation says to not put your assets in the same folders as your Production is built in. That a parallel folder structure is safer somehow. And so I do that mostly ... on the same drive, I have my Production, and I can see the organizational folder structure of it in the file manager app of Windows.

c01484d022
Reply all
Reply to author
Forward
0 new messages