-
Log and Transfer Won’t Recognize Volume/Clip Names
Hello,
First I must say that my problem pertains specifically to Log and Transfer with the Canon DSLR Log and Transfer plugin, and I am not sure if it has to do with that plug in or FCP itself, as I haven’t been able to try to replicate the problem with other metadata, as I have none on hand at present. Anyhow, here goes:
I’ve been using the Log and Transfer plugin for the Canon DSLRs and I love it. I like being able to label all of my clips in the L & T window, save an archive folder for each card, and then keep all of the original metadata. One of the reasons I like this is because if I am done with a project that I likely won’t need to work on again, I can erase all of the ProRes data. Then, if I do need to work on that project again, I can open the FCP project, reingest the offline clips from the archived metadata, (since Log and Transfer will recognize the names of all the clips I labeled from the volume) and then my project is again complete and workable.
But I have noticed a little problem.
I have all my archived cards, in their original directory structure, in a folder on a hard drive. It’s called “Archived 5D Metadata.” If I open up one of these cards that I have already logged in the log and transfer window, it shows up with clip names, and an indication as to whether it’s been ingested, as it should.
But I wanted to move my entire archive folder to a new hard drive, so I did. If I mount that same archived card, with the same FCP project open, and the metadata having the same directory structure and original clips and thm files and everything, it no longer produces clip names in the L&T window. It still mounts in the L&T window, and it has the same reel name, which is the name of the archived folder, but it has the Canon produced clip names (MVI_####). Final Cut won’t recognize it as the same metadata or the same volume even though everything about it is the same, except for the hard drive it lives on.This makes the whole archiving capabilities of this plugin less useful, since you can’t move around your archived files without causing FCP to stop recognizing them.
Unless there is a way to make FCP realize this is in fact the same volume.
Any suggestions?
thanks
jesse
-
11 Replies
-
You should be able to select the offline clips in a bin and choose batch capture from the project.
Once the archived cards are loaded in the l&t window, fcp should begin transferring the media. The clip names get saved with the project, not the original media, and once the l&t process is complete you should have ProRes QT files that are named and online.
Jeremy
-
Thanks Jeremy,
If I try to re-ingest the clips, by batch capture or dragging a clip into the L&T window, it will only recognize the Volume that the clip came from if it is in the original place that I had it when I logged and transferred the clips.
For example, I have a folder on my desktop, from where I originally archived and logged the clips, called “Card1.” If I mount that Volume, Final Cut will re-ingest the logged clip. I can also see all the clips labeled in the Log and Transfer window. I have also copied “Card1” onto an external hard drive, where I want the folder to live.
When I do the batch capture, L&T asks me to find the volume “Card1” so that it can transfer the clip. If I point it to the volume, “Card1” on the external hard drive, it will not transfer. It doesn’t recognize it as the same volume even though the information inside it is identical. If I point it to the identical folder on my desktop, it will transfer the clip.
It’s not that the Card1 folder on the external hard drive won’t mount in Log and Transfer. It will, it just is not recognized as the same metadata that I logged these clips with, so I am stuck keeping the archive on my desktop.
Make sense?
-
You explain it well, so it makes sense that way, but i don’t think it shoud work this way. I think this is beginning to sound like a bug. This very same concern was brought up in another post not too long ago.
I have to do further testing on it myself. You didn’t happen to modify the canon plug in to accept t2i files, did you?
-
No. I didn’t modify the plugin. As soon as I get the chance I’ll see if I can replicate with P2 and other kinds of metadata.
-
P2works as expected as does everything else. I think this is limited to canon footage.
Once I get back to the office I’ll run some tests.
-
I am seeing this same issue. I haven’t tried it yet with the RED or P2 footage, since right now the projects I am working on are all Canon projects. However, hopefully this will get fixed, because it really does make workflow using the canon footage quite difficult.
I found a workaround that allowed me to get past the problem.
original volume name: data
original path to raw footage: /clp/snafu/acousticdemo/footage/pacv2/7darchived volume name: ken16c
archived path to raw footage: /snafu/acoustic/footage/pacv2/7dHere is how I got around it:
- renamed external volume from ‘ken16c’ to ‘data’
- recreate directory structure on archived volume to match original ingest path. so, i created /clp/snafu/acousticdemo/footage and moved the ‘pacv2’ folder and contents into it
- load log and transfer window, then mount the volume ‘7d’ inside ‘pacv2’
- go s
elect the clips in the final cut project window and hit Ctrl-C
And this worked just fine. Note that if I started log and transfer without the volume mounted (in other words skip step 3 and just try to batch capture and let the L&T missing volumes window come up), I could not get it to work, even though it recognized that the proper volume was mounted. It would just error out.
Hope this helps, and if anyone knows a way to make this work without going through this, please let me know. It’s a bit of a hassle to say the least…
-ken
-
Thanks Ken,
That does help.
So to be clear, you renamed the external drive to have the same name as the original one it was saved to?
Definitely a hassle, and it shouldn’t happen like that, in my opinion.
And Jeremy, you confirmed that this problem of not recognizing moved volumes DOES NOT happen with P2 metadata?
-
Hi Jesse:
Yes, I renamed the external volume to match the volume where I originally ingested from.
I also had to maintain the physical directory structure in use when it was originally ingested. At first, I tried renaming the volume, when that didn’t work, I rebuilt the directory structure to match. Then, it worked just fine…
-ken
-
Yes, P2 is solid. You select batch capture and fcp will bring in the files as you named them.
-
I just ran some tests and this is most definitely broken. It makes me nervous about restoring older projects in the future. I’d highly recommend writing Canon about this. P2 works as expected and is rock solid. This is a huge bug. There’s no way I would be able to rename any of my drives just for this reason.
Looking to see if there’s a newer version of the plug in now.
Jeremy
Reply to this Discussion! Login or Sign Up