[Chris Bravo]

Thanks for the tips. I will definitely try the Xto7 if I get desperate. For now, I am exporting a prores and using Resolve’s scene detect to cut it up, which works well, as long as you are sitting on a pretty decent picture lock…

Your suggestion to use FCP7 to scrub the “bad” parameters off the xml got me thinking, so I opened up the xml directly in Dashcode just to see what it looked like and was surprised to get this:

in the resources list:
<media id="r3" name="BOAC_performance" uid="Htjxbg9wREm3H29rVH7b+Q" projectRef="r2"/>

and this in the string-out section:

<mc-clip offset="8648640000/2400000s" ref="r3" name="BOAC_performance" duration="97297200/2400000s" start="4764039280/2400000s" audioAngleID="Upyx4xb1To+JD+YLa7xwSg" videoAngleID="wDH5j0YMS3eB9YNd3NcPhA">
<keyword start="0s" duration="167388221/30000s" value="boac_performance"/>

remarkably, to me at least (not any sort of programmer), there is no reference to the actual media file (MVI_XXXX.mov) but only to the name of the multi-cam clip in FCPX (BOAC_performance) and a videoAngleID. Which sort of raises more questions like: how is it even possible to use the XML, as a stand-alone document, to link back to the original footage at all?