Team Projects - Stuck on "Processing Loaded Assets"

[lukeg84836182]

I was working within a team project yesterday and then the program crashed on me. When going back into Premiere and trying to open the Team Project again, it goes through the first few steps but then gets stuck on "Processing Loaded Assets" and never moves past it. I've tried loaded previous versions and it happens to. I've tried reverting to an older version of Premiere and it doesn't work either. And, I've also tried renaming the Team Projects Local Hub folder. None of this things have resolved the problem. Are there any other things I can try?

[PeterELee]

Sorry to hear you are experiencing this issue. Are you able to open other Team Projects successfully?

If so, has any of your media changed recently or been moved to a different volume? One frequent cause of slow loading is media on a slow volume, especially one mounted over the network. If that's the issue, you may just need to wait longer and see if the Team Project eventually finishes loading.

[lukeg84836182]

Thanks. I was able to load a different Team Project successfully. As for the media, it is housed on an external hard drive but it hasn't moved or changed. It was working fine yesterday then the program crashed and it hasn't been able to successfully load since. I'll try waiting for a while though and see if that's the issue. I think the longest I've let it wait is about 15 minutes (the progress bar hits a point and then doesn't seem to budge so I assumed it wasn't doing anything).

[PeterELee]

Thanks. The progress can stall like that when it's waiting for something that's normally quick, but for some reason is taking a long time, e.g. due to network problems or a slow drive. Or there could be a more persistent problem -- it's impossible to tell just by looking at the progress bar, unfortunately.

Are you or your collaborators able to open the Team Project from another computer?

[lukeg84836182]

Yeah, I let it wait for over two hours now and it hasn't moved at all. I don't know if it's the case but I wonder if one file became corrupted when the program crashed because it kind of seems like it gets stuck on one particular thing. It had worked fine for the past couple months.

I won't be able to try it on another computer until later today but I'll try that out and let you know!

[PeterELee]

Sorry to hear it, but thanks for checking! Have you tried creating a new Team Project from the last shared version? If not, try this:

1. Open a different Team Project (or a standalone .prproj)

2. In the Media Browser, browse to the Team Project that's having this issue (under Creative Cloud\Team Projects Versions).

3. Right-click on the name of the Team Project in the Media Browser, and choose "New Team Project from version..."

You can do the same thing with auto-saves, but then there's more chance of trying to restore an auto-save that has the same problem as the most recent one.

[lukeg84836182]

Okay, so that did work. I was able to create a new Team Project from that saved version. Unfortunately I had a lot of unsaved edits from that crash that would be in the auto-save but I'm assuming that may be a lost cause? At least this gets a working version up and running again. Thanks!

[PeterELee · Accepted solution]

Glad to hear that worked! You can certainly try the same process with your auto-saves. With any luck, you'll be able to go back one step in the auto-save history and be back up and running. It might take a few more iterations to find the most-recent auto-save that works, though.

You mentioned earlier that you tried renaming your Team Projects Local Hub directory. That original directory contains all of your auto-saves, so the first step will be to quit Premiere (and any other Adobe software that uses Team Projects), then change the name of that original directory back to Team Projects Local Hub.

Next, launch Premiere, open a different Team Project or standalone project, and browse to the auto-saves for the problem Team Project (the Auto-Saves tab is next to "Versions" in the Media Browser). You can then scroll to a previous version or use the "previous version" arrow at the bottom of the scrollbar. Once you've selected the auto-save you want to try, right-click on the Team Project name and choose "Make Auto-Save (date and time) the Latest...". The next time you open that Team Project, it will be in the state it was in for that auto-save, while leaving the rest of the auto-save history in place. If that works, you're in business! If not, try going back one step further until you find the most recent auto-save that does not exhibit the problem.

[Walon5FF1]

Actually I just encounter the exact problem. And even I created a new teamproject from the old version, it also got stucked when processing loaded media. So I tried to find the corrupt file. For the past hours, I didn't add or move any new media, so I thought it could be the  media cache files. After I deleted the latest media cache files, the teamproject came back to normal. Thank GOD!

[defaultxx7idsf05mlq]

How do you delete "the latests media cache files"?

[Mikay²]

For anyone who wants to know:

Press ctrl/Command whole Premiere Pro launches. Then you get the options to clear the media cache files. Unfortunately, it didn't work for me.

[izettem72164525]

I'm sitting with the exact same problem... deleting the Cache files not helping... did you find a solution? (I'm not the owner of the Team Project)

[Udo_Pawlik]

Hi,
Which version of PPRO are you using? We released a fix in 23.5 for an issue where users were unable to open certain Team Projects.

Best, Udo 

Udo Pawlik | Sr Software Product Quality Specialist | Adobe | upawlik@adobe.com

[izettem72164525]

I'm on macOS Ventura 13.4 & downgraded to PP 23.3 after we had issues with 23.4 - I do not see a 23.5 version in my Creative Cloud app