View Full Version : 7D Plugin for final cut has been released


Declan Smith
March 19th, 2010, 02:12 PM
It's here

Canon EOS 7D Digital SLR (http://www.usa.canon.com/consumer/controller?act=ModelInfoAct&tabact=DownloadDetailTabAct&fcategoryid=314&modelid=19356)

David Chapman
March 19th, 2010, 03:12 PM
And it came in time for my birthday! Thanks, Canon.

Now, if only I hadn't rented out my 7D kit today. Craaaaaaaap.

Andy Wilkinson
March 19th, 2010, 04:11 PM
Interesting. So, if I've read it correctly, this allows me to ingest 7D .mov files "at high speed" into FCP. Will this be any quicker than what I do now - copy onto a RAID and then convert to ProRes in Compressor on my Mac Pro?

David Chapman
March 19th, 2010, 04:26 PM
It should be a lot quicker than Compressor since even MPEG Streamclip is faster. I'm going to test all 3 later on tonight.

David Chapman
March 19th, 2010, 04:31 PM
From the requirements, it looks like you have to have Snow Leopard 10.6.2 and later with either FCP 6.0.6 (last update in FCS2) or FCP 7.0.1.

I'm going to see if Leopard and FCP 6.0.6 get me anywhere. If not, Snow Leopard is only $30.

Declan Smith
March 19th, 2010, 05:22 PM
Initially I couldn't get this plugin to work as FCP kept telling me that there no files in the correct format or directory structure, even though there were. What I was trying to do was load in previously backed up 7D movie files that I had on my hard disk. However, I had deleted all those .THM files, which contain not only meta data, but a small jpg clip of each movie file. The plugin is expecting to find these as that's what it uses to build the thumbnails.

So, If like me you made the mistake of deleting all the .THM files, you will need to grab a valid .THM and copy it to the same filename (but with a .THM extension).

i.e. MOV_1234.MOV, then copy any valid .THM to MOV_1234.THM

Note that the thumbnail will be wrong but at least you will be able to ingest the file.

So now I will make disk images of my SD cards before I do anything else, and back those up.

Bryan McCullough
March 19th, 2010, 08:58 PM
Interesting that this plugin doesn't support the T2i. I get the same directory structure error mentioned above.

I wonder if I used a thm file from a 7D and put it in my file structure if it would work. Anyone want to send me a thm file?

James Miller
March 20th, 2010, 01:11 AM
Initially I couldn't get this plugin to work as FCP kept telling me that there no files in the correct format or directory structure, even though there were. What I was trying to do was load in previously backed up 7D movie files that I had on my hard disk. However, I had deleted all those .THM files, which contain not only meta data, but a small jpg clip of each movie file. The plugin is expecting to find these as that's what it uses to build the thumbnails.

So, If like me you made the mistake of deleting all the .THM files, you will need to grab a valid .THM and copy it to the same filename (but with a .THM extension).

i.e. MOV_1234.MOV, then copy any valid .THM to MOV_1234.THM

Note that the thumbnail will be wrong but at least you will be able to ingest the file.

So now I will make disk images of my SD cards before I do anything else, and back those up.

The time code data is set by the THM file, so whilst you can ingest and convert the clips the time code start point will be the same. Have a look on the 5Dmk2 thread.

Declan Smith
March 20th, 2010, 02:21 AM
Ok, after realising my mistake of deleting the .thm files, and after some trial and error, I thought I would put together, what I think , is a useful workflow for backing up ad card captures in a similar way to tape, and capturing using the new plugin. (I think I had too much coffee last night)!

Anyway I hope this is of some use and interest to others
YouTube - Canon 7D Final cut pro EOS plugin Ingest Workflow (http://www.youtube.com/watch?v=1fqTxX1zamo)

James Miller
March 20th, 2010, 03:55 AM
Remember you don't have to make a disk image as Canon instruct, just create a folder called 'DCIM' you can put multiple sub folders in here as long as they contain .MOV and .THM files from the supported cameras. You just eject the folder from the transfer window when you are done.

As for support fro the 550D, would be nice is someone like 'Glue Tools' would produce a small app that would convert the .THM into the correct format. Shame that Canon have yet to support the plugin with a camera that supports the same video formats as the 7D. May be they will.

Extract taken from the .THM file below:
--------------------------------------------
ˇÿˇ·6Exif

James Miller
March 20th, 2010, 03:59 AM
My post above goes funny when I try and add the few lines of code.
Attached here is a txt file of the full post.

James Miller
March 20th, 2010, 04:23 AM
Here is a generic .THM if you want to test with your 550D. (zipped for integrity)

Date timecode set at 12:00:00

Craig Campbell
March 20th, 2010, 06:51 AM
I thought there was to be a way to read the 7D's clips extended metadata with this plugin, if so can't seem to find it...

Declan Smith
March 20th, 2010, 09:46 AM
Remember you don't have to make a disk image as Canon instruct, just create a folder called 'DCIM' you can put multiple sub folders in here as long as they contain .MOV and .THM files from the supported cameras. You just eject the folder from the transfer window when you are done.

You are quite right, you can load from any folder if the .thm and .mov files are there. I describe a workflow that works for me and is simple to setup and use. I even copy over an empty dir, for no other reason than it's cheap to do so and makes the workflow simple.
I wanted a simple system to reference the original media in a similar way to a tape workflow and cataloging. Of course the important thing is to make sure you have a reliable backup of your original media. Single file dmg files are easy to copy around and when mounted, act much like the original sd card. Also not sure if you reset file numbering in camera and then had two files on the same drive with the same name, how fcp would deal with that, so I felt it would be safer to just backup the entire sd image.

Christofer Thelin
March 20th, 2010, 01:47 PM
Interesting that this plugin doesn't support the T2i. I get the same directory structure error mentioned above.

I wonder if I used a thm file from a 7D and put it in my file structure if it would work. Anyone want to send me a thm file?

I guess that is a way for Canon to limit the experience for T2i users, as you said.. The 7D and 550D seams to have the same video codec built so there should be no issue with the plugin..

The initative to use a 7D for holiday-pros becomes greater with a better workflow.. But on the other hand just use batch convert in compressor and set a smart folder and you get the same result ;)

(Still I want it to work with the plugin..)

David Chapman
March 20th, 2010, 05:12 PM
I rented out my 7D yesterday so I wasn't able to play with the plugin, but I was excited to see it released before my birthday. I got my camera back today, but my only Intel machine (macbook pro) died today and Apple needs it for a week.

Happy birthday indeed.

Kelly Langerak
March 21st, 2010, 10:42 AM
I get the same unsupported error. I took the images from the compact flash card and copied everything over to a 32gig usb stick and then dropped them onto my hard drive. I have the mov file with the .THM file beside it. What am I doing wrong?

Final Cut 7.0.1
Snow 10.6.2

Declan Smith
March 21st, 2010, 05:12 PM
Make sure the directory structure mirrors the Canon 7D card. I seem to have problems when it doesn't.

i.e. when you copy them over to another disk, make sure it's like:

Chuck Spaulding
March 22nd, 2010, 09:52 AM
I'm sorry did I miss this? Does this plugin work with OSX 10.5.7 (Leopard)?

Alan Halfhill
March 22nd, 2010, 11:29 AM
Works on my system fine. About real time transfer. Still much faster transfers with Quicktime player. (It will put multiples in multiple cores.)

I really like the you can turn off channel two. I put has noise into it to defeat the AGC with a Juicedlink Jl-DN101 Adapter. Much better audio.

Colin Lahana
August 10th, 2010, 08:39 PM
Guys

I have just returned from a 6 week trip to Canada and Alaska and shot quite a few video clips as well as 3,000+ stills on my 5D MarkII. Unfortunately I managed to drop it along with a few lenses into the sea (in a so called waterproof bag) and destroyed them. Bummer. Just waiting for insurance on them now.

Anyhow during our trip I imported all the stills and movies into Aperture3 on a daily basis and have like other postees, lost the THM files, directory struture etc.

Does anyone know whether the movie clips lose any quality (ie compression) going into Aperture. I have just dragged the mov files straight into FCP and they play OK in the timeline at least.

cheers

Johannes Soetandi
August 11th, 2010, 12:02 AM
Ouch..

No I dont think you will lose quality. I've edited some videos that I imported via Aperture and still looks perfectly fine..

Chuck Spaulding
August 12th, 2010, 10:19 AM
You can compare the quality by importing them using MPEG StreamClip. If you crank the quality to 100 it was as good if not better than the Canon plugin.

And best of all its free. Squared 5 - MPEG Streamclip video converter for Mac OS X (http://www.squared5.com/svideo/mpeg-streamclip-mac.html)

Declan Smith
August 13th, 2010, 02:14 PM
Guys

Does anyone know whether the movie clips lose any quality (ie compression) going into Aperture.

cheers

The clips will be imported (copied) verbatim from the CF card into apertures library with no loss of quality. You are best advised to transcode the clips from H.264 into an editing codec (like Prores 422 LT) before editing them in FCP.

You obviously need to take care with settings when transcoding to ensure the highest possible quality. You can use compressor or Mpeg Streamclip to accomplish this. If however you want to re-construct, as it were, your CF cards and use the EOS plugin, then you will need to to ensure that you store the files in a nested tree with the folder DCIM/xxxxxxx where xxxxxxx is the folder name, like 100EOS7D. You will also need a THM file for each clip. As you don't have these, then you can copy any valid THM but remember to match up the filename. i.e. if your MOV is call MVI_1234.MOV then your must have a matching THM called MVI_1234.THM. Although the meta information and the thumbnail will be wrong it should be sufficient for the EOS plugin to recognise it.