Hey Fons,<br><br>Yeah, I'd say for my needs, I can just create a few presets and just cycle through them as needed!<br>Thanks again!<br><br>Andrew.<br><br><div class="gmail_quote">On Sun, Oct 4, 2009 at 11:18 PM, Fons Adriaensen <span dir="ltr"><<a href="mailto:fons@kokkinizita.net">fons@kokkinizita.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Sun, Oct 04, 2009 at 03:33:46PM +0200, Dominic Sacré wrote:<br>
<br>
> Unfortunately it's not that simple. Most hardware MIDI controllers will<br>
> let you send continuous controller values or toggle between two values.<br>
> But to control the stops in Aeolus you basically need to be able to<br>
> manipulate individual bits of the controller values...<br>
><br>
> Some time ago I wrote a small script that might be just what you need.<br>
> It uses mididings (<a href="http://das.nasophon.de/mididings/" target="_blank">http://das.nasophon.de/mididings/</a>) to convert normal<br>
> MIDI controllers (one CC for each stop) to Aeolus' CC 98. You'd just<br>
> need to insert it between your MIDI controller and Aeolus.<br>
<br>
</div>The basic problem here is that MIDI doesn't have anything<br>
close to what is required. On a pipe organ you can switch<br>
each stop on/off independently of all others. MIDI is not<br>
designed to do that, its 'preset' model is something quite<br>
different. The standard Aeolus setup has around 55 stop<br>
buttons, and that amounts to more than 2^55 ~ 3e16 =<br>
30000000000000000 combinations or 'presets'.<br>
<br>
The easiest way to control Aeolus from MIDI is to create<br>
a number of presets in Aeolus (it can have up to 1024)<br>
and then use the standard MIDI messages (bank/preset) to<br>
select one of them.<br>
<br>
If you really want to control individual stops that is still<br>
possible using normal controllers. You need (for the standard<br>
instrument) 4 buttons to select one of the four groups, and<br>
16 buttons to select a stop within a group. If you organise<br>
things this way then each button just needs to send a single<br>
controller message.<br>
<br>
The essential thing to understand is that switching a stop<br>
on/off is a two-step process. First you select a group and<br>
and action (on/off/toggle), then you select a stop within<br>
that group. The first (group/action) message is stored, you<br>
only need to send it when it changes. This is really no more<br>
complicated than the concept of preset banks.<br>
<br>
Apart from all this, mididings is the perfect tool to<br>
manipulate all things midi. Using it you can map Aeolus'<br>
control messages to whatever you want.<br>
<br>
<br>
Ciao,<br>
<font color="#888888"><br>
--<br>
</font><div class="im">FA<br>
<br>
Io lo dico sempre: l'Italia è troppo stretta e lunga.<br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Linux-audio-user mailing list<br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user</a><br>
</div></div></blockquote></div><br>