August 2008 - Pro-apps-dev - lists.apple.com

Re: adding a clip to a bin via xml
by Helena Ju 29 Aug '08

29 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 29, 2008, at 7:10 AM, Tommy Schell wrote: Hi, To target a bin and not just a project, and append a clip to it. Thanks Tommy Schell _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/hju%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… Hi Tommy, Unfortunately, the way it is set up today, due to a flaw in the logic, one has to specify a bin and all its contents and do a replace. We are aware of the shortcoming. Is there a simple way to add a clip to a bin within an open Final Cut Pro project via xml, if the clip is described in a Final Cut Pro xml file? This email sent to hju(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

adding a clip to a bin via xml
by Tommy Schell 29 Aug '08

29 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, To target a bin and not just a project, and append a clip to it. Thanks Tommy Schell _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… Is there a simple way to add a clip to a bin within an open Final Cut Pro project via xml, if the clip is described in a Final Cut Pro xml file? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Compressor flags for chapterized .m4v
by Frank Jonen 29 Aug '08

29 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Compressor flags for chapterized .m4v
by Frank Jonen 29 Aug '08

29 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Point parameters when applied to shape layers
by Darrin Cardani 28 Aug '08

28 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Darrin On Aug 27, 2008, at 9:54 PM, Garrick Meeker wrote: On Aug 27, 2008, at 5:21 PM, Darrin Cardani wrote: Darrin On Aug 27, 2008, at 5:01 PM, Garrick Meeker wrote: get point: -0.567039 1.398438 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: 0.013514 0.981308 0.395413 0.395413 361 257 get point: 0.500000 0.500000 0.395413 0.395413 361 257 get point: -0.297297 1.172414 0.077779 0.077779 475 372 get point: 0.500000 0.500000 0.077779 0.077779 475 372 get point: 0.031250 0.958333 0.158203 0.158203 379 271 get point: 0.500000 0.500000 0.158203 0.158203 379 271 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.530316 1.398437 1.000000 1.000000 358 256 get point: 0.536723 0.500000 1.000000 1.000000 358 256 get point: -0.530316 1.398437 1.000000 1.000000 358 256 get point: 0.536723 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.263399 1.172414 0.077779 0.077779 475 372 get point: 0.533898 0.500000 0.077779 0.077779 475 372 get point: 0.065148 0.958333 0.158203 0.158203 379 271 get point: 0.533898 0.500000 0.158203 0.158203 379 271 On Aug 27, 2008, at 4:35 PM, Darrin Cardani wrote: On Aug 27, 2008, at 4:05 PM, Garrick Meeker wrote: Thanks, Darrin -- Darrin Cardani dcardani(a)apple.com -- Darrin Cardani dcardani(a)apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… Wow! That's nuts! Thanks for tracking this down! I've filed this bug (for future reference): <rdar://problem/6182337> Filters: Point parameters on pixel independent filters go haywire if applied to shape I finally tracked it down. Apparently setting kFxPropertyKey_PixelIndependent = YES in properties will cause point values to go haywire when applied to a shape layer. Garrick, That doesn't make a whole lot of sense to me. The .39... scale is because it's drawing a preview either in the timeline, the layer list, or the inspector window. But I don't see any reason why the point parameter would change its value. Looking at the filters that ship with Motion, Fisheye and Droplet have point parameters that seem to work as expected. Are you getting back a valid value for the FxParameterRetrievalAPI object? Here's my printf's showing x and y from getXValue, x and y scale, width, and height. The odd lines are from renderOutput and the even lines (that around about 0.5) are from inside frameCleanup. It's applied to a simple rectangle shape that covers about half of a DV frame. Does this make any sense? I seem to be getting inconsistent and bogus values from getXValue when my FxPlug filter is applied to a shape layer in Motion 3. Has anyone seen this? I don't have time to make a simpler test case right now. Can you elaborate on how they are "inconsistent and bogus?" In what way are they different from what you expect? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Point parameters when applied to shape layers
by Darrin Cardani 28 Aug '08

28 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Darrin On Aug 27, 2008, at 7:10 PM, Garrick Meeker wrote: On Aug 27, 2008, at 6:07 PM, ben syverson wrote: Do you absolutely need to access the point value during frameCleanup? - ben On 27 août 08, at 19:01, Garrick Meeker wrote: -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… Would it be possible to post a short code snippet? From your description, it sounds like everything should be working, but maybe there's some minor thing you're not seeing in the code. Alternatively, if you want to send me the built plugin, I can at least see what Motion's doing internally. frameCleanup is when it works as I'd expect. It's renderOutput that's giving weird results. I've found that there are certain parts of the API that don't necessarily work as expected in some methods. It would be nice if they simply returned an error instead of returning strange values, but it's not a huge deal if you know what works where. Here's my printf's showing x and y from getXValue, x and y scale, width, and height. The odd lines are from renderOutput and the even lines (that around about 0.5) are from inside frameCleanup. It's applied to a simple rectangle shape that covers about half of a DV frame. Does this make any sense? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Point parameters when applied to shape layers
by Garrick Meeker 28 Aug '08

28 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 27, 2008, at 5:21 PM, Darrin Cardani wrote: Darrin On Aug 27, 2008, at 5:01 PM, Garrick Meeker wrote: get point: -0.567039 1.398438 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: 0.013514 0.981308 0.395413 0.395413 361 257 get point: 0.500000 0.500000 0.395413 0.395413 361 257 get point: -0.297297 1.172414 0.077779 0.077779 475 372 get point: 0.500000 0.500000 0.077779 0.077779 475 372 get point: 0.031250 0.958333 0.158203 0.158203 379 271 get point: 0.500000 0.500000 0.158203 0.158203 379 271 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.567039 1.398437 1.000000 1.000000 358 256 get point: 0.500000 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.530316 1.398437 1.000000 1.000000 358 256 get point: 0.536723 0.500000 1.000000 1.000000 358 256 get point: -0.530316 1.398437 1.000000 1.000000 358 256 get point: 0.536723 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.533141 1.398438 1.000000 1.000000 358 256 get point: 0.533898 0.500000 1.000000 1.000000 358 256 get point: -0.263399 1.172414 0.077779 0.077779 475 372 get point: 0.533898 0.500000 0.077779 0.077779 475 372 get point: 0.065148 0.958333 0.158203 0.158203 379 271 get point: 0.533898 0.500000 0.158203 0.158203 379 271 On Aug 27, 2008, at 4:35 PM, Darrin Cardani wrote: On Aug 27, 2008, at 4:05 PM, Garrick Meeker wrote: Thanks, Darrin -- Darrin Cardani dcardani(a)apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I finally tracked it down. Apparently setting kFxPropertyKey_PixelIndependent = YES in properties will cause point values to go haywire when applied to a shape layer. Garrick, That doesn't make a whole lot of sense to me. The .39... scale is because it's drawing a preview either in the timeline, the layer list, or the inspector window. But I don't see any reason why the point parameter would change its value. Looking at the filters that ship with Motion, Fisheye and Droplet have point parameters that seem to work as expected. Are you getting back a valid value for the FxParameterRetrievalAPI object? Here's my printf's showing x and y from getXValue, x and y scale, width, and height. The odd lines are from renderOutput and the even lines (that around about 0.5) are from inside frameCleanup. It's applied to a simple rectangle shape that covers about half of a DV frame. Does this make any sense? I seem to be getting inconsistent and bogus values from getXValue when my FxPlug filter is applied to a shape layer in Motion 3. Has anyone seen this? I don't have time to make a simpler test case right now. Can you elaborate on how they are "inconsistent and bogus?" In what way are they different from what you expect? This email sent to site_archiver(a)lists.apple.com

1 0

NSXMLDocumentTidyXML codec issue
by Gregory Clarke 28 Aug '08

28 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi list, Greg. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I've found a problem using NSXMLDocumentTidyXML to clean up XML for FCP. My altered sequence XML ends up being a bit messy, so I've passed it through NSXMLDocumentTidyXML and then NSXMLNodePrettyPrint to give me good looking easily foldable XML code. This has never been a problem with my PAL DV footage, which has a <codecname>Apple DV - PAL</ codecname> codec with code <codectypecode>dvcp</codectypecode>. However my first try with NTSC footage caused FCP to warn that there is a codec missing and the sequence refused to open. This is followed by an "out of memory" error message. The codec was <codecname>Apple DV - NTSC</codecname> with code <codectypecode>dvc </codectypecode>. Note the space in the codectype. After NSXMLDocumentTidyXML the trailing space had been stripped from the 4 letter codectypecode, so FCP would no longer recognize the sequence's codec. If I just give FCP my un-tidied XML it's happy. I don't think this is a bug with NSXMLDocumentTidyXML since it's no doubt meant to tidy that extra space. Since I've already got a work- around, this is more of a heads-up for other XML users on the list. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Point parameters when applied to shape layers
by Garrick Meeker 28 Aug '08

28 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 27, 2008, at 6:07 PM, ben syverson wrote: Do you absolutely need to access the point value during frameCleanup? - ben On 27 août 08, at 19:01, Garrick Meeker wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarch… _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… frameCleanup is when it works as I'd expect. It's renderOutput that's giving weird results. I've found that there are certain parts of the API that don't necessarily work as expected in some methods. It would be nice if they simply returned an error instead of returning strange values, but it's not a huge deal if you know what works where. Here's my printf's showing x and y from getXValue, x and y scale, width, and height. The odd lines are from renderOutput and the even lines (that around about 0.5) are from inside frameCleanup. It's applied to a simple rectangle shape that covers about half of a DV frame. Does this make any sense? This email sent to garrick(a)digitalanarchy.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Point parameters when applied to shape layers
by ben syverson 28 Aug '08

28 Aug '08

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Do you absolutely need to access the point value during frameCleanup? - ben On 27 août 08, at 19:01, Garrick Meeker wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I've found that there are certain parts of the API that don't necessarily work as expected in some methods. It would be nice if they simply returned an error instead of returning strange values, but it's not a huge deal if you know what works where. Here's my printf's showing x and y from getXValue, x and y scale, width, and height. The odd lines are from renderOutput and the even lines (that around about 0.5) are from inside frameCleanup. It's applied to a simple rectangle shape that covers about half of a DV frame. Does this make any sense? This email sent to site_archiver(a)lists.apple.com

1 0