on Dec 21, 2019 at 5:19:05 am Last Edited By Michael McCune on Dec 21, 2019 at 5:30:26 am
Previous post mentioned an issue with Fusion Studio 16, and to a lesser degree, Resolve Fusion, where Fusion would not recognize known-good files. That is, files that would open and work without issue in other applications.
Fusion simply did not respond when asked to open most files: note that Windows did not have any problem with these files. Found a sometimes successful workaround by importing the files into Resolve Edit page and then into Resolve Fusion.
Found some files that did successfully import into Fusion but otherwise Fusion Studio would not respond, not even showing error messages in the console, other than an occasional, "Failed to load at frame 0."
Tried everything from firewall blocks, permissions, path length, hierarchy depth, etc. No joy.
Then by happenstance found that between two copies of the same file content (namely, a tif frame sequence), one succeeded and the other did not.
Found that the file name of the successful version was very simple for test purposes. But also found--by using an extended name using a simple repeated character-- that the file length and the path length itself was not the problem.
So, what was the difference between the successful and the unsuccessful file names???
Found then that the failed files used a semi-colon in the file name (as a separator between descriptors used to denote various ongoing changes). This local naming convention was implemented on hundreds of current project files without issues in Resolve nor in other applications such as 3D LUT Creator, Photoshop, Topaz, Natron, Media Encoder, and others.
The semicolon is a legal file and path name character in Windows. BUT NOT, with the help of Mr. Google, LEGAL for SMB names. Resolve Studio and Fusion Studio seem to differ in their reliance upon the SMB protocol, arising perhaps from features such as remote rendering and collaboration.
Changing file name semicolon character to another separator character seems to have solved this (very troublesome and really debilitating) problem.