Re: FCP 6.0.3 and FxCustomParameterAction updates
Re: FCP 6.0.3 and FxCustomParameterAction updates
- Subject: Re: FCP 6.0.3 and FxCustomParameterAction updates
- From: Darrin Cardani <email@hidden>
- Date: Fri, 23 May 2008 13:38:44 -0700
On May 23, 2008, at 1:03 PM, Pauli Ojala wrote:
Hi, Pauli,
thank you very much for providing the FloatingWindow FxPlug
sample. I've had the users that were reporting problems with our
plugin in FCP 6.0.3 run the sample, and it works as expected for
them, so the problem is clearly in our FxPlug code.
Were you able to reproduce the problem with my bars & tone steps?
My guess is that this what your users are hitting. Even if not,
someone is bound to hit it eventually.
Yes, I can reproduce that (parameter updates only happen if the clip
is open in the viewer). But actually this limitation doesn't bother
me too much -- at least it's consistent and easy to explain.
What these users are seeing with our plugin is more fatal, no
updates at all except in special circumstances (switching from FCP
to another app and back, and other strange cases). They do report
that your FloatingWindow works, so there's clearly something rotten
in my code.
I tried rewriting my FxPlug parameter+event code following your
model, but with this new version I now have an unfortunate problem:
render triggering doesn't work in Motion 2.x anymore. My old code
did work in Motion 2. (It originally took some weird voodoo to get
it working reliably there, which made the code a mess... That's why
I was eager to do a rewrite.)
FloatingWindow isn't useful as a comparison because it simply
crashes Motion 2.1.2. (Looks like it goes into an infinite loop in
CFRelease; I didn't have time to do any debugging yet.) I wish I
could simply decide not to support Motion 2, but the previous
version of Final Cut Studio is so widespread that it doesn't seem
like a realistic option.
Any ideas on how to get FloatingWindow working on Motion 2 would be
greatly appreciated.
Well, the most straightforward thing to do would be to detect whether
you're in Motion 2 and use the old code path that worked if you are,
otherwise use the newer code path. Is that possible to do?
Darrin
--
Darrin Cardani
email@hidden
_______________________________________________
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