Re: Controller mapping
Re: Controller mapping
- Subject: Re: Controller mapping
- From: William Stewart <email@hidden>
- Date: Mon, 10 May 2010 17:41:21 -0700
On May 8, 2010, at 12:10 AM, john smith wrote:
>
> Thanks Bill,
>
> however, that only works using MIDI messages?
Yes, so you get a MIDI message into your AU, which your AU has mapped to a parameter. Your AU then uses that MIDI message to change the value of the parameter, and then is uses the AUParameterListener to notify any listeners (including views) that the parameter has changed.
> What we really want is the communication to be 2-way, so that the controller gets updated when a parameter changed (from the GUI or due to automation). Is that possible?
You'd have to send a MIDI message to the controller. That would involve knowing which MIDI destination to send too, etc... So, no, not at this point.
>
> Also, we want to do this without the user to have any settings. It should "just work". (like you use controllers in ProTools, where the developer can map the parameters to the different types of controllers).
> So, as an example, let's say I have an eq, and a controller with 8 rotaries and 8 switches per page.
>
Yes - I think the host knows all if needs to know (or can figure this out)... If you can file a bug, we can have a closer look at this
> So, page 1:
>
> switch 1: band 1 on/off
> rotary 1: band 1 freq
> rotary 2: band 1 gain
> rotary 3: gand 1 q
>
> switch 5: band 2 on/off
> rotary 5: band 2 freq
> rotary 6: band 2 gain
> rotary 7: gand 2 q
>
> page 2:
>
> switch 1: band 3 on/off
> rotary 1: band 3 freq
> rotary 2: band 3 gain
> rotary 3: gand 3 q
>
>
> etc. etc.
>
>
> I hope this is clearer now.
yep - thanks Michael
Bill
>
>
> Greets,
>
> Michael Olsen
> PhonoXone
>
>
>
> > Hi Michael
> >
> > Yes.
> >
> > If you have a look in the base classes, there is an CA_AUTO_MIDI_MAP define. What this does is enable you to map a MIDI message to a parameter, store that mapping and re-constitute it later.
> >
> > Your effect becomes an "aumf" type (which is an audio unit that implements the MIDI message/API). A host then can notice this, and will route MIDI messages to your AU. You could provide a hot-map type facility in your UI using the audio unit properties that are defined for this (see <AudioUnit/AudioUnitProperties.h> (kAudioUnitProperty_AllParameterMIDIMappings, etc)
> >
> > AULab provides some support for these as well, so that can be a good test bed for you to use for development.
> >
> > Bill
> >
> > On May 6, 2010, at 7:52 AM, john smith wrote:
>
>
> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now.
_______________________________________________
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