FCP X Import of M2TS AVCHD files causes pizza wheel on browse?

[Jeremy Garchow]

Bill-

X does not need the volume to read this media.

[Robin S. kurz]

Which versions of FCP X and OS X are we even talking about? Nothing unusual about the disk they’re coming from?

But yes, the import of AVCHD files, whether from the camera or even the individual “naked” MTS files, haven’t been a problem for me as of 10.1. So I’m with Jeremy on that one. It must be something else.

[Bill Davis]

[Jeremy Garchow] “Bill-

X does not need the volume to read this media”

Jeremy,

I’m not saying it needs volumes to read it.

I’m saying that if the issue is that the software isn’t “finding” the clips in order to import them – then putting them in the volume structure that is most native to FCP X is one way to potentially overcome that issue.

The X engineers will always make more and more filetypes “readable” as the program progresses. But there are ways that the clueless can manipulate the raw assets in THEIR workflow that strips out the location Info that X relies on to see and work with files.

And my suspicion is that this was the OPs problem.

But as always I can be wrong. ; )

It’s just that if ClipWrap could solve it, then the fundamental problem might not be the nature of the clip itself, but rather the clip header info that ClipWrap is replacing. And It may be that re-wrapping the files into a volume structure that X understands may just be enough so the the program can then see the clips properly without having to go outside for that file header repair.

Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

[Ben Hendriks]

My experience:

When importing MTS directly X uses de transportstreams with (in my case)
ac3 audio. With a lot of clips a lot of beachballing.
With volume structure X rewraps to mov and transcodes the audio to pcm.
A very different approach, I think Clipwrap does the same.

Cheers Ben

[Tim Jones]

We have finally uncovered what was causing the issue in the m2ts files that we received and whyy they were giving FCP X fits on import – the audio was encoded as AAC instead of the AC-3 format as defined by the standard (thanks to Colin at Divergent Media). To make things work, FCP X was converting the AAC audio to AC-3 for proper container contents and that’s what was putting the system in bog-mode.

I’ve asked the content creator to change the audio type to AC-3 for future clips.

Tim
—
Tim Jones
CTO – TOLIS Group, Inc.
https://www.productionbackup.com
BRU … because it’s the RESTORE that matters!

[Bill Davis]

FCP X Axiom.

Sometimes, the cause of your problems in X will actually be the video. –
but most of the time, 100% of your problem will be your audio!

(Going to get a needlepoint of that done someday.)

Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

[Tim Jones]

Corollary to that axiom – even if it’s not your audio, it’s your audio!

What a strange trip this has been.

Tim
—
Tim Jones
CTO – TOLIS Group, Inc.
https://www.productionbackup.com
BRU … because it’s the RESTORE that matters!

[Fabrizio D’agnano]

[Tim Jones] “To make things work, FCP X was converting the AAC audio to AC-3 for proper container contents and that’s what was putting the system in bog-mode.
“

And why is Clipwrap so much faster in doing that, if it’s what it does?

Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2014 MacBook Pro Retina, Blackmagic UltraStudio Mini Monitor, FCP7, FCPX, OSX 10.9.4

[Jeremy Garchow]

[Tim Jones] “I’ve asked the content creator to change the audio type to AC-3 for future clips.”

Glad you got it sorted.

Jeremy