5D Mark II import problems. Any advice, suggestions?

[Tangier Clarke]

I’m with Oliver on this one. That was the big todo of Premiere’s Mercury engine – being able to just get to work on native formats. However you have to pay for it in the end when you’re up against a deadline and have to export to the very format you would have transcoded to anyway unless you’re going straight to H.264. Also, when you’re editing and applying effects, filters, layers, etc. H.264 native editing just becomes cumbersome and the load on the machine gets crazy. Whether your NLE is foreground or background rendering said effects and filters, it’s actually uncompressing (transcoding it first) in place then compressing it back to the timeline or storyline format.

With the lower cost of drives today, I prefer to do my transcoding up front for a more efficient (obviously that’s subjective) workflow from start to finish.

My 2 cents.

Tangier

[Tangier Clarke]

I’ve since trashed the screen grabs i took every time there was an import error, so I can’t check for the file sizes of the ones that had import problems.

Sad though, unless I’m missing a feature in FCP X that I have to keep track based on screen grabs and that FCP X won’t skip to the next import files without user interaction.

There needs to be a log of some kind like FCP 7’s transcoding window where you get an red alert for failed imports. Perhaps the issue is FCP X want’s to keep the files in their timestamped consecutive order and skipping one would throw that off. However I wouldn’t mind if it had some kind of Finder level temp file there or a disconnected clip name in the event browser with a yellow yield-like error marker to show me that there was an issue importing and the file isn’t there. Besides, even if it did skip a file or files and you had to go back and reimport that – the way it adds the clips timestamp to the file name, if one sorted the Finder clips by name they would still be in order, just not in order by date created.

Tangier

[Moira O’brien-galea]

This is a bug introduced in 10.0.8 and applies to both 5D2 and 5D3 imports (i have not tried it with any other camera).

As FCPX ingests 5D3 files with timecode I don’t want to lose that facility. Dragging and dropping the .mov files gets over the problem but I lose the timecode info.

Canon, please sort this out. I never had any problem ingesting files until this update.

Moira