FCPXML 1.2 Import behavior - Event Versus Project
FCPXML 1.2 Import behavior - Event Versus Project
- Subject: FCPXML 1.2 Import behavior - Event Versus Project
- From: Alex Wolfe <email@hidden>
- Date: Sat, 29 Dec 2012 16:25:19 -0600
Looking for confirmation on some metadata behavior observations, and what may be inconsistent behavior.
Observations:
The metadata contained on a project timeline clip is distinct from the metadata contained by the same clip in an event.
- If metadata is assigned in the event and the clip is then copied to the timeline, it inherits from the event.
- If metadata is assigned to the highlighted clip on the timeline, or to the highlighted clip in an event - it does not sync - they are held separately.
If importing a fcpxml event file - i.e. with the clip node following resource (stylized xml for example):
<project>
<resource/>
<clip>
<metadata/>
...
The metadata properties are mapped into the asset in the event as expected.
If importing using the project form (stylized xml for example):
<project>
<resource>
<projectref name="test event"/>
</resource>
<sequence>
<spine>
<clip>
<metadata/>
An event will be created for "test event", the clip will be present in both event and timeline, and the metadata will be present on the clip instance on the timeline, but *not* on the clip instance in the event.
According to the DTD you can insert the <metadata> tag underneath an <asset>, and I've tried doing that in the resource section - though in my testing that does not work in either the Event or Project XML mode.
In summary:
I can attach metadata to a clip in an event only if I import an Event XML.
If I import the metadata in a Project XML then the metadata is only tagged to the instance of the clip on the timeline, not to the clip in the event.
Questions:
Has anyone else noticed this? Am I mistaken?
If this is true, is Apple aware? Is this intentional? Bug or Feature?
Thanks
Alex
Elklight Technology, LLC
http://elklight.com
_______________________________________________
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