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

Re: question on refreshing parameter data between instances.
by Steve Christensen 15 Aug '09

15 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com On Aug 14, 2009, at 6:13 PM, Brian Gardner wrote: Good point, Steve. _______________________________________________ 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… It does sound like arrays were a bad idea. I do like Darrin's suggestion of using NSNotifications. Seems more stable. I'll assume that NSNotifications doesn't have a similar issue, and will work properly even if the particular clip isn't currently being directly worked on. (Is that a valid assumption?) I don't remember offhand if NSNotificationCenter retains notification observers or not. I would suppose that it would so it doesn't walk off into the weeds if an observer were to go away without unregistering, but you should see if that is, indeed, the case. If it is you would need to figure out a way to make sure the instance is properly disposed. I'm not sure what you meant by "the particular clip isn't currently being directly worked on" part. If it's referring to making sure that the global settings are correctly propagated into plugin instances not yet created, or those that were hypothetically created at some point but have since been destroyed since they're not "being used," then, no, that won't happen because those instances don't exist at the time the notification is sent out. It may be that a better solution would be to have a dirty flag as an instance variable and mark all plugin instances as "dirty" when they're initialized so that the current global settings can be stuffed into the parameters when they're first created and/or replacing the "invalid" parameter value(s) with the current "good" ones from the singleton. Note that this still does not address how the singleton gets the "good" values in the first place. This makes the assumption that a plugin instance is created for each clip that uses your effect and that the instance will hang around in memory until either that clip is removed, the project is closed or the host app quits. I don't know the underlying architecture but it's just as likely that plugin instances are created as needed and then destroyed if you're not currently working with a particular clip. If you create an array and add instances to it, you -could- end up with a bunch of stale items that no longer refer to real clips and/ or conflict with the plugin instance that now manages your effect for a particular clip. ... steve This email sent to site_archiver(a)lists.apple.com

1 0

FCP XML marker comment limit?
by Rainer Standke 15 Aug '09

15 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Hello, are there any length limits to the comments in markers in FCP XMLs? Thanks, Rainer _______________________________________________ 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: question on refreshing parameter data between instances.
by Brian Gardner 15 Aug '09

15 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=I5zo4Hz6SpNulH2twA8JxCsg3mhstW+a7rIfhIwUK5v/6YSM9sUJCczTx5VbChtR; h=Received:From:To:In-Reply-To:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-Mailer:X-ELNK-Trace:X-Originating-IP; Good point, Steve. It does sound like arrays were a bad idea. I do like Darrin's suggestion of using NSNotifications. Seems more stable. I'll assume that NSNotifications doesn't have a similar issue, and will work properly even if the particular clip isn't currently being directly worked on. (Is that a valid assumption?) -- Brian steve _______________________________________________ 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 makes the assumption that a plugin instance is created for each clip that uses your effect and that the instance will hang around in memory until either that clip is removed, the project is closed or the host app quits. I don't know the underlying architecture but it's just as likely that plugin instances are created as needed and then destroyed if you're not currently working with a particular clip. If you create an array and add instances to it, you -could- end up with a bunch of stale items that no longer refer to real clips and/ or conflict with the plugin instance that now manages your effect for a particular clip. ... This email sent to site_archiver(a)lists.apple.com

1 0

Re: how trims & cuts effect reference image wells
by Brian Gardner 15 Aug '09

