Skip navigation
This discussion is archived

Metadata Mapping doesn't function

3871 Views 10 Replies Latest reply: Oct 13, 2008 8:21 PM by Linnnnn RSS
swans101 Calculating status...
Currently Being Moderated
Jul 21, 2008 3:06 PM
I read the manual and followed it step by step. I'm able to create maps but no information actually maps. I've tried several different maps with no success, but most important to me is the ability to map FCP logging info or quicktime data (reel # & timecode start/stop) to some sort of searchable/listable field. Here's a specific:

Created a custom field called "Reel #"
Mapped the following:
From Field: Reel # (Custom Metadata)
To Field: Reel (Final Cut Pro Metadata)
Priority: 3
Two-Way Mapping unchecked

I have also tried the reverse of that and a few different priority levels. Even if I assign the Reel # field to an FCP element I can't get it to translate. It seems like if this info is embedded into the quicktime file, I should be able to map to QT metadata but I can't find any QT fields in the mapper. Anyone had any success with this or in making the FCP/QT metadata more useful in general?
Dual 2.7 G5, Mac OS X (10.4.11)
  • Marc.S Calculating status...
    Currently Being Moderated
    Jul 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)
  • Nicholas Stokes Level 2 Level 2 (490 points)
    Currently Being Moderated
    Jul 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)
  • ChristinaC Calculating status...
    Currently Being Moderated
    Jul 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:
    - Album
    - Artist
    - Author
    - Comment
    - Copyright
    - Description
    - Director
    - Information
    - Keywords
    - Producer
    - Software
    - Title
    - Year
    - cmmt
    - desc
    - name
    - uuid

    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)
  • andiron Calculating status...
    Currently Being Moderated
    Aug 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)
  • subquestion Calculating status...
    Currently Being Moderated
    Oct 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?

    Cheers
    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
  • Matt McM Level 1 Level 1 (65 points)
    Currently Being Moderated
    Oct 10, 2008 6:22 PM (in response to subquestion)
    Yes, this is correct. The metadata is written to the quicktime files only if Log and Transfer is used, not Log and Capture.
  • subquestion Level 1 Level 1 (85 points)
    Currently Being Moderated
    Oct 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
  • Linnnnn Level 1 Level 1 (130 points)
    Currently Being Moderated
    Oct 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)

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.