[Tangier Clarke]

Joe thanks for the reply. I did test against each camera separately and the audio still had sync drift. I did have to use PluralEyes to remedy this simply because it has sync drift correction. It worked about 85% of the time. Essentially I had to locate in the Finder each matching angle and audio, drag that into PluralEyes, sync, then send to FCP X, repeat. Not fun, but it helped. I am not a huge fan of PluralEyes, but it does come in handy some time. I think perhaps my expectations of any app to be five multiples audio clips and audio and generate multicam/synchronized clips separately (rather than a synced timeline of clips) in the browser or bin or media pool is too heft a request; perhaps on the app memory side of things I am not sure.

One of these days I’ll get around to using Tentacle Sync devices

It would definitely be a nice feature for FCP X to accommodate sync drift in the application. I too like the F8 for the same features you mentioned.

Thanks again.

[Tangier Clarke]

I have a library that, after being launched became corrupted. I managed to export an XML of the library after this notice. The DTD failure is the result of that XML being imported into a new library. The most recent backup library and exported XML has similar problems.

I ran the XML through Digital Rebellion’s XML Repair, but it found nothing wrong.

[Tangier Clarke]

I am confused with your question. It’s from FCP X. Do you mean is it from a library, event, or project? I believe it’s a library XML. An XML made from the backup file gave the same results when trying to import.

[Tangier Clarke]

I echo Jeremy on transcoding in FCP X. Let it do the work for you so that it maintains it’s database. If you prefer to do it outside of FCP X as I tend to do you may want to transcode using EditReady. We’re very particular about having custom file names that are maintained and easily searchable/ identifiable through post, archiving, and resurrecting, a project if need be. Unfortunately FCP X can’t do that inside it’s database and in the actual Finder file name. 99% of our projects run through EditReady first, but you should be fine with all of those codecs in FCP X. If you’re wary of space then transcode to proxy during editing, ProRes on Export.

[Tangier Clarke]

I found it. It’s called “counting”. Didn’t realize that was there. It seems more or less like the same Numbers generator in Motion but with a different name. Though it (the FCP X generator) seems it still doesn’t work with just 10 frames of the generator.

Using the default generator in 10 frames won’t get me from 1 to 300 as are the default parameter start and end values.

[Tangier Clarke]

There’s a numbers generator in FCP X? I can’t find that. had I know I would have just used that.

[Tangier Clarke]

[Tangier Clarke]

It can vary. Let’s say 0 to 100 in 10 frames. I am trying to simulate changing bank account amounts. So it can be $45-$55, $80 to $140, or $200 to -$30.

It works without issue in Motion, but as a published parameter it doesn’t work.

[Tangier Clarke]

I am preparing to import footage from a C300 MK II.

I wondered just in general do you all still use the Canon XF plugin when FCP X supports the format directly? I am trying to better understand do you need the plugin anyway. Searching the inter webs I see that perhaps the plugin was need a little while ago; particularly with FCP X 10.2. I hadn’t checked when FCP X began supporting XF-AVC. Does the plugin provide any benefit? With FCPX 10.3 is it needed.

Aside form being just for this camera and format, in general do you install the plugin when FCP X already supports the format for any other camera and codec?

[Tangier Clarke]

And I see I missed the concept here. The entire time I thought the title generator itself was somehow affecting the movement of the frame when actually as you mentioned it’s the animation on the title background that affects the frame.

Thanks.