Weird Glitchy Area on my Footage

[Michael Hancock]

Great news! And don’t forget to file a bug report with Apple!

—————-
Michael Hancock
Editor

[Paul Binks]

Yes I am dragging them out of the stream folder, but no matter where I try to place them fcp won’t accept them

[Paul Binks]

I have successfully transfered three mts files but that is it, every time I try now fcp crashes

[Jon Baum]

I too have experienced the import glitches when importing into FCPX from a Canon Vixia HF G10 camcorder. The ClipWrap workaround is effective as it can open multiple .mts files as “Spanned” and convert into a single .mov file suitable for Final Cut Pro X and does not exhibit the glitches.

Unfortunately, this import anomoly continues with Final Cut Pro versions 10.4.1 and as of yesterday, 10.4.2. I sincerely hope Apple addresses this bug in the next version release.

[James Cude]

Looks like this might be fixed in the macOS High Sierra 10.13.5 update.

[Jon Baum]

I’ve updated to MacOS 10.13.5 and then imported 4 clips from my Canon Vixia HF G10 camcorder into FCPX 10.4.2. So far, so good. No digital anomalies. This is part of an e-mail I’ve received today as a reply from my feedback report of this thread’s issue through the FCPX app:

Hi Jon,

This is Chris from Apple Pro Apps in Cupertino. Thank you for your recent feedback about using Canon AVCHD clips in Final Cut Pro.

We believe this issue has been resolved in the latest macOS update, which was released earlier today. At your earliest convenience, please update to macOS 10.13.5, see if your issue has been resolved, and report back with your results.

[Jon Baum]

It’s BAAAAACK. Same glitchy issues importing from my Canon Vixia HF G10 into Final Cut Pro v10.4.7 under MacOS 10.15 (Catalina). Workaround continues to be copying *.mts files to my MacBook Pro desktop from the camcorder’s SD card and then using EditReady to join the .mts files and then rewrap into a single .MOV file which is then imported into FCP – without the artifact glitches. Hope the FCP team at Apple sees this post and gets it on their radar to fix, again.

[Joe Marler]

[Jon Baum] “Same glitchy issues importing from my Canon Vixia HF G10 into Final Cut Pro v10.4.7 under MacOS 10.15 (Catalina). Workaround continues to be copying *.mts files to my MacBook Pro desktop from the camcorder’s SD card and then using EditReady to join the .mts files and then rewrap into a single .MOV file which is then imported into FCP -“

I have some old HF G10 material and it seems to work OK on FCPX 10.4.7 on Mojave 10.14.6.

Normally the correct procedure for AVCHD is import from the AVCHD package which automatically re-wraps and copies the files into the library. You should not copy .mts files out of the package and import using leave files in place, which can cause performance problems.

Alternatively you can use EditReady to re-wrap the files in the AVCHD package and then import those using “leave files in place”. This automatically includes all needed metadata and handles clip spanning.

If you still have problems when doing that, I can look at some test material if you put it on a share point.

[Jon Baum]

I just updated to MacOS Catalina 10.15.1 and re-imported footage from my Canon Vixia HF G10 that showed the digital anomolies under 10.15. Same glitches appear during footage playback – I’ve sent in a FCP bug report last week. Hopefully they will re-address this problem.

I did follow Joe Marler’s process of reading the mounted volume from the camera’s SD card with EditReady which nicely spanned the packaged .mts files and converted to a *.mov file that was devoid of any glitches.

[Jon Baum]

I have reported the digital anomolies issue with Apple Pro Apps support and have been working with an excellent Apple Creative Media Senior Advisor to gather pertinant information on FCPX, MacOS (Catalina) from my MBP laptop and also from a fresh Catalina install on an external drive partition. In all cases, direct import from my Canon Vixia HF G10 camcorder into FCPX (latest version) produces the “weird glitches” upon playback in FCPX or from exported (.m4v) video files.

The Apple rep will also try to observe the glitches from his test iMac with the camera archive file I have provided to him, as another example on a separate system. He suspects that the “non-standard” AVCHD codec from Canon might be at issue when Mojave was updated to Catalina (“something may have fallen through the cracks” in video codecs).

I am asking anyone reading this thread, who has upgraded to MacOS Catalina, to repeat those processes which led to the “weird glitches” in the past to see if this is also reoccuring for you, and please report back in this thread. Thanks.