I believe the error has to do with the "?" in the start of the saving location, which I don't know why it's there. Any ideas on how to fix this issue? Both Dropbox and Premiere Pro are up to date. I've also asked on the Adobe community, but I don't know if this bug is related to Adobe or Dropbox.
Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join
If the issue with creating or saving those projects into your Dropbox folder persists when Dropbox is completely closed, this would suggest that the cause is related to something outside of the Dropbox application. You may want to check other applications or components of your computer's Operating System that could be causing this.
I have used Dropbox for creative projects for years - ever since it first premiered, but I only started having this error in the last few months. In both ProTools or Adobe Premiere, saving project files OVER already-saved projects (ie, hitting CTL+S) results in an error from the application saying they can't save. See below:
This DOES NOT happen with any other file type (word, photoshop, for instance). This DOES NOT happen if just save to the desktop OR when I save when DB is quit/not running - so I know it's DB specific. This DOES happen on my laptop.
I have this same issue, specifically with Premiere only. Other apps including Photoshop, After Effects & Cinema4D do not have the same behavior even tho they are saved in to the same top level folder structure.
I'm not sure if the issue lies in Adobe or Dropbox's (or both) but my work around instead of doing a file save as is to temporarily pause DB syncing via the system tray icon. Super big pain for sure until the issue is resolved.
Yup, I also get this issue. Frustrating because I switched from Google Drive to dropbox because I was getting errors saving C4D into Drive, now on Dropbox I get this issue with Premiere! Everything else is fine though.
As Walter mentions above, could you let us know if you can prevent the error message from appearing by pausing sync before editing the file, and resuming syncing after you've closed the third party app?
Did this post help you? If so, please give it a Like below.
Still stuck? Ask me a question!
Tips & Tricks Find new ways to stay in flow or share your tips on how you work smarter with Dropbox.
So the only way to save the file while dropbox is actively syncing is to do "Save As", hence why there's 10 versions. Everytime I tried a normal "Save" it would create those additional files with the crazy names!
I'm working in a project which is a long-term project of 3 movies. I created the project last december and finished already 2 movies early january. For the 3rd film I had to wait for some extra shooting and I started editing about 2 weeks ago. From this extra material I used some for the elder movies, which I edited earlier, and re edit them.
Exporting the latest movie, with the new clips, doesn't give this error. But the other two movies just won't export! It makes me go mad! I have been trying for hours to find a solution for this error/ bug
Solution: Open task manager, close all the Adobe creative cloud services running in the background. Reopen the premiere project, select Cuda in the project settings. It should properly work now.
I believe this error code indicates too many GPU accelerated effects during the export process. The editor needs a more performant computer system, including a GPU with more VRAM based on their workflow.
Thanks,
Instead of exporting the video right from premier, I sent it to adobe media encoder (I think everyone do this but I just found out... jaja). There... I preview the file while it's being encoded. The error kept occurring in the same second of the timeline so... I basically "redid" that part (no really, simply re-import some files, etc) until the error stopped.
In my case... I had trouble with 2 .png files with a lot of transparent, overlapping, unnecessary space. I drove them to photoshop, cut them a little, saved them, and reimport them. I don't know if cutting them was really necessary or simply reimporting a new version of the .png would have worked... but... that's how I solved this problem. Hope you guys did too!!
In my case, the error was being displayed because of a JPEG file because it had a " ' " in the name (this is what I guess, I'm not sure). As soon as I fixed the name and relinked the file, the error was gone.
ff7609af8f