Re: FCPX input metadata mapping
Re: FCPX input metadata mapping
- Subject: Re: FCPX input metadata mapping
- From: Mark Gilbert <email@hidden>
- Date: Sun, 11 Nov 2012 20:49:18 +0000
Vlearly FCPx also supports other quicktime specific metadata for movies.
but there is an iXML implementation chart for FCP7 at:
http://www.ixml.info/compatible.html
http://www.ixml.info/FCP_ixml_implementation.pdf
It's possible or even likely that FCPX shares the same implementation
if anyone from Apple is reading this, please update the iXML implementation chart and submit it for update on the iXML specification website.
> Message: 1
> Date: Sun, 11 Nov 2012 12:18:03 -0600
> From: Alex Wolfe <email@hidden>
> To: email@hidden
> Subject: FCPX input metadata mapping
> Message-ID:
> <CAG2GG4Oc=z_6Gbghy9hZ80b8L0T=email@hidden>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Is there a list (exhaustive or otherwise) that indicates specifically what
> metadata from what sources FCPX will map into it's internal representation?
>
> I.e. "scene" appears to be represented internally as
> com.apple.proapps.studio.scene. I've found that if you stuff the iXML BWF
> metadata in a wav file that FCPX will map the /BWFXML/scene, reel, take,
> notes information from the iXML chunk. What other locations will FCPX map
> that info from? I.e. what quicktime keys would be mapped into
> com.apple.proapps.studio.scene. What AVFoundation metadata keys (I'm guess
> none). Is there user defined metadata with common forms that FCPX will try
> to map?
>
> Fundamentally what I'm looking for is a cannonical mapping document of
> quicktime/bwf/userdefine/proprietary/etc metadata keys to FCPX internal
> representation.
>
> Thanks!
> -------------- next part --------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden