Re: AU Views, 'thng' versus ComponentEntryPoint::Register
Re: AU Views, 'thng' versus ComponentEntryPoint::Register
- Subject: Re: AU Views, 'thng' versus ComponentEntryPoint::Register
- From: Eric Eizenman <email@hidden>
- Date: Mon, 27 Mar 2006 17:54:47 -0800
I don't think it will work. It'll be probably too late in registering
those effects. AudioUnits don't have a way of dealing with multi-
effect plug-in that publishes other effects dynamically. The AU way
to create a multi-effect is simply pack the 'thng's in a single
resource file which is registered system wide.
You could supply some kind of a utility that will run on start-up and
will publish the components before the user start his host
application. That utility might write 'thng' resources or register
those components you like.
------------------------------------------------------------------
Eric Eizenman
BIAS Inc., Audio Software Development
------------------------------------------------------------------
On Mar 27, 2006, at 1:27 AM, Angus F. Hewlett wrote:
A good point... normally, any given AU component will provide a
'thng' for each plugin (and optionally for each view, though the
view can be dynamically registered). The question is, can an AU
component provide a single 'thng', and then register further
plugins when the first one's entrypoint is called?
=========================================================
Angus F. Hewlett, Managing Director (CEO)
FXpansion Audio UK Ltd - http://www.fxpansion.com
Registered in the UK - #4455834 - VAT: GB 798 7782 33
=========================================================
Kenneth Weiss wrote:
Bill,
We use the 'thng' because we have multiple plugins within one
component so we need many entry points,
Is it possible to use the ComponentEntryPoint's for multiple
entry instead?
Kenneth
Kenneth Weiss,
Audio Software Engineer
email- email@hidden
phone- 972-3-6084023
On Mar 24, 2006, at 9:41 PM, William Stewart wrote:
On 23/03/2006, at 2:17 PM, Angus F. Hewlett wrote:
Hi all,
Looking at ours and some other AUs, there seem to be two
different ways that an AU can register its View component with
the system:-
-- via ComponentEntryPoint<CViewClass>::Register()
This is dynamic - that is the view is being registered by code
being executed
-- via a 'thng' resource describing the View, and the
COMPONENT_ENTRY macro.
This is static - the view is registered by the component mgr
code based on the resource entry. In general this is the
preferred option as it doesn't require any of your code to
execute in order for you view to be discoverable; though the
difference here is minimal from what I can surmise.
Bill
Is one preferred over the other? Both seem to pass auval OK, as
far as I can tell.
Best regards,
Angus.
--
=========================================================
Angus F. Hewlett, Managing Director (CEO)
FXpansion Audio UK Ltd - http://www.fxpansion.com
Registered in the UK - #4455834 - VAT: GB 798 7782 33
=========================================================
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
--
mailto:email@hidden
tel: +1 408 974 4056
____________________________________________________________________
__ ____
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry
Pratchett
____________________________________________________________________
__ ____
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40waves.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
inc.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden