Re: Clump name and AULab
Re: Clump name and AULab
- Subject: Re: Clump name and AULab
- From: "Marc Poirier [dfx]" <email@hidden>
- Date: Fri, 4 Aug 2006 10:42:05 -0400
Hmmm interesting... I also have always thought that the generic
AUView didn't show the clump names, only the little boxes around the
parameter clumps, but indeed it does show them with the
AUMultibandCompressor. But not with my AUs. And so far as I can
tell, I am implementing the property stuff for it correctly, and
auval shows that it finds the clump names fine, yet the generic
AUView does not. An example is KTGranulator which I ported to AU (an
easy example cuz it has no custom GUI):
http://koen.smartelectronix.com/KTGranulator/
So I'm kinda puzzled. Has anyone else encountered this same
problem? Any ideas?
On Jul 26, 2006, at 3:30 PM, William Stewart wrote:
On 26/07/2006, at 7:54 AM, philippe wicker wrote:
Hi all,
I have regrouped part parameters of a music device AU into some
clumps and I'm wandering how a host proceeds to query the clump
names. When the AU generic view is opened within AULab, the clumps
appear as boxes containing the parameters, but the clump name
does not show up.
Is it a normal AULab behavior?
AULab's view will show the clump names if they are present - our
Multiband compressor should have these
What do I need to implement within the AU code to return the clump
names to a host?
kAudioUnitProperty_ParameterClumpName
AudioUnitParameterNameInfo (read)
This works in a similar manner to the ParameterIDName property,
except that the inID
value is one of the clumpID's that are returned with the AU's
ParameterInfo struct.
I assume I need to write some code in my overriden GetProperty
method. How can I query these clump names? I mean, which scope and
element numbers do I need to use when I call AudioUnitGetProperty?
Clumps (names, etc), like general info on parameters, are really a
scope property.
If you are defining parameters on part scopes, then each element in
the part scope will share the same parameters types, etc (just
different values of course for each element) - think of input
volumes on a mixer... For the way these parameters are clumped, the
same applies - the clumping is defined on the scope (so just as
with param info, the element is ignored), and the host will query
the different scopes for their parameters and clumps.
Does that make sense?
Bill
_______________________________________________
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