site_archiver@lists.apple.com Delivered-To: Pro-apps-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=s8v99xfX4b1CmZWQaoZNbc0VbwQfpZPIwN/S+fu+o9bN8tk+DtFW2XvYIa1h8QTC; 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; Just to clarify this before I start... I get the start time from the FxTimingAPI in timeline frames (I think). If a generator is cut, it's 2nd half would have it's start time changed? Did I understand that right? -- Brian 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> _______________________________________________ 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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... And that change is always distinguishable from a clip that's just being moved? (By looking at the duration, because the duration also changes on a cut, but not on a move.) 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. Darrin This email sent to site_archiver@lists.apple.com