Hi Rainer, thanks for your reply. I filed a bug (#12151320) for both issues. Thomas. MINDTRANSPLANT Audio & Video Produktion www.mindtransplant.com clipexporter.mindtransplant.com Am 21.08.2012 um 23:03 schrieb Rainer Standke:
Hello Thomas,
On Aug 21, 2012, at 12:57, Thomas - Mindtransplant <thomas@mindtransplant.com> wrote:
Hi,
there is a strange behavior that I´m not sure if it is intended or not. It would be nice if a Apple employee could provide some feedback:
When I use the right-click command "Break Apart Clip Items" on a video clip (not a compound clip) the <video> Node loses it´s <clip> parent Node. For example, this: <clip> <video> <audio/> </video> </clip>
Turns into this: <video> <audio lane="-1"/> </video>
The video node inherits the attributes from it´s previously deleted parent clip node and the audio node get attached to the video node. Now, if I delete the audio item in FCP X and select the video item and choose "New Compound Clip" it behaves as expected and creates a compound clip. The fcpxml equivalent now looks like this: <clip> <video/> </clip>
In FCP X I double click the newly created compound clip and take a look inside. Now I duplicate the video item inside the compound clip by holding alt and dragging it up to the 1st lane. If I leave the compound clip content view and return to the main timeline, the clip is no more a compound clip and I´m not able to view it´s contents. The fcpxml look like this: <clip> <video> < video/> </video> </clip>
My questions are: 1.) Is it a bug or is it intended that the parent clip node is deleted when using "Break Apart Clip Items" on a video clip? Since this behavior only occurs when breaking apart clip items I assume it´s a bug. This does not occur when appending or inserting video-only media from the Event Browser!
This seems to be no bug in the sense that Apple has recognized it as such. As a matter of fact, in my opinion, this is a bug in the sense that the same node (<video>) can have two different meanings, i.e. <video>, as in: video inside a clip, as well as <clip>, as in: it carries the relevant timing info. In my opinion this needlessly complicates parsing, and thus is also a dangerous thing. You might want to file a bug.
2.) If this behavoir is intended how do I differentiate a <video> node that is inside a compound clip and one that is inserted from the Event Browser? Both cases have the same xml structure. This differentiation is important to my app since it decides whether to create a comp layer in After Effects or not.
I guess you'll have to look at the XML structure several levels deep. It may suffice to check if your video node has a clip ancestor that itself has a clip ancestor.
3.) I assume that not being able to open the compound clip (as mentioned in the last part) is a bug, right?
That looks a lot like a bug to, although I haven't tried it myself. You should file a bug about that.
Hope this helps,
Rainer
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com