Creative COW SIGN IN :: SPONSORS :: ADVERTISING :: ABOUT US :: CONTACT US :: FAQ
Creative COW's LinkedIn GroupCreative COW's Facebook PageCreative COW on TwitterCreative COW's Google+ PageCreative COW on YouTube
BLOGS:My COW BlogAdobe BlogMacWorldEditingTechnologyAfter EffectsFinal CutEntertainment

A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.

COW Blogs : Jeremy Garchow's CowBloggie : A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
Share on Facebook
**PLEASE READ COMMENTS FOR HELPFUL UPDATES ABOUT ORIGINATING DSLR BACKUPS TO DISK IMAGES

It has now come up a few times on the FCP forum here at the cow, that the E1 Log and Transfer plug in is a bit faulty when it comes time to restore or move a Canon project to different machines and hard drives.

Cow user Jesse Hicks pointed it out and Ken Lowrie posted a potential work around here:

http://forums.creativecow.net/thread/8/1115207

Basically, the log and transfer plug in will not restore a project if the file path has changed from the point of the original log and transfer. The E1 plugin can't recognize the clip and volume names through log and transfer, especially if you have renamed/logged the clips in the L&T window to something useful. Upon trying to restore the project, you will get a warning like this:



No amount of adding the volumes, searching for media or anything will allow the L&T plug in to recognize the media if it has moved. Only the original file path will allow to restore a connection to the original Canon media. For those of you who work on one hard drive and one computer all the time, then you have nothing to fear, carry on. But for those us who work on multiple machines/hard drives, multiple locations and generally move things around, please read forward. Here's some potential situations where this might come to bite you:

-If you need to move your Canon DSLR project to another machine and you don't want to move all of the resulting ProRes files, you will not be able to relog and transfer the footage. That is to say, if you start the log and transfer process in the field on one computer or hard drive, then send it to another machine back in the studio to another hard drive, you will not be able to relog and transfer the logged footage from the original project.

