eos-update-main.png

image

A test folder that I created and moved a few of the files into.

image

Both folders loaded into the version 1.2 plug-in.

I’m not exactly sure what camera these example files were shot with (folder says 100CANON) but the version 1.2 plug-in didn’t have any problems loading these clips up.

I installed this update on my system at home and tried to load some files from my Canon 7D but had a couple of issues. It seems that the plug-in no longer wants to load 7D clips that I have backed up forever using the proper directory structure:

image

The updated L&T plugin won’t load this 7D directory.

image

It returns this warning.

What is really strange is that I was able to remove the .THM files from the above directory and it did load the clips.

image

By removing the .THM files the updated L&T plug-in was able to load clips from my 7D backups that it wasn’t able to load before.

image

It will load media directly off a 7D CF card however.

As the release notes say, you will get “incomplete shooting information” when importing from a 7D with missing .THM files but from the looks of the Media Start and Media End columns after I removed the .THM files it’s still getting timecode from somewhere. What I like best about the update is that it appears to now load raw H.264 files that have been backed up without any specific folders structure and/or .THM files:

image

As you can see above there is no Canon directory structure or .THM files. Plus I had added a suffix to all these file names before backing them up.

This Canon EOS MOVIE Plugin-E1 for Final Cut Pro has been known to have a few problems for a while now. It’s most common problem has seemed to be not transcoding the entire file but I have never experienced that problem and I have transcoded many, many hours of footage. I prefer this plug-in over most other FCP transcode options when possible as it’s fast and it assigns both a reel name and timecode, two very important things to my editing workflow.

I guess what I really don’t understand is why can’t Canon make this plug-in always perform the same way and be compatible (without hacking) with all of their DSLRs that shoot video?

Support ProVideo Coalition
Shop with Filmtools Logo

You Might Also Like