This discussion is archived
3871 Views 10 Replies Latest reply: Oct 13, 2008 8:21 PM by Linnnnn
Currently Being ModeratedJul 21, 2008 11:43 PM (in response to swans101)It does not work because you have choosen the wrong metadate fields. For all this FCP Logging Stuff (works für Logging via Log and Transfer, not sure if it does for Log an Capture) you need to use the dynamic Metadata stuff, found at the very end of the long mapping list.
for Reel it is "reel (Dynamic Metadata)"... all the other mappings are down there, too.Mac Book Pro, Mac OS X (10.5.3)
Currently Being ModeratedJul 22, 2008 12:02 PM (in response to swans101)Swans101 and MarcS
Final Cut Pro doesn't write the Log and Capture Metadata to the Quicktime files. It make in a future release, but not currently. Log and Transfer does. Metadata mapping will work with Log and Transfer only.
Hope this helps.Mac OS X (10.4.7)
Currently Being ModeratedJul 22, 2008 9:43 PM (in response to Nicholas Stokes)Many thanks to Marc and Nicholas. Through your advice and testing I have successfully mapped the fields below only on log and transfer material. It would be so much more useful if this worked on everything, especially if Final Cut Pro logging within the browser would also translate.
One important discovery about all this: the mapping will only work on an asset's initial scan into FCSvr. If the file was already an asset before you created your metadata maps, those maps will not translate to the asset unless you delete the asset and rescan (full, not add only) the device. Also, if a metadata group assigned to the asset doesn't contain the fields you are mapping to and you decide to add those fields to the group later, you will have to delete the asset and scan the device again. Looks like heavy forethought is the general rule for FCSvr because you can't easily correct or adapt to new situations later!
From: reel (dynamic Metadata) To: Reel # (Custom Metadata) Priority: 3
From: logNote (Dynamic Metadata) To: Log Note (Custom Metadata) Priority: 3
From: scene (Dynamic Metadata) To: Episode/Segment (Custom Metadata) Priority: 3
From: shot (Dynamic Metadata) To: Shooting Location (Custom Metadata) Priority: 3
Biggest disappointment: I haven't found a way to map starting timecode of the file to any fields. That's a big one.Dual 2.7 G5, Mac OS X (10.4.11)
Currently Being ModeratedJul 31, 2008 9:44 AM (in response to swans101)I was so excited to see this post / solution on here since this is something I too have been battling. However, I logged into FCSrv to implement the workflow but I don't have those Dynamic Metadata Fields. When I sort my Metadata Fields by category and navigate to "Dynamic Metadata" I have the following:
The only Reel, logNote, Scene, and Shot fields I have are in the Final Cut Pro metadata which I was told cannot be used in the maps.
Any ideas where my "Dynamic" Reel, logNote, Scene, and Shot fields would be?
Thanks!Xserve, Mac Pro, G4, iMac, Mac OS X (10.5.3)
Currently Being ModeratedAug 1, 2008 1:18 PM (in response to ChristinaC)Christina,
Sorry for the delayed response, but here's what I know. The Dynamic MD you're interested in is all the way down at the bottom of the list of the "From Field" pull down menu when you go to create a Metadata Map. I'm not sure where else it might or might not appear, but I know it is there on my system. I also found the timecode field I was looking for and it's already mapped by default! It is called Timecode Offset (Custom Metadata) and shows an approximate starting timecode of the file. It seems to be a little off, but I've read about problems like that in other forums. Guess the rule is to use the TC in Final Cut Server as a close estimate rather than a frame accurate representation for now. Hope this helps!Dual 2.7 G5, Mac OS X (10.4.11)
Currently Being ModeratedAug 8, 2008 1:31 AM (in response to swans101)Dynamic metadata is Quicktime metadata. That is, QuickTime 7 metadata fields get automatically turned into FCSVR Dynamic metadata. This happens when FCSVR sees the field for the first time. You have to send at least one QuickTime movie in (that has the appropriate fields) before FCSVR will "know" about them.MacBookPro, Mac OS X (10.5.3)
Currently Being ModeratedOct 9, 2008 9:21 AM (in response to andiron)Is this for L&T only? I am trying to test mapping the Reel number (on the QT) to FCSvr Assets that were captured via L&C (not L&T). No joy so far. Anyone got Log & Capture info mapped yet?
CheersMP Dual 2.66GHz 7GB, iPhone 3G, Nano(3rd Gen), Mac OS X (10.5.4), Final Cut Server 1.1, Final Cut Studio 2
Currently Being ModeratedOct 13, 2008 8:03 AM (in response to Matt McM)Thanks Matt but I am trying to the Reel to stick right now which does stick to the QT. Thats why I was wonding but it doesn't seem it is possible to have the Reel displayed.MP Dual 2.66GHz 7GB, iPhone 3G, Nano(3rd Gen), Mac OS X (10.5.4), Final Cut Server 1.1, Final Cut Studio 2
Currently Being ModeratedOct 13, 2008 8:21 PM (in response to subquestion)unfortunately even though "Reel" is written onto the disk (you see the same info anytime you bring a clip into the FCP Browser of any project, and if you change it you get a warning that the changes will overwrite the current info on the disk)...this Reel metadata is not the same as the metadata you would get from say the FCP Log and Transfer window. It is not part of the QT metadata container in the same way. You can tell by just looking at any clips metadata, it is not revealed there (I have an app which displays/pulls the metadata and Reel didn't show up) and therefore FCSVR won't be able to see it of course...which is why no dynamic metadata showed up in the clip within the Search All Devices window...so ultimately Reel cannot be mapped.
As I mentioned in another post, you can search for Reel via Log and Capture by just making a Smart Search. In the Asset Advanced Search tab, just toggle the Metadata Filtering lookup to be "Include Log & Capture Metadata" and then search for your reel name and it should pop up. You can do the same in the Element's Search tab too (just in the regular search, you don't have to expand the advanced one).Mac OS X (10.5.5)