You're not missing anything, Paul; there are no docs. There is also no API around RelinkFootage(); yes, the feature has already requested. Several partners accomplish what you've described, like this: Editor completes their edit, using lo-res footage. Editor exports FCP XML for the project (new in PPro CC: you can export just the active sequence as FCP XML.) "Munge" the FCP XML using some custom tool, replacing file paths to lo-res with paths to hi-res. IMPORTANT: The lo-res and hi-res footage must be using the same audio channel configuration, or you'll get off-line clips. Import the 'final' FCP XML (footage paths point to hi-res) Render the 'final' project. All of the above, except the custom munging (your job!) and exporting, are possible via PPro CC (and, with the limitations noted above, CS6) scripting. Our MAM partners typically write a custom panel (which can also execute scripts) to provide interaction with their managed assets, and communicate with an Export Controller plug-in (there's a sample in the PPro C++ SDK) to drive the Render stage. Of course, one of PPro's strengths is how it deals well with the heaviest of footage types, withOUT needing proxies, so I'd start by assessing whether PPro CC is performant enough with native footage, before bothering with the above. Feel free to ask me stuff here, and/or write me directly to discuss your workflow further.
... View more
AdChoices