Re: FxPlug filter conflicts with multiple filters installed.
Re: FxPlug filter conflicts with multiple filters installed.
- Subject: Re: FxPlug filter conflicts with multiple filters installed.
- From: "Emile Tobenfeld (a. k. a Dr. T)" <email@hidden>
- Date: Wed, 28 Mar 2007 14:07:38 -0400
Title: Re: FxPlug filter conflicts with multiple filters
installe
Darrin
We have other, more serious, problems with C++ templates, that
affect rendering in release builds. I haven't had time to dig into
them yet, and am hoping it has something to do with build
settings.(The same code renders fine when built with Xcode in an
AEPlug.
If you have any insights here, please let me know.
Thanks.
At 10:56 AM -0700 3/28/07, Darrin Cardani wrote:
On Mar 28, 2007, at 10:53 AM, Pierre
Jasmin wrote:
Emile Tobenfeld (a. k. a Dr. T)
wrote:
Hi
I am working on a set of FxPlug filters for use in FCP and Motion. The
bulk of the code in these filters consists of a large pre-existing
library of C++ code. There is a relatively thin layer of Objective C
code, (along with some utility code written in C++) wrapped around the
old library. All of the common Objective C classes are given unique
names (for each filter) at precompile time.
What I am finding is that certain filters interfere with other filters
when they are installed. This happens particularly in debug builds.
(I'm not sure its completely restricted to debug builds -- if it were,
I could work around it if necessary.
What I am seeing is situations like
1. If filter A is installed, FCP will crash (in its
own code) when filter B brings up its UI, even if filter A is not
used in the session
2. If Filter C is installed, Filters D and E will
not render correctly, even if filter C is not used in the
session.
I realize this is sketchy information, but I'm hoping someone on one
of these lists has an idea about how to deal with the problem.
Thanks.
Apparently and you won't believe it, as per another list, all class
names in FxPlugs must be unique (a problem with the Objective C
language and current linker) and also unique amongst natives, your
friends and competitors as all FxPlugs are loaded into the same
address space.
So you have to revert right now I am told (not being an the expert on
Objective C) to use defines as in
PlugA: #define
CustomParam MyCompanyNameMyPluginNameCustomParam
PlugB: #define
CustomParam MyCompanyNameMyOtherPluginNameCustomParam
Actually in Emile's case, this is a
problem with C++ templates. We're still trying to figure out what's
happening, as this is different from the Objective-C
case.
Darrin
--
Darrin Cardani
email@hidden
--
"The test of a first-rate intelligence
is the ability to hold two opposed ideas in the mind at the same time,
and still retain the ability to function."
F. Scott Fitzgerald
Visit "Before the Fall -- Images of
the World Trade Center" at http://www.foryourhead.com
Emile Tobenfeld, Ph. D.
Video Producer
Image Processing Specialist
Video for your HEAD!
Boris FX
http://www.foryourhead.com
http://www.borisfx.com
_______________________________________________
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