Re: Lane numbers in fcpxml
Re: Lane numbers in fcpxml
- Subject: Re: Lane numbers in fcpxml
- From: Piers Goodhew <email@hidden>
- Date: Tue, 11 Oct 2011 09:25:37 +1100
It does appear that you can rely on the fact that if two clips overlap temporally, the one with the highest lane number will be in front.
I'd assume that if you extended, e.g. C1 it would slide *under* C2 - normal fcpx behaviour. Would be interesting to see what happened if you extended a C clip in the imported project where they're all in the same lane (but it doesn't seem to hurt B does it...).
That's what seems reasonable to me, anyway. Official Apple clarification would be better of course.
PG
Sent from my phone, anything lewd or incomprehensible is probably autocorrect and not my fault.
----- Reply message -----
From: "Bruce Sharpe" <email@hidden>
To: "Pro-Apps-Dev" <email@hidden>
Subject: Lane numbers in fcpxml
Date: Tue, Oct 11, 2011 5:19 am
I am finding that lane numbers in fcpxml do not necessarily correspond to
what is displayed visually in the UI. For example, consider this layout
with clip A1 in the spine and clips Bn, Cn, Dn in lanes above the spine:
D1 D2 D3 D4
C1 C2 C3
B1 B2 B3 B4
A1
All the Bn clips have lane=1. I would expect all the Cn clips to have
lane=2, and Dn to have lane=3. But instead, the lanes of Cn are 2, 3, 4 and
those for Dn are 5, 6, 7, 8. Moreover, the lane numbers in a given visual
lane seem to be in random order.
If I construct XML with Cn=>lane=2 and Dn=>lane=3, it constructs a timeline
that looks the same as above, so it seems that import uses different rules
than export.
What are the rules for lane numbers? Is there a way to reliably infer the
lanes as displayed visually from the lane numbers in the XML?
Bruce
_______________________________________________
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