-If you have already finished and archived a project, and need to go back to it (and you didn't save the log and transferred ProRes files in your archive) you won't be able to relog and transfer the footage and reconnect to the original project.

-If you were planning on doing an offline/online with your DSLR footage, this is now not possible with the Log and Transfer plugin and different machines. For example, if you off-lined in ProRes Proxy and want to online in whatever flavor of ProRes on another machine with a different hard drive structure, you won't be able to.

If you notice Ken Lowrie's instructions from the post I linked to earlier, he had to rename the volume on which the DSLR footage is sitting. While for some this might be possible, but for others this is entirely impossible. Imagine trying to relog and transfer to a SAN and had to rename the SAN! Yikes.

Another potential work around would be to use VIdeo Tool Shed's, FcpReconnect (http://www.videotoolshed.com/product/41/fcpreconnect/3). Using this method, you could relog and transfer the footage with default file names and be able to reconnect to whatever version you need. The trick here is that the original files and the newly log and transferred files must have same tc and reel name. The "TC" and reel names get assigned as part of the Log and Transfer process in FCP from the E1 plugin. As we all should know, Canon DSLR footage has no assigned tc when you shoot it but rather the tc is created form the date/time stamp in the THM file. Reel names are created from the folder that the original footage resides in.

I have included a picture of the bin that shows this method will work if you have not renamed the original folder structure of the Canon DSLR files:



If you have renamed the folders (which is now the reel name), you will have to rename the current folder to the one that was originally assigned upon the very first log and transfer. OR if you don't want to rename the reel to match, you could use another Video Tool Shed product called QtChange to add reel names after the log and transfer but before using FcpReconnect. After the reel and tc match between the two file sets, FcpReconnect will be able to reconnect the footage to the newly logged and transferred files regardless of the names of the files in the Finder.

Hopefully, an update to the E1 plugin will fix all of this because as of right now, it's a royal pain.

A little update for you on 1/31/2011

FcpReconnect works great (with a quick update from Bouke to get 720p59.94 working).

I had to re log and transfer a project from a coworker and the only thing available was the original project, and the camera original media in the proper file structure. The project was originally logged and transferred from a drive that was with my coworker who was on the road.

What I had to do was Log and Transfer all the footage in it's entirety with the default file names. You then export a batch list of all the offline clips in the project. FcpReconnect then analyzes the batch list and the recently logged and transferred clips. At that point you have the option to rename the media (to match the logged information) or move it and rename it. I simply renamed it. You then return to FCP and run the reconnect process. Since the names (and reels) now match, FCP connects with no issue. Pretty handy and saved a lot of manual "match by hand" work. Thank you VideoToolShed!

Another update on 2/1/2011

In one of the comments I suggested trying to use QtChange in the h264 files first. Unfortunately, this causes L&T to crash so I cannot recommend this. FcpReconnect is the way to go for restoring your offline DSLR projects that weren't coming from disk images. You can use QT change to add TC from the THM files from transcoding applications that don't support THM files. For example, if you use MPEG Streamclip to transcode your h264 files to ProRes with original file names, you can tell QtChange to use the information from the THM files to add tc. You can then use FcpReconnect provided you have entered the proper reel names for the clips. It's tough, I know, but the tools listed do work!

Jeremy

Posted by: Jeremy Garchow on Jan 17, 2011 at 9:49:04 amComments (24) Canon DSLR, Log and Transfer
Reply   Like  
+3
Share on Facebook

Comments

Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Elliott Balsley
They were originally captured with the current plugin version 1.2. But if I understand what you're saying, I think this might work: make clips offline, then re-capture all the media to a new folder, then just reconnect and point it to the new folder. It's not as automated as L&T, and it will take longer to re-capture all clips instead of only the ones I need, but I think that should work at least.
@Elliott Balsley
by Jeremy Garchow
Did you try and right click the clips in browser or timeline and 'batch capture'?

--

You can follow my twits
Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Elliott Balsley
They were originally captured with the current plugin version 1.2. But if I understand what you're saying, I think this might work: make clips offline, then re-capture all the media to a new folder, then just reconnect and point it to the new folder. It's not as automated as L&T, and it will take longer to re-capture all clips instead of only the ones I need, but I think that should work at least.
Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Elliott Balsley
I don't think disk images are a complete solution. I'm currently trying to online a project which was shot on Canon 7D. Six months ago, I archived all the CF cards to read-only dmg's, which is my normal workflow. I cut the project in ProRes proxy, and now I'm having trouble re-capturing as 422 HQ. I mount the dmg's and they show up in L&T, but all the grey circles are empty, so it doesn't recognize they have been captured. Therefore, of course, batch capture will not work.
Graham's idea seems to make sense — that by archiving the original media to disk images, the path will never change — but I am still having the problem. Or maybe it's a different issue. Any ideas?
@Elliott Balsley
by Jeremy Garchow
Have you tried to recapture?

If these were first captured with the old log and transfer plug, you might have to reconnect.

Do you have the latest log and transfer plugin?

--

You can follow my twits
Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Neil Sadwelkar
From what ive understood, the EOS L & T plugin 'assigns' a TC to each converted clip by looking at the 'time of day' in the THM files. When you recapture, it does the same so it can find the same clip again. But the original h.264 file out of the camera is not 'striped' or modified. Right?

So, if you edit in FCP and then send out an EDL to Baselight or Resolve, they can't reconnect to the H.264 'camera files', as the original files don't carry TC. So you have to use the ProRes files.

What I've done recently for a full length feature was to take each days rushes, make a copy, and then take these copies into QTChange where I striped them with TC one hour increment each day of shoot. And set the Reel name as folder name. So the original files (actually copies) were modified.
Copies were made as a measure of safety.

After the edit, the files were sent to Baselight with an EDL And it all reconnected fine. Even motion effects, reverse, etc.

-----------------------------------
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India
@Neil Sadwelkar
by Jeremy Garchow
Yes, Neil. But you wouldn't be able to L&t those new h264 files with Fcp. Also, if the original file path changes, the l&t process won't work as I've stated many times in this article. As a test, log and transfer a clip in Fcp. Now take it offline and delete media from disk. Go to the folder to where the orig h264 resides. Add a "z" to the encompassing folder name. Go back to Fcp and batch capture and it's busted.

Adding reel and tc info from QTchange us fine, but the eos plug won't like that media anymore. Also, Qt change will add tod tc from THM files so you can stamp it with that. You might have better harmony between the prores files and h264 files that way.
@Jeremy Garchow
by Neil Sadwelkar
My workflow did not need me to import Canon files into FCP via L & T. The files I 'striped' with QT Change were imported into Avid MC via an ALE that I made in Metacheater.

For FCP, I don't use L&T at all for Canon as it does not make the original files usable by any other system. I stripe the original H.264 files, use Compressor to batch convert them into ProRes and then simply drag the ProRes files into FCP. These converts don't have the compressor preset suffixed top their name.

So my ProRes converts and original H.264 are named identically. (But labelled by root folder/volume name). Now, if I ever need to go back to the H.264 files from FCP, then a simple reconnect works since they have identical file name, reel name and time code.

I have to stress here that I do not stripe the originals that came out of the camera. I make a copy first.

Before striping TC, I also conform the 23.98 fps to 24 fps in CinemaTools and mod the sound by 0.1% to match, but that's another story.

-----------------------------------
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India
@Neil Sadwelkar
by Jeremy Garchow
Got ya. You are talking about a totally different workflow.
Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Tucker Starr
We have run into similar, but not identical problems with the Canon Log and Transfer plugin. A little background here:

http://forums.creativecow.net/readpost/8/1113918

Since having that problem (incompatibility between files transferred using the old version when trying to batch capture using the new plugin, and vice versa), we have reverted back to the using the old plugin (v1).

We have not run into problems batch capturing using L&T plugin, even when moving files to a different disk, or to or from our SAN.

HOWEVER, we have run into a a dead-end trying to batch capture from original Canon files that have been archived to LTO and then un-archived back to our SAN (or local disk) and have isolated this problem to the "date created" of the original MOV file having changed during the back and forth to/from LTO. The L&T plugin WILL NOT recognize the reel as being mounted if the Quicktimes have different "date created" (which happens as a result of the FTP protocol used to transfer data to LTO.

Anyone else seen this?
Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Jeremy Garchow
[Tucker Starr] "Since having that problem (incompatibility between files transferred using the old version when trying to batch capture using the new plugin, and vice versa), we have reverted back to the using the old plugin (v1)."

I've tried with v1 and v1.1. Same results. It only matters on where you started the log and transfer. If that changes, the plug in will fail. For example, if I have all the DSLR files in a folder on my raid called "Footage to transfer" and then log and transfer, if then take those files offline, rename the folder to "footage" the log and transfer function will fail. The file path must remain the same. If you can get this to work with changing the file path from the point of the original log and transfer, please do tell.

[Tucker Starr] "The L&T plugin WILL NOT recognize the reel as being mounted if the Quicktimes have different "date created" (which happens as a result of the FTP protocol used to transfer data to LTO."

What LTO system do you use? I haven't tested this particular workflow coming from our Cache-A, but since the plugin is so busted anyway, it's not surprising.
@Jeremy Garchow
by Tucker Starr
We seem to be fine moving files around to different volumes, as long as the name of the folder that contains the DCIM folder stays the same. The only time we are having problems is when the "date created" of any of the Quicktime files changes.

The LTO we're using is Quantum LTO3 A Series - the problem isn't the LTO itself, but the fact that when we FTP transfer files to/from the LTO, it changes the "date created" on the files, which makes it so that the Canon L&T plugin won't recognize the reel as being the same reel anymore.
@Tucker Starr
by Jeremy Garchow
Wow, perhaps it has to do with how your volumes are mounted (you did say, SAN correct?). If I change one letter of the original file path, it's busted.

Can you give me an example of the file path?

The reason I asked about the LTO is that I don't use FTP, but rather Finder level operations to archive and restore. Doesn't seem to change much, but I will have to check that.
@Jeremy Garchow
by Tucker Starr
Example of file path we did just this morning:

We originally L&T'ed to ProRes Proxy from:
EXT05:Mountain:DSLR:MOU-012611:DCIM:100EOS5D

Then did our edit, MM'ed the sequence to offline media, and re-L&T'ed to ProResHQ from the new location, to where the files had been moved (on our XSAN)
UNIVERSAL:MEDIA:Mountain:DSLR:MOU-012611:DCIM:100EOS5D

Worked like a charm. Where it DOESN'T work for us is if there has been any change to the "date created" of the MOV file (which happens going to and from LTO), or if we try to use v1.1 on originally v1 captured media, or vice versa.
Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Robert Shaver
This workflow,





creates a mountable image for each media cartage (CF or SD)so I think it may solve this issue, at least for OS-X. The "drive" name would be the same and the path within it would be identical.
@Robert Shaver
by Jeremy Garchow
Thank you, Robert. This is definitely how to move forward with DSLR projects until the Canon Log and Transfer plug-in ever gets fixed.

Just to reiterate, if a project is already started/completed and someone is attempting to restore or online a particular set of files that were originally logged and transferred without disk images, one will still run into trouble if the file path has changed and is impossible to change/unknown to the original (although an XML might show the orig. file path, unable to check that at the moment).

Please keep all the suggestions coming, everyone.

Jeremy
Re: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Graham Hutchins
I believe there is a workaround for this.

If you create a disk image of each card (.dmg via either Disk Utility or I found a cool little app called DropDMG that will allow you to batch automate the process, though I'm sure there's a way to script this) before you log and transfer as part of your archiving workflow, you will have a mountable volume that will retain it's relative file path regardless of where the .dmg is saved.

You can move these .dmg files anywhere and the only way to access this data is to mount it and it will mount as a volume in the same place every time.

I've just finished testing this out and all you do is drag your disconnected clip from the browser onto the L&T window, the "Re-Import" dialog comes up, click OK, and then the missing volumes warning comes up. Don't click anything in the warning, just navigate to your corresponding disk image/reel that FCP is looking for and double click to mount it and the warning dialog goes away and the clip begins to import.

I've done this from 3 separate drives with copies of the same disk image and they all seem to work.

-Graham

Post Supervisor, Giant Pictures
@Graham Hutchins
by Jeremy Garchow
Awesome, Graham. Thanks a lot for the response and the sleuthing.

But this is still contingent on having done this BEFORE you have logged and transferred, is that correct?

Jeremy
@Jeremy Garchow
by Graham Hutchins
Correct.

I have also had a chance to try this out on separate systems with much success.
@Graham Hutchins
by Tory Stewart
I might be crazy, but after encountering this issue part-way through a project I made disk images of all my reels/cards and was planning to re-log & transfer all the media from the new disk images and connect all my old clips to the new media to avoid connection problems down the line. Before embarking on this mad scheme I mounted one of the new disks and tried to batch capture some of the existing clips I had already logged and transferred months ago without disk images, and it actually worked. Maybe this was a fluke but I've done it now with several batches of clips from multiple disks without incident.
@Tory Stewart
by Jeremy Garchow
Yes, it works if you don't change the file path/don't change machines. If everything is untouched, it will work if the media hasn't moved or changed file paths. Add one more letter to the file path, and it won't work.
Re: Blog: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Brian DeViteri
Wow. Some (professional) people are in for a HUGE headache if they follow standard media management following the conclusion of a project.

This almost makes it seem like people may be better off treating the Log & Transfer utility the same as they would MPEGStreamClip or 5DtoRGB for the meantime. At least with those conversion tools, you know what you're getting into from the start.

If you're meticulous and take extremely good notes (screen shots) of all your settings prior to conversion, it actually may be easier to recreate/relink your project using those tools - providing that you don't want to actually "Log" any of your footage prior to conversion...

I guess saving & archiving the ProRes422 files, along with the source is now going to be standard of practice for everyone.
Re: Blog: A few words of warning for the EOS MOVIE Plugin-E1 for Final Cut Pro users.
by Jeremy Garchow
[Brian DeViteri] "Wow. Some (professional) people are in for a HUGE headache if they follow standard media management following the conclusion of a project."

Bummer, ain't it?

At least with FcpReconnect, all you would need to figure out is reel name if both data sets were logged and transferred with THM files. Clip Name doesn't matter so much. The reel name seems to remain constant across multiple machines if you don't rename the encompassing folders.

The other thing to do would be to use QtChange to add reel and tc to the h264 files FIRST which might make it easier to reconnect to screwed up Log and Transferred ProRes files later.

It all depends if the encompassing folders (i.e. reel names) get changed. Otherwise FcpReconnect is all you would need.

At any rate, it's screwy.

Thanks for the response.

Jeremy
@Jeremy Garchow
by Jeremy Garchow
Earlier, I suggested trying to use QtChange on the h264 files first. Unfortunately, this causes L&T to crash so I cannot recommend this.



Blog Feed  RSS


FORUMSTUTORIALSFEATURESVIDEOSPODCASTSEVENTSSERVICESNEWSLETTERNEWSBLOGS

Creative COW LinkedIn Group Creative COW Facebook Page Creative COW on Twitter
© 2014 CreativeCOW.net All rights are reserved. - Privacy Policy

[Top]