Open latenitefilms opened 8 months ago
Currently Metaburner creates a cache file in the Application Support folder when you import a FCPXML.
This cache file is read on the first frame of playback and saved to memory.
However, currently if you move the Final Cut Pro Library to another machine, there's no mechanism to re-build the cache file.
...and to complicate things, currently "Save FCPXML Internally" is off by default.
Currently Metaburner creates a cache file in the Application Support folder when you import a FCPXML.
This cache file is read on the first frame of playback and saved to memory.
However, currently if you move the Final Cut Pro Library to another machine, there's no mechanism to re-build the cache file.