Anyone else having an issue relinking to externally created proxies? When I select the clips that are offline and go to relink to proxies. I get the relink dialog with no media clips to relink. If I switch to relink all, same issue.
BUT if I select relink to original I have the option to relink.
Am I misunderstanding how relinking to externally created media should be done?
It's as if FCPX doesn't think the offline clips need proxies.
bcassin wrote: Anyone else having an issue relinking to externally created proxies? When I select the clips that are offline and go to relink to proxies. I get the relink dialog with no media clips to relink. If I switch to relink all, same issue....
The new feature to relink to external 3rd-party proxies requires XML to guide the process. Otherwise FCPX has no reliable way of knowing what proxy file matches what media file.
The process was described this way: "Editors can now link to proxy media generated by third-party applications via XML. Examples include Frame.io, a cloud-based creative collaboration platform for review and approval, plus asset management tools like Keyflow Pro and PostLab."
It seems plausible that clever people like Philip Hodgetts and Andreas Kiel (who are highly skilled at XML metadata) might eventually offer utilities to facilitate this.
wang_enn wrote: Before you relink the proxy files ,you have to relink the original , then copy the libary to another mac , relink the proxy files will apper.
On 10.4.09 it is not necessary to relink original media before relinking to FCPX-generated external proxies. After moving proxies to another drive, they will go off line, then you just select those red clips, then Files>Relink Files>Proxy Media. It will relink only the proxies in their new location.
The OP was asking about 3rd-party proxies, not FCPX-generated proxies. 3rd-party proxies will not relink by any method, but require XML from the software that generated them. Examples include Frame.io, Keyflow Pro and PostLab. Possibly after 3rd-party proxies are connected via XML they could be relinked using the above method if moved to another drive.
I use ffmpeg to convert the proxy files. The origin files must be online before i link to the ffmpeg proxy files , If the origin files missing i got error,the relink window didn’t show the missing proxy files. Once I set all proxy files online .I copy project without origin files to the other mac relink proxy files works fine too .
wang_enn wrote: I use ffmpeg to convert the proxy files. The origin files must be online before i link to the ffmpeg proxy files...
With 10.4.9, why would you create proxies with ffmpeg, since FCPX gives ability for various frame sizes, both ProRes and H264? With 10.4.9 there is a very simple workflow for creating a small proxy-only library. The procedure is much less error-prone than previous methods. It automatically handles non-proxy assets such as audio and graphics. See Ripple Training summary starting at 11:32:
foxytom wrote: Just saw the as I was looking for an answer to a similar problem and found the answer in this little vid by Felipe Baez.
The trick, it seems, is to make sure that they proxy and the original are linked for the very FIRST time, you need to have access to the original media. He also explains the logic of it...
Thanks for that post. However Felipe is not really addressing HOW to relink to externally-generated proxies, only that you must relink before sending a proxy-only library.
In his quick, simple demo he relinks to some Kyno-generated external proxies and it just magically works. But how could FCPX possibly know what original file matches with what external proxy file? There must be an accompanying XML file produced by the 3rd party proxy app that guides FCPX on the relink. To my knowledge the format of that and procedure are not documented.
FCPX can't even relink to its OWN proxies without XML guidance. E.g, generate proxies on several files, move those out of the library to some folder, then re-import the same original files to another library and try to relink to the proxies FCPX itself previously generated. It will fail. OTOH I've seen a few cases where it sort of works, so there may be some bugs or inconsistencies.
I also noticed another apparent bug in proxy relink. If you do the above test and try to relink a single file, it seems to disregard the media duration check. IOW it will relink a proxy from a different clip having a different length. So then you have a different clip showing for the same thumbnail when you switch the viewer between proxy or original mode. It still does the audio component check.