Premiere 2022 issues opening project from network

Report · Feb 15, 2022

I'm running Premiere 2022.2.0 on two Windows PCs with similar builds (PC1: i9/64GB/2080Ti/Win10) + (PC2: i9/32GB/3070Ti/Win11). Both are connected to my QNAP TS-1685 NAS via 10GbE switch for shared media. On each individual computer, I have no problems at all with this setup. Playback is smooth, relinking is quick, etc. However, when I save a project on PC1 and then attempt to open that same project file on PC2, the project loading screen hangs at 75% and loading will not complete. Some trial and error indicates that, if I unlink all media before saving, PC2 will eventually open the project but it takes hours and hours depending on the complexity of the project. If I don't unlink, the project never loads as far as I can tell.

This obviously has something to do with the networking but I'm baffled by what that could be. If I was direct connected via USB, the project file would open instantly and ask me to relink as usual. That would also be the expected behavior if there was some sort of mismatch in the drive mapping here so if that's the case, why is the project hanging indefinitely? It's making working on the two systems impossible.

Wondering if anyone using network drives (NAS or otherwise) has had a similar issue. I found an answer in the forums that suggested repairing Virtual C++ processes but that had no effect. Really struggling to identify the cause of this and could use some help. Adobe chat did not understand my issue and I haven't been able to get on a phone call with them but suspect that would be a dead end anyway. Really need both of these up and running!

Report · Feb 15, 2022

You say you use that Qnap for media sharing, but didn't say if the project files are on that system also. Do you use the same locations for both computers for the project file/cache stuff, or are they different, perhaps local storage?

The project files are of course the database for the entire project's ... everything. And they use various cache and other files as storage for parts of their data. Which they can typically rebuild when moved, but that rebuilding can take some time with larger projects.

Neil

Report · Feb 15, 2022

Hi Neil-

Thanks for your response and here's some clarification:

- The project file (as in the .prproj) is generally kept in the project folder along with the auto-saves on the NAS. However, for my testing, I tried putting the project file on a local SSD as well. No change in behavior.

- All cache, peak and preview files are on a local M.2 per individual computer. Which would mean that the first time a project is opened on one PC, it would need to build its own peak files and cache, etc. I would say this could be a cause for the hang except that this same behavior is not exhibited when I copy media to an external and share with an editor on another system. In those cases, the project opens normally and when media is relinked, the caches are rebuilt without issue. So I don't think this is the culprit either. Plus, the fact that the project simply will not open means it never even gets to that point, correct?

Report · Feb 15, 2022

I should also note another test I tried:

- I tried disconnecting the network drive completely and opening a local project file that referenced media there, hoping that the expected behavior of opening quickly and going straight to the relink dialogue would happen. It did not. It's simply not opening still. On hour 3 of waiting to see if it will open. This is not a complicated project so even if it needed to rebuild database files, it should have taken 5 minutes max.

Report · Feb 17, 2022

If anyone is reading this via search for this issue (like me), I spent a couple hours with Adobe on the phone today troubleshooting this and have a workaround but not a solution. The problem is not with networked media but with the fact that a network drive is connected at all. If you physically unplug the cable connecting to your NAS and open your project, it will open just fine. Then reconnect the cable and link your media. The rep I spoke to described this as a bug that he will present to the engineers. Entirely possible it's a setup problem with the NAS but he couldn't imagine a scenario in which that would be the case. But at least I have a way to open projects now.