The Other wrote: The file was fun to produce because I could play with Aeolus's stops while the MIDI file was playing, catching those on-the-fly adjustments in the final recording. If one listens to aeolus with studio monitor (audio reference) speakers, it sounds like an ideal recording of a great masterwork organ, without of course the creaks and groans, whistles, hisses, clicks and other mechanical noise such an organ might have (or have developed with age). Aeolus is an awesome program that makes me anyway, a lifelong piano player, now have an interest in learning to play organ (to develop skills to play a multi-manual keyboard and pedalboard). Steve

david wrote: Try starting it from the command line and see if an error message appears. Unless, of course, you already tried that, then never mind. -- Darren

david wrote: See if the intructions at the following URL help-- :-) http://www.geocities.jp/midi_organ_net/aeolus/ Steve

On Sat, Sep 20, 2008 at 10:54:22PM -1000, david wrote: Jack is the default. You can use ALSA with the -A option. It will try to start Jack in that case (this may be removed in future releases). If you start Aeolus in a terminal it will usually report if anything goes wrong. Aeolus also accepts MIDI over Jack if you have that enabled. Make sure you're running Jack and Aeolus in RT mode. In many cases that's enough to avoid xruns, even on a standard kernel (but YMMV). 45% CPU is on the high side. On my six year old 2G P4 it Aeolus rarely goes above 15%, and quite less on average. You also get a too high CPU estimate from Jack/Qjackctl if not running realtime. Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Wie der Mond heute Nacht aussieht ! Ist es nicht ein seltsames Bild ?

On Sun, Sep 21, 2008 at 12:13:34AM -1000, david wrote: You can probably have an almost xrun-free system. You don't need an RT patched kernel for this. Look at the file /etc/security/limits.conf, and verify if you have some lines there similar to @audio - rtprio 99 @audio - nice -10 @audio - memlock 400000 Instead of @audio there could also be '*'. If you don't have these, add them (you must be root to do this). The nmber after 'memlock' should be something like 80% of your RAM size. Verify if you have an 'audio' group. If not, create it. Make sure your are a member of this group. In Qjackctl's setup, enable realtime and set priority to e.g. 60. Also enable 'memory unlock'. Make sure you use a raw ALSA device (normally hw:0). To be on the safe side, set frames/period to 256 and periods/buffer to 3. Try later if things work with 2 as well. You should now be able to run jackd in realtime mode. The three warnings from Aeolus should be gone as well, and with a bit of luck also most of the xruns. You have to enable this, it's in the lower left corner of Qjackctl's setup window. Don't know if Rosegarden will like this. Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Wie der Mond heute Nacht aussieht ! Ist es nicht ein seltsames Bild ?

On Sunday 21 September 2008 21:39, Stephen Doonan wrote: It probably already is, but may be worth looking in /sbin/lsmod to see if snd-seq-midi is loaded. Saying that though, when you open Qjackctl, it will complain if that module isn't loaded, saying "midi ports not available", or something like that. The above is related to my experience with my usb midi keyboard. Nigel.

Stephen Doonan wrote: Emu MidiXport. My keyboard automatically switches to transmit mode when it detects a MIDI connection. Simply having the adaptor plugged in is enough to trigger that. -- David gnome(a)hawaii.rr.com authenticity, honesty, community