You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
"Unknown Error" when saving an Adobe Premire Pro project directly into a Dropbox folder
I use Dropbox to store most of my files so I can share them easily, so I normaly create the projects directly on a Dropbox sync folder on my PC.
However, since some days ago, I have started get...
Thanks for the update Agirres.
In this case then, this might be caused by the syncing process when our app is running while you're also working on Adobe Premiere Pro.
Apart from quitting the app when working on your files through Adobe's Premiere Pro, you might also be able to work-around this issue by pausing the sync.
I know it's not much, but I sure hope this helps to some extent.
Please let me know if there's anything else I can assist with.
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:
A similar unknown error comes up with protools.
However, doing a "Save As" works fine - until it's saved. Then, if I try to save THAT file again, I get an error.
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.
Windows 10 Pro build 1909. Fast everything. Plenty of disk space.
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.