15 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=XwtCU/DjOyD+cymZTczF2mzU0ILhcgQvuOcQxfRKs8Dswxs9cGM8wZ0m6JrvKJFz; h=Received:From:To:In-Reply-To:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-Mailer:X-ELNK-Trace:X-Originating-IP; Hi, Darrin. Thank you for your suggestion about caching the generator's startTime. I gave this a try, but ran into difficulties. The main problem seems to be that the the startTimeForEffect returns a completely different value when renderOutput is called from the timeline versus the viewer. So, detecting changes between the current startTimeForEffect value and the cached value seems problematic. Because just double clicking the generator in the timeline to load it into the viewer (may) cause the value to become different, even though the generator has not been cut or trimmed. The startTimeForEffect, vs. the inPointOfTimelineForEffect, vs. the startTimeOfImageParm (with respect to a generator) all seems very confusing to me. Could you please explain what these are? I've read the docs, but they don't really say much beyond the method name. Getting a generator's image parameter to correspondingly react to a cut seems rather daunting. Perhaps I am just missing something, and a better understanding of these TimingAPI methods would resolve it? -- Brian PS: In FCP, changing any parameter (except the image parameter, itself) seems to cause a parameterChange message for the image parameter. This is the opposite of what I was expecting. On Aug 11, 2009, at 10:24 AM, Darrin Cardani wrote: Let me know if you have any questions. Here's the plugin I used: <ImageWellChangeTester.zip> Darrin On Aug 7, 2009, at 10:55 AM, Brian Gardner wrote: I'm tryng to get my head around what happens to a FxPlugin (especially a generator) when it is trimmed or cut inhalf then it's parts are moved around on timeline. And what a plugin which has reference image parameter(s) should/could do to appropriately update itself. I would assume the FCP 7 will make a copy of the generator (or clip+filter), then make two API method calls, to which our plugins can optionally respond: My plugin should respond to these two methods, and update it's internal state for accessing the appropriate frame ranges of it's reference image parameters to meet the new post-cut state of the edit. Is my assumption anywhere near correct? If so, what are those FxGenerator 2 methods to which my FxPlug should respond? If not, how does it really work? And how should/can my generator respond to a cut edit, so that it can appropriately access it's reference image parameters? -- Brian _______________________________________________ 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/dcardani%40apple.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… Immediately after a Cut (razor), the 2nd half returns a -1 as the startTimeForEffect (as well as a -1 for the inPoint and outPoint). Once it renders into the viewer, the numbers are then changed to be relative to the viewer (not timeline). Then, once it is rendered into the canvas (by moving the playhead to be over the 2nd half) of the cut generator, the numbers are again altered to be relative to the timeline. I vaguely remember someone else having issues with the startTime being unexpectedly 0. Perhaps they'd hit the same viewer vs canvas issue? Brian, The way you suggest it should work would be a good design. However, that's not how it works currently. :( Paul's out on vacation, and he'd have a better idea of how it works in FCP, but I'll go over what Motion does. I believe that FCP does basically the same thing, but am not positive. An image well is a parameter like any other. When you change the clip duration or the start point, you change the value of the parameter, so the host app will ask your plugin to re-render, just as if the user changed the value of a slider or checkbox. It should first call your plugin's -parameterChanged: method with the ID of the image parameter, but upon testing, I've discovered that it does not (at least in Motion - you should try in FCP). This is a bug you should write up. So all your plugin knows is that something changed and it should rerender. One way you can track what's changed is by caching the image in the image well's start time and duration. In your - renderOutput: method, you can use the FxTimingAPI to see if the image parameter's start time or duration is different from your cached value and do the appropriate thing if it's changed. It's not as convenient as getting a -parameterChanged: message, or a notification directly, but it should be workable. 1.) a method invoked to the original generator passing it the old and new duration. (to the 1st half of cut object) 2.) another method invoked to signal the new copy of the generator, passing it the old and new relative start frame offset. (to the 2nd half of the cut generator) This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: [Q] Final Cut Pro and a video file of which size is still growing
by Eryk Vershen 14 Aug '09

14 Aug '09

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: [Q] Final Cut Pro and a video file of which size is still growing
by Michael Miller 14 Aug '09

14 Aug '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=6YD8PCkTw+Ry72weFUPUFBRbR7d2Dn1Z0oM/0bro93Q=; b=tGTpE6Nq9ird5XocjJdq1upOlg1jU0ucCjXJ5yJK8XrLBjs0pAoTcT98H2tnU5kg/b 8hGnJ1N90kko60sCK+JgtGQnsgt8ARGqJnefgz7hsQiSmo4vssTKN4EF96kMRa3WOFds 3s7epeyTtdj/LhVKxyUdln6H+2DZ6bQtXfQLU= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BvNWb0UG5+vb0aJtdoEm6J3hEGzho6SWUQtMNv4Og1RN+d3rtzp/69DMh4b0XFv4BS S4X2JlzUyWimbp2AMHN9d3aolLyXS28vK6/ev7GXokCOWSzOWkdxIs5Ubh0S7ex2t2p4 3DYqt47/2j3mqp1wSeWAWXxDGGqkIOPqUhJy0= _______________________________________________ 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: [Q] Final Cut Pro and a video file of which size is still growing
by JongAm Park 14 Aug '09

14 Aug '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=oux1k5XShZL/QtZDkWSVQ2djn+1nzs51q0jzX1J83dwLNN7A1txgC9wmPqz0pFOF6y5l8vF4ixXiThpg+o/L3ruzCZnC3m67FpZj1b+eFfYk/liaeN4N5S1x2HzuOYeGvfQkQ7Bl2QBJ+9DnEXpOcbCz3vZwkbkdxYPFTUwiDd4= ; User-agent: Thunderbird 2.0.0.22 (Windows/20090605) thank you, Helena, for your quick response. Our program send the "Update Media File" apple event. Hmm.. I would like to investigate the pattern it works further. Let me give some time to take a look at it. Thank you, again~ :) JongAm Park Hi JongAm, Cheers! Helena On Aug 14, 2009, at 9:51 AM, JongAm Park wrote: Hello, all. Thank you. _______________________________________________ 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… Helena Ju wrote: I believe if you send the update media file apple event ('udfF') we'll update our information about the media file. further documentation can be found here http://developer.apple.com/documentation/AppleApplications/Reference/FinalC… May I ask a question about FCP's picking up the latest file size / duration information from a video file which is already loaded to a FCP project window? We produce many video files which still grow when they are added to FCP project window. At certain point, the file will stop growing, because recording is finished. Then, we want the FCP project window shows the proper "duration" of the file. Is there a way to refresh the FCP project window when recording is finished? To : Mike and JP. Does this describe our situation enough? Is there any missing workflow or behaviour? This email sent to hju(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: [Q] Final Cut Pro and a video file of which size is still growing
by Helena Ju 14 Aug '09

