>1. This new version seems to always load two instances of the requested
>synth:
Hm. I have never seen this. What is the output from 'which startBristol'?
>2. After the sounds of the previous one are still active.
Multiitimbral. How did you close the synth window? If you do it with ^C, or
destroy the window then I do not always have a change to remove the synth
from the engine. It then lingers on the same midi channel. This was half
intentional, to allow for multitimbral support, but killing the GUI from the
window titlebar should result in a graceful remove of the emulation as well
as the GUI.
>3. Jack did not work.
There are a few other complaints of this one, am looking into it.
>4. Some of the synths get no sound.
Ah, that may have been me. Some of the default synth memories have volume
set to zero - I needed to use them to test the ARP 2600 which has no
keyboard. The up/down memory keys should load the first available one. I
will fix this in the next upload, it may also be an issue with a late
enhancement: the -load <memory index> will allow you to set the first memory
location. Default value is 'zero', but some of the synths do not have a
memory number zero since they take 'bank' numbers that start from '1'.
>
>MIDI works fine but one must specify the -mididev if this is not the first
>alsa/oss device. Mine being the second one, I have to give it /dev/midi1 in
>a
>OSS mode and hw129:0 in ALSA. I assume there is a way of (setting up for)
>using device names instead of this stuff.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Received on Sun Sep 24 20:15:04 2006
This archive was generated by hypermail 2.1.8 : Sun Sep 24 2006 - 20:15:04 EEST