AVCHD video from Canon C100 stuttering in FCPX 10.4

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.

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.

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.

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.

Here's a technical question for Tom maybe... anyone really! Would it be possible to run both 10.3.4 and 10.4 at the same time on the same machine? Maybe 10.3 under one user account/login on say an iMac, and 10.4 under a different user account/login?

If that's possible, then maybe at least I'd still be able to use all of my computers for importing and editing the same projects across the board until (hopefully) Apple fixes this problem.

Oh well... figured it was worth asking anyway. At least I hung onto 10.3 on one of my machines for importing. It would be nice if Apple would at least make 10.3 available as a download to other subscribers who weren't as lucky while they sort this out.

You got some communication from Apple related to this issue?! Over the years, I've probably submitted a dozen Feedback tickets via that link you posted. I've never once gotten a response from Apple about any of my issues. You getting a response is like finding the holy grail for us pro users regarding communication from Apple.

What did they tell you about the issue? Are they working on it? Do they hope to resolve this issue with AVCHD footage (AVCHD/interlaced footage is the common denominator for all of us... I'm filming with Canon XA10's.)?

It's really hard to believe that some things that have always worked perfectly since the advent of FCP X can suddenly stop working properly after simple updates. And it's even harder to believe that Apple won't make the version that did work for us well, 10.3.4, available again for download until said issues are resolved.

That's what I feared. Sometime in the next week I'll upgrade myself and see how the problem has improved or not.But yes, it's good to know that at last somebody at Apple is acknowledging that the problem exists.

From the Final Cut Pro menu.

Yeah I'm having that red issue as well. Very annoying.