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: Pauli Ojala <email@hidden>
- Date: Sat, 24 May 2008 00:11:23 +0300
On 23.5.2008, at 23.38, Darrin Cardani wrote:
On May 23, 2008, at 1:03 PM, Pauli Ojala wrote:
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?
I suppose it is. The old code path is weird and contrived, the result
of experimental voodoo years ago; I was hoping to do a complete
housecleaning of the FxPlug code and finally throw it away, but looks
like I'll have to keep it in the attic for now.
FxHostCapabilities' methods -hostIsMotion and -hostVersionNumber is
the proper way to detect the old host, right?
--
Pauli Ojala
Lacquer oy/ltd
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