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 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.

So... I see there's now a FCPX 10.4.1 update (adding closed-captions). But, not a peep about the AVCHD issue in the update notes. Kind of mind-boggling considering how widespread this problem is.

Has anyone updated to 4.1 and noticed this problem has been addressed? Or is it still a problem?

If it's still a problem, this would be a huge letdown. Considering months go by between updates, this could be an absolute nightmare for countless professionals out there.

I hope it's been quietly addressed. And as appreciative of Apple that I am, it drives me crazy that they won't even acknowledge a problem and let us know they're on it. With no updates or commentary from Apple about a problem like this, it's anyone's guess that they're even paying attention to us.

So I tried this workaround, and, unfortunately, it didn't work for me.

https://www.youtube.com/watch?v=swxBfFYIBVM&feature=youtu.be

That's a video clip from the workaround import:(

Thanks for trying this out though!

Just to check in... I updated to 10.4.1 and that DID NOT solve the AVCHD video issue. I'm really, really disappointed in Apple this time around. It's a huge letdown to update the app and not have a fix for something that so many of their users are experiencing. We can't even use any of the great updates if FCP won't even import our footage without artifacts. Not even a peep out of them even acknowledging the issue. I'm afraid I'm going to have to look to other editing options with my busy season approaching. I feel so let down.

I have not... not familiar. Just looked it up... $50. That's not a big deal, but even if it worked, it adds another step to the import process that was not needed before the 10.4 update. This whole thing really feels like a punch-in-the-gut... and I'm truly beginning to believe Apple really doesn't care about their pro users much anymore. I find it very hard to believe that their team of engineers couldn't come up with a fix for this in a matter of hours and get an update out for their pro user base ASAP.

This is what I'm still dealing with after 10.4.1: Artifacts - YouTube

That aside, how would EditReady help, in theory? What steps would have to be taken to get the footage from EditReady into FCP 10.4 (or 10.4.1). Maybe if it cuts down on the usual transcode time in FCP, perhaps it may be a workaround that is worth looking into.

There is a free trail of EditReady but unfortunately it only works on the first minute of each clip, so owing to the random nature of the problem it's hard to prove if it solves the issue.
It does seem easy to use and has some other handy features but yes it is a pain having to add that transcoding step to your workflow and negates a lot of the speed advantages of FCP.I have used a trail of Kyno and it's working fine but it's expensive so when the trail finishes I really have no other alternative than to get EditReady.
Unless of course Apple pulls their finger out and somehow solves this mess, but I'm starting to fear they are just going to ignore AVCHD and let third party apps solve the problem.

Thanks for taking the time to chime in, Brett. So you've had success with Kyno? I'm not familiar with it, but if it is taking your AVCHD footage and "fixing" it (I assume converting it to ProRes for FCPX) so it plays back without the artifacts in FCP, that's promising if, in theory, EditReady does the same thing. Also, in theory, wouldn't the files only have to be copied into a new Library in FCPX when importing without having to check the 'Optimize Media' box? If so, then that's not so bad if it cuts out the optimizing time typically associated with FCP during import.

I hope Apple isn't just going to ignore AVCHD. That would be like Adobe ignoring RGB and only allowing CMYK to function properly in Photoshop. Seems ludicrous from a business perspective given how common AVCHD is. Maybe not as common as H264 MOV files, but still... close to half of my colleagues out there film to AVCHD.

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.

Brett, are you saying the glitches are only on transcoded AVCHD files, so in ProRes or proxy files? Does what mean if you don't transcode you don't see the problem, and/or that when you export a file from the glitchy timeline to say H.264 you don't see the glitches either? Do you have idea about what length of file triggers this problem?

Thanks.

I can't speak for Brett, but I did some tests under those scenario/s, Tom.

In my first test, I imported an entire wedding shoot and did not transcode the media like I typically do (left the 'Create optimized media' button unchecked). Besides the checkboxes 'Add to existing event' and 'Close window after starting import' the only box checked was 'Copy to library' from that popup menu. After FCP was 100% done ingesting the footage, I still had artifacts.

I did a second import test in a fresh library, this time only checking the 'Leave files in place' (on a dedicated hard drive for all of my master video files straight from the cameras). I was hoping this would ditch the artifact problem, but I had no luck. I still had artifacts, at different points in the footage too. So it's completely random.

I also looked at the master video files directly from the AVCHD source, but they play back fine in Quicktime without any artifacts. It's clearly an issue importing into final cut 10.4 or later.

My solution, for others that might be reading about this problem for the first time, is to continue using 10.3.4 or earlier, if you still have it (fortunately I had 10.3.4 on one of my workstations and now solely use that workstation for importing footage).

Exactly the same issue. I've imported into library as optimised media, proxy media and original media, I've left files in place, doesn't matter what I do the issue is still there and totally random. If I delete the original and relink in the storyline the issue sometimes disappears but either comes back or moves to another part of the clip.
The only solution so far is to transcode into ProRes outside of Final Cut, then import.
I've had FCP X pretty much since its release and use AVCHD footage every day and the issue only appeared in 10.4. Sadly I don't have 10.3.4 and all my libraries have been converted to 10.4

From the release notes there's no mention that I have seen about this problem being addressed.
Perhaps it's in the too hard basket or Apple have just given up completely on AVCHD import.
Two updates without a fix is not a good sign.

Thanks for responding, Brett. I too looked at the notes... I'm just hoping they may just quietly address this issue. I'm not sure how hard it could be to figure out... AVCHD was able to be imported into FCPX since it's inception. To me, it's obviously just a simple bug somewhere. If I can go back to 10.3.4 and successfully import AVCHD, it's certainly not a hardware issue. If it's hard to figure out you'd think they'd let us know they're "on it" and to stay tuned. If that were the case, I'd continue my workaround despite it adding a significant amount of time to my workflow. And if they are giving up on it, you'd think they'd let us know that, too. Because if that was the case, I'd certainly have no choice but to migrate to another program that's will be reliable for my workflow. I'd find it very hard to believe they'd give up or abandon AVCHD. To me, it would be like Photoshop telling its pro users they'll no longer be supporting RGB or CMYK. I've submitted a couple of the feedback forms regarding this issue... practically begging them to at least acknowledge the issue with it's pro user community, and still nothing. It's growing more and more frustrating that pro users that Apple claims they value are left in the dark over an issue that renders its pro editing program useless for a sizable contingent of their user base. It's frankly mind-boggling at this point.