14 Aug '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi JongAm, Cheers! Helena On Aug 14, 2009, at 9:51 AM, JongAm Park wrote: Hello, all. Thank you. _______________________________________________ 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… I believe if you send the update media file apple event ('udfF') we'll update our information about the media file. further documentation can be found here http://developer.apple.com/documentation/AppleApplications/Reference/FinalC… /apple_ref/doc/uid/TP30001149-CH292-SW1 May I ask a question about FCP's picking up the latest file size / duration information from a video file which is already loaded to a FCP project window? We produce many video files which still grow when they are added to FCP project window. At certain point, the file will stop growing, because recording is finished. Then, we want the FCP project window shows the proper "duration" of the file. Is there a way to refresh the FCP project window when recording is finished? To : Mike and JP. Does this describe our situation enough? Is there any missing workflow or behaviour? This email sent to hju(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

[Q] Final Cut Pro and a video file of which size is still growing
by JongAm Park 14 Aug '09

14 Aug '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding; b=z2CKUqGoYUFLBkQsG2OEDLgD+yO/ndbn5StekN/1BRlddu3gUqZYwDHhQ4TN9xHYRyAsHaMmgR6ca7MOwonHJd2DZTZQ1XDfk212H0nm+jRBj2iiQtqRodxPOO7J4GGFan1CZNfmeQ5/xPLOIiJLLKnUHpHkjDhZkBo8g5YhRmE= ; User-agent: Thunderbird 2.0.0.22 (Windows/20090605) Hello, all. Is there a way to refresh the FCP project window when recording is finished? Thank you. _______________________________________________ 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… May I ask a question about FCP's picking up the latest file size / duration information from a video file which is already loaded to a FCP project window? We produce many video files which still grow when they are added to FCP project window. At certain point, the file will stop growing, because recording is finished. Then, we want the FCP project window shows the proper "duration" of the file. To : Mike and JP. Does this describe our situation enough? Is there any missing workflow or behaviour? This email sent to site_archiver(a)lists.apple.com

1 0

Re: question on refreshing parameter data between instances.
by Darrin Cardani 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com On Aug 13, 2009, at 12:38 PM, Brian Gardner wrote: There is no issue until the user decides to alter a global value by changing a parameter value. Unfortunately, I can't figure out how to do that. So, the best I can do is using a singleton ... which is probably Project scoped, which is acceptable. Darrin -- 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… That parameter change will in turn update the corresponding global value, stored in the singleton. At this point, all of the other plugin instances set to useGlobalValues will have a parameter value that still is set to the old global value, except the one that the user has just changed. So, the change must be rippled to all of the other instances of the plugin. Normally, I'd expect to do this by having the singleton maintain an array to keep track of the relevant plugin instance id's. Toggling an instance's useGlobalValues parameter, would add/remove it from the singleton's array. The singleton could loop through this array, to send a message to each managed plugin instance to perform a setParameter, to reflect whenever a global value changed. But... just after an 'open project', the id's are not the same as in the previous session (I think), and the singleton has an empty array anyway (singleton data wasn't seralized). So, this array would need to be reconstructed somehow after the 'project open'. Since the deserialization of the useGlobalValues parameter bypasses ParameterChanged, it never invokes the singleton. So the singleton can't build a list of the relevant plugin instance's new id's. Perhaps, I can replace the toggle with a 'custom parameter' toggle, just so that i can trap the deserialization? Then I could (re)build a new array upon project open. Rather than having an array and trying to keep it in synch, what would probably be better is to use NSNotifications. When a plugin is set for global values, it tells the Notification Center that it wants to receive notifications from the singleton. When the singleton makes a change it tells the Notification Center to notify everyone who wanted to be notified of changes. That way, neither the plugins nor the singleton actually have to track each other. Actually, the user wants these globals to be scoped to the sequence. Almost like a Sequence Setting (but with easier access, since the globals are changed more often). Though, if the user can open multiple projects in one session, then it's probably not even project scoped, it's probably session scoped. (Session scoped is also not very desirable, either.) Certainly, somehow, these global settings must be scoped and stored within the Project file. Yes, if you create a singleton, it is application scoped, actually. It exists in the app's address space and would be used by all instances which request it. We don't currently have a way for plugins to know about the sequence or project to which they are applied. It's been requested on a few occasions, but we haven't implemented it yet. Feel free to file a feature request. And let us know how you think it should work, too. This email sent to site_archiver(a)lists.apple.com

1 0