|**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:
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!