This fcpxml is at least a problem with a feasible solution. How about 200+ audio clips with no audio to sync external audio to.
Welcome to the real world, where things go and do things you didn't want or expect. I don't think it's acceptable practice in a collaborative workflow to pass people files they can't read. The FCPXML that describes that has no easy way to map to plain XML without serious human interpretation. Just put the car door sound clip directly beneath its matching video clip all "above the line" so you can work on them both as a visual unit.
A simple example would be that If I put a cutaway shot of a car door closing five tracks above my Primary storyline - in X there's no reason to put the Sound clip that matches that shot 5 levels BELOW the Primary. For example, there are X capabilities like Auditions, Compound Clips, Synchronized Clips, video clips with (trackless) embedded audio - and dozens of other attributes of an X edit that simply don't have exactly matching capabilities in a tracked timeline. Regardless of whether you use one of the XML translation utilities like Intelligent Assistants XtoCC- you're going to have to accept that X has editing constructs that simply don't exist in other NLEs - so there is never going to be a translation that happens without problems.
0 kommentar(er)
