AVCHD video from Canon C100 stuttering in FCPX 10.4

Hey Matt, In all of my tests Quicktime has always perfectly played files directly from AVCHD and BDMV structures. It's only after import to FCPX that the problems appear.

Did you try the workaround yet?

I've posted about similar problems but with the C300. Just adding in that all issues should be reported directly to Apple through the Feedback - Final Cut Pro - Apple link. I went through all the steps and got a support ticket opened with some communication back and forth, it would be good if everyone having the issue did the same.

I received an email from the Apple Pro Apps team from Apple on Friday. They instructed me to update to 10.13.5 and asked if I could import some AVCHD and see if that resolved the problem for me, that they believed the 10.13.5 updated would resolve the issue.

I updated my MacBook Pro to 10.13.5 and tried an import with no success.

Today, I wiped my MacBook Pro and did a clean install of 10.13.5 from a bootable disk I created. Then I installed FCP from the App Store. After another attempt at an import, I'm still having the same issue.

It's not as prevalent or common in the footage as before. I found three instances of pixellation at the top of the screen in a clip just over an hour long, where before, maybe it was a couple dozen. But the problem still exists (using Canon XA10's that film to AVCHD).

So, for me at least, 10.13.5 is not a fix. But I'm encouraged to finally have this problem officially recognized from the Apple team. That tells me they're determined to fix this issue, for which, I'm appreciative.

I'd like to follow up one more time. I'd like to make clear, THIS MAY BE A FIX FOR MOST OF YOU! I've done more tests on some other footage and it only appears that the issue only affects clips longer than an hour long. I can't find any artifacts in shorter clips. And, oddly, in two of my tests on clips over an hour long, the artifacts have only appeared around the 40 minute mark. In both tests I couldn't find any artifacts in any other part of the clips. So, if any of you never film anything over an hour long, you may be in luck with his latest OS update.

I have flickering issues with reds in 10.4. They start flickering desaturating on and off. Pretty annoying. I have to transcode all the files in a separate software.

Canon c100 avchd

Apple has to address this

It appears to have something to do with how FCPX converts either AVCHD or BDMV collections or rewraps .MTS files that ends up corrupting the clip data. It also changes the clip numbers.

All I know is that when I remove all that before importing the clip, It looks perfect and still has the same clip numbers.

I just finished a muticam edit today which worked fine.

I could be wrong... I did so many tests, over two months ago, that maybe Quicktime did play the files fine. For some reason I remember it didn't, but maybe I'm getting it confused with iMovie or something else. I haven't tried your workaround yet. Admittedly, I've been bogged down with a renovation on our home. However, my workaround has been using 10.3 on one of my computers for doing nothing but importing footage. That's the easiest way for me. But I do intend to try your workaround and see if I have the same results at some point! Once I do, I'll report back with my findings.

Yeah it converts to whatever ProRes version you need and does so pretty quickly but you still have to wait until everything is transcoded before you can start work and when you have 14 hours of footage.
Once converted into a designated folder you just import with leave files in place and no further transcoding required although I do transcode to proxy where the problem shows up again. But when you switch tp the original media on export the glitches go away.

I called in a few times too, offered up lots of documentation to help narrow the issue. It took some escalation up the chain, you have to be nice and persistent.

My problem with the C300 and Canon XF codec was addressed in the 10.4.1 update, but the fix actually made things worse. I'm still hoping for a fix that takes things back to pre 10.4, but who knows how far off it is. Seems like lots of issues for Canon gear right now.

Have you used EditReady to transcode the media?

It sure seems to be the case, Matt.

When I get to the studio today I hope I find my laptop still has 10.3.

This is twice I've been screwed by updates by Apple in the last 4 months. I lost 75% of the performance my iPhone 6+ when I updated to iOS 11. Had to pay $700 for a new phone when the phone I had worked excellently.

APPLE, CAN WE GET A FIX? You are hurting my business and me, too

Apple can you hear Me???

If there's one thing I've learned over the years, it's to not fix something that ain't broke. Typically I'll wait at least 6 months and monitor the discussion forums before I do any updates to FCPX, Motion, Compressor or my OS. By monitoring the forums before updating, I can see if there are any glaring issues and if those issues will affect my workflow.

This time, I only waited a month and took a chance. The expanded color control functionality pushed me to do it. With it being my slowseason, I wasn't doing much importing of anything. So for weeks I didn't think anything was wrong until I had to do some importing and found the issues with the AVCHD files. Thank goodness I still had 10.3 on one of my machines.

At the end of the day though, I always give Apple the benefit of the doubt. If it was not for the original iMovie and then the original Final Cut Pro back around 2000, I never would have gotten into video editing nor started my own business. The Apple ecosystem has made my career possible, and for that I'm forever grateful. I mean, I still have power mac's that can run FCPX. If I would have chose to upgrade the CPU's and other things, they'd still be great machines. The iMac's I'm using are nearly 7 years old and still humming along.

On top of that, the entire FCPX bundle is next to dirt cheap. Unlike the alternatives where there's hefty subscriptions or huge pricetags to begin with (and charges for updates). So when something goes bad, like an iPhone, I don't mind spending the money for a new one. Apple's saved me thousands over the years by not charging a subscription to use their editing software... not to mention the general reliability and long life of their hardware (desktops, laptops, etc.).

I've used the other software options too for editing... and FCPX is by far the best, to me at least.

Unfortunately there's growing pains with any update. It's rare when an update comes out and everything works as it should. This can be said of the alternatives out there, too.

I guess my point it, I try to keep things in perspective. Apple's helped me make well north of 7 figures while I've been in business since '02.

But if there's one thing I've learned, it's to BE PATIENT with updating any software or OS. Usually after 6 months any bugs are worked out. Sadly, I didn't take my own advice with this last update, lol.

Cheers!

Hey Matt,

Thanks for the timely perspective and hard won wisdom. I needed it.

I started in 1990 in audio production with an SE30 Macintosh (80 MB HD), and a Sound Tools II rig loaded with everything I could get.

I only used it half time and watched my more than $20K system go over the horizon to obsolescence pretty quickly.

I went to PC for 15 years to save money. Then I got hired to produce a local movie and decided to buy an iMac.

The day after I bought the iMac, I did a trailer using iMovie that was better than the movie itself. It took about 2 hours to make the trailer and I made enough to pay for the computer in 2 hours. I was sold.

Now for the price of my old SE30 I edit 8 cameras and 16 tracks of audio for music concerts on my latest iMac.

Pretty amazing.

Thanks for reminding me to be grateful!

This is interesting... so, basically you're just copying the MTS files to a new folder and then importing them from the new folder leaving the original copied files in place?

In theory, when one creates a folder and calls it "Smith Wedding", the original MTS files could just be copied to the "Smith Wedding" folder (or a folder within "Smith Wedding") and then import those copied file, checking the box to 'leave files in place' when doing the import?

Is that the general gist of it? If so, I'll do a test on a full wedding video import.

And if it works, that would make you a genius for figuring that out! Might be a good workaround for the time being while Apple solves the problem.