I've spent a while searching the forum and found lots of info on the care, feeding, and use of proxies but have not found this specific situation so far.
I'm shooting 4K video with a Canon C300 MKII which can generate a proxy file as it records the 4K file which it saves to an SDHC card in the camera. It uses the same exact file name but adds a _01 P at the end of the name.
The camera proxy file is 4% of the file size of the 4K file (2.33Gb compared to 57.7GB).
The FCPX proxy file is 12% of the file size of the 4K file (6.97GB compared to 57.7GB).
I typically store all media in the Libary and check off generate Optimized Media and Proxy on import.
If I wanted to use the camera generated proxy files to edit with and then switch to the 4k files before outputting what would be the best workflow? Would I need to store the original media outside the Library in one folder, the camera generated proxy in another folder and use something like A Better Finder Renamer to remove the _01P from the camera generated proxy?
I know that the simplest thing is to just use the FCPX generated proxy files . . . which is what I do now but was trying to wrap my head around this other workflow.
The administrator has disabled public write access.
...I'm shooting 4K video with a Canon C300 MKII which can generate a proxy file as it records the 4K file which it saves to an SDHC card in the camera. It uses the same exact file name but adds a _01 P at the end of the name...I typically store all media in the Libary and check off generate Optimized Media and Proxy on import....If I wanted to use the camera generated proxy files to edit with and then switch to the 4k files before outputting what would be the best workflow?...
It's not possible to use externally-generated proxies within the FCPX proxy system -- unless FCPX proxies are generated first to produce the required SQL table entries within CurrentVersion.fcpevent. If the externally-generated proxies match specific criteria -- filename, aspect ratio, audio config, etc, you can create FCPX proxies, discard those and copy the new proxies in their place. Alternatively you can regenerate the symlinks pointing to the new proxies using the "proxy cheat" method discussed in this article: www.fcp.co/final-cut-pro/tutorials/1828-...ant-by-using-aliases
Note the "proxy cheat" method is actually using aliases, not symlinks (even though Finder calls them both aliases). This procedure kicks off an undocumented FCPX behavior whereby it reads the new aliases and creates fresh symlinks pointing to the proxy files. To avoid a filename collision with the aliases, the new symlinks will have the suffix (fcp1), so the library or the designated media storage location will end up with two pointers for each proxy file, one an alias and the other a symlink. I have tested this extensively and it mostly works but is not 100% reliable.
There is a new app under development called "AProxyMate" which will automate some of the above but it will still require you generate the normal FCPX proxies before replacing those with new proxies. This was discussed in FCPX Radio #78: player.fm/series/final-cut-pro-radio-109...app-from-pixelstitch, but the FCPX proxies must have first been created. This procedure might be useful if you needed small proxies for web use. However it does not avoid the time-consuming process of generating FCPX proxies.
There is currently only one way to use externally-generated proxies without creating FCPX proxies. You create the proxies which match FCPX criteria, then relink the library to those, then use the proxies as original media. When you are finished editing you then relink back to the true original media. The downside is you can't rapidly switch between original and proxy modes, nor have mixed original/proxy media. The upside is proxies will never get lost and you can relink them if changing drives. I have done limited testing of this and it seems to work, but I wouldn't trust it without extensive workflow testing.