[Tangier Clarke]

This doesn’t answer specifically what you want, but if you don’t get an answer consider Mediainfo.
https://mediaarea.net/en/MediaInfo

It’s very useful and helpful.

Tangier

[Tangier Clarke]

That is correct. The file type stays the same – H.264, but it will be wrapped in an MOV. You can still tell FCP X to transcode all of the video content once it’s already imported. The above mentioned method just insures you have an as-close-to-original copy of your AVCHD files as backups. ProRes was not your original.

One workflow recap:
Import ALL media into FCP X
Go into library package and COPY MOV files out to unique folder reels
Assign same folder reel names to appropriate content.

The danger in doing this is that you have to be certain you imported all of your footage. Some people only import some of the contents of an AVCHD card; particularly if the card wasn’t wiped before the most recent shoot and therefore has leftover content from a previous shoot that isn’t necessary to keep.

It’s safer just to backup the card data into a unique folder as a reel. But if you know what you’re doing and are thorough, the method above isn’t a problem.

Just be mindful that with multiple cards you may end up with Clip1, clip 2, clip 3, etc multiple times. This is why you need unique reels folders.

Tangier

[Tangier Clarke]

You could also import the media into FCP X with no optimization. This way it just rewraps into an MOV file. Then go into your library package and COPY them out of there into unique folders as reels. These will server as your backups. Make sure to assign the same folder names to reels inside FCP X.

Doing this method you get:
Small file sizes (pre optimized)
Quicktimes you can just point back to easily

Tangier

[Tangier Clarke]

Yeah, I tried something similar as well. Thanks everyone.

Tangier

[Tangier Clarke]

No real problem I suppose. I like to keep my libraries tidy.

Tangier

[Tangier Clarke]

I should have copy/pasted the specific notice, but the error eluded to a difference in duration as the problem. Though rare, I have seen this happen before with FCP X and it boggles my mind how it happens. All I know is that between myself and another editor, I do all of my syncing in FCP X. The other editor sometimes get’s their footage from assistant editor who syncs using PluralEyes. Now that shouldn’t matter, being that we’re using the same reels (folders of content). So when I get the other editor’s event, library, or storyline project and trying and reconnect some things this happens.

I can’ point definitively that what I described is the cause of this. Though I don’t know what else to go to. It’s so strange that I am getting events with media references that are one frame off from me pulling the same source in using FCP X.

Tangier

[Tangier Clarke]

The only way I’ve been able to get around the annoyances of relinking/reimporting from AVCHD is:

(by the way as of writing this it’s 2016 and I am using FCP X 10.2.2. on OS El Capitan)

Make a new library and import the offline clips into that library’s event.
Move or copy the clips into the library I originally wanted them to be in.

Sadly it has to be this way because for some reason, the offline clips still register as imported in the import dialogue window; even though they’re offline. Trying to relink to reimport just plain doesn’t work when FCP X thinks it already has the clip. So odd. Clip is offline, but it already has it and therefore won’t import for relink.

The re-import from camera/archive feature is almost useless to me unless a camera, volume, or FCP X archive is mounted. I wish they’d add a reimport from folder feature. That’d solve things.

FCP X is an amazing app I’ll give it that. However there are some very basic things that it does so horribly or rather has tried to simplify so much to the extent that it’s actually more difficult.

Tangier

[Tangier Clarke]

Yep. Had that. Have it all set to stay with the library.

Tangier

[Tangier Clarke]

Still misaligned.

Tangier

[Tangier Clarke]

Funny, I hadn’t noticed that it is in fact better. However not totally. It’s not clean like before the bug happened, but there aren’t as many strange lines anymore. Now there’s just a small spot over the last frame number space and a couple of spots that look like dead pixels – and they aren’t dead pixels.

So it’s sort of fixed.

Tangier