| wiki | search |
Contents |
JACK and Qjackcontrol
It is highly recommended to run Aeolus on top of the JACK soundserver. The following steps require that JACK is configured and running. Though that JACK is a command line application, it is recommended to use qjackctl as a frontend to control your audio system:
MIDI connections
Additionally you can use a tool like aseqview to check if there is incoming MIDI data at all (don't forget to connect it to the same input as Aeolus like shown in the screenshot above & NOTE the channel numbering differs by 1):
Playing on your keyboard (or other source) now should show the incoming MIDI events as activity in aseqview.
Audio connections
If you do not get any audio output, you can use an application like Meterbridge to check if Aeolus outputs audio:
As meterbridge needs some command line arguments to be started, here is an example:
- meterbridge -n meterbridge -t dpm aeolus:out_1 aeolus:out_2
MIDI settings
In the Aeolus main window, click on the MIDI button. This dialog allows you to tell Aeolus which partition will respond to a certain MIDI channel:
In the section called "Keyboards", select which MIDI channel will play which division. A common setup maps MIDI channels as follows:
| Division I | Channel 1 |
| Division II | Channel 2 |
| Division III | Channel 3 |
| Pedal | Channel 4 |
In the section called "Divisions", select which MIDI channels are used to control swell (MIDI CC 7), tremulant speed (MIDI CC 12) and depth (MIDI CC 13). The current instrument doesn't provide swell and tremulant for division I, but for divisions II and III. In most setups the same MIDI channel as for the notes will be used. The control channel (in the current instrument) is for controlling global parameters.
Some explanations about partitions, keyboards and MIDI channels.
Switching the stops
Finally, switch on and off stops as you like and enjoy playing Aeolus!
Presets
