-
A cautionary tale: various major Xto7 woes …
A first foray into the wonderful world of Xto7 translation in the all-new FCPX 10.0.3 and it’s not going well so far.
A fairly straightforward sequence over just over two minutes duration, these are some of the problems:
1) All the video came through more or less OK but one clip (no different in source from various other successfully transferred items) was one frame long and used only the very last frame of the source video – not correct in either case.
2) A lot of the source audio was from an 8-channel source of which I only used one mono channel in the edit. These mostly came through as 32-channel clips – yup, that’s right 32!!! Wherever the audio had been detached from the video (a necessary step in this instance), it did not get translated.
3) The biggest problem however was that the majority of the audio came from two separate non-sync sources, both of them stereo AIFFs. Quite a few of these clips didn’t make it through the translation process at all. Of those that did, all of them use the first frame of the source for the first frame of the edited clip – which is a disaster.
Just to clarify all of the non-sync audio (i.e. from any audio source that wasn’t tied to video) came in using the first frame as the source timecode in each case.Just as I was starting to get excited about using FCPX for some real jobs and using Xto7 as a sort of intermediate OMF translator! I have to say that Automatic Duck, while it still worked, had a number of issues but it worked a whole lot better than this with audio.
I’ll be sending this feedback to IA and hope that there’s something they can do, but for now it’s a bust, for my type of workflow at least. That’s 35 of our English pounds unwisely spent 🙁
A shame.
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com