17 Mar
2013
17 Mar
'13
4:41 p.m.
Hi,
If you want to use multiple AMS patches at onces, you've to load
multiple instances of AMS right?
How should I route midi output from a sequencer or hardware controller
with one single midi output to those multiple instances of AMS without
triggering all the AMS instances? AFAIK qmidiroute has only 2 output ports.
\r
17 Mar
17 Mar
4:55 p.m.
On Sun, 2013-03-17 at 16:40 +0100, rosea.grammostola wrote:
AFAIK qmidiroute has only 2 output ports.
"--portCount <num>
Set the number of available ALSA output ports to
<num>. The default is 2."
http://manpages.ubuntu.com/manpages/natty/man1/qmidiroute.1.html
5:23 p.m.
On Sun, Mar 17, 2013 at 4:40 PM, rosea.grammostola wrote:
Hi,
If you want to use multiple AMS patches at onces, you've to load multiple
instances of AMS right?
How should I route midi output from a sequencer or hardware controller with
one single midi output to those multiple instances of AMS without triggering
all the AMS instances? AFAIK qmidiroute has only 2 output ports.
hi
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.
greetings
6:01 p.m.
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?
\r
6:26 p.m.
On Sun, Mar 17, 2013 at 6:00 PM, rosea.grammostola wrote:
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.
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?
6:33 p.m.
On 03/17/2013 06:26 PM, David Adler wrote:
On Sun, Mar 17, 2013 at 6:00 PM, rosea.grammostola
wrote:
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
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?
4205
days inactive
4205
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
David Adler -
Ralf Mardorf -
rosea.grammostola