Re: using multiple ams patches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/17/2013 06:26 PM, David Adler wrote:
On Sun, Mar 17, 2013 at 6:00 PM, rosea.grammostola wrote:

Start multiple instances of ams and in the 'Control Center',
bottom left, select the Midi channel to listen, default is 'Omni'.

shortcoming:
That setting won't get saved with the patches, ams starts with
the setting that was active on last application quit.

This appears to be a known shortcoming, the MCV module has
(at least in cvs) that 'reserved for later use'-parameter, which is
meant to become a Midi channel selector.
Once that is implemented, one instance of ams will be usable
as a true multi-channel synth.


Thx. Then the qmidiroute solution is preferable atm (running all the stuff
in NSM via nsm-proxy).
Is AMS still in more or less active development?

I'm patiently watching this 'reserved for later use'-parameter
for -- eeh -- years now. Apart from that, ams is quite a finished
product, so there's no need for much development activity.
It's not abandoned, devs are still around and the one bug I
once reported was fixed within a few weeks.

Ok, NSM support would be nice, I know I'm repeating myself ;)

Concerning qmidiroute, after restart I had to set note to 'fixed' again (it was already on fixed) before the routing via qmidiroute was working again. Annoying.

\r
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user


[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux