30 Jul
2005
30 Jul
'05
11:15 p.m.
What I'm dreaming of is configuring my sequencer to output to just one
alsa sequencer port. On that port is one "logical" bank of all the
"logical" instruments I use (just instrument names, only). The piece of
software listening on this port is to associate each instrument with a
synthesiser, and most importantly, can be reconfigured by selecting a
different profile if I unplug my laptop from an external synth and am
forced to use a software synth temporarily. I am a roaming midi user.
Are there any solutions already to this problem? What do you guys do to
manage your instruments?
Ryan
31 Jul
31 Jul
4:51 p.m.
On Sun, Jul 31, 2005 at 11:15:46AM +1000, Ryan Heise wrote:
What I'm dreaming of is configuring my sequencer
to output to just one
alsa sequencer port. On that port is one "logical" bank of all the
"logical" instruments I use (just instrument names, only). The piece of
software listening on this port is to associate each instrument with a
synthesiser, and most importantly, can be reconfigured by selecting a
different profile if I unplug my laptop from an external synth and am
forced to use a software synth temporarily. I am a roaming midi user.
Let's see
whether I got this right: You want a MIDI router with
one input port and several output ports, and you want the router
to look at the names of available synthesizers and automatically
connect its output ports accordingly. Similarly, the router should
recognize your sequencer and hook up its input port accordingly.
This leaves the question of how to assign events to output ports.
I suppose one could simply route events based on their channel.
Is this the behavior you have in mind?
Possible enhancement: Instead of profiles, one may want to have
hierarchies of instruments, so that for each output port the
router automatically picks the most desirable instrument that's
currently available.
Are there any solutions already to this problem? What
do you guys do to
manage your instruments?
My standard approach to problems of this kind is to just
hack
together a few dozen lines of throwaway Python code as I need
them. The job you describe shouldn't take much more than that.
(And it just happens that I recently added some functionality
to my Python bindings for accessing sequencer clients and their
ports by name:)
Peter
1 Aug
1 Aug
12:30 a.m.
On Sun, Jul 31, 2005 at 08:51:26PM +0200, Peter Brinkmann wrote:
Let's see whether I got this right: You want a
MIDI router with
one input port and several output ports,
Pretty much. For example, suppose my virtual band has:
- Bass
- Drumkit
- Rhodes
- etc.
When I'm at home, I'd like to plug in to my external Bass synth. When
I'm away from home, I'd like to use the software synth on my computer.
When we're rehearsing with an actual Bass player, I'd like to turn off
the Bass line and let the real Bass player play over the top (I realise
this last case is a little different, but it would be good if this
feature were also integrated into the same tool).
My standard approach to problems of this kind is to
just hack
together a few dozen lines of throwaway Python code as I need
them. The job you describe shouldn't take much more than that.
(And it just happens that I recently added some functionality
to my Python bindings for accessing sequencer clients and their
ports by name:)
I'm imagining the script/program needs to interpret the midi data in
order to route it. Is that a simple matter or a difficult one?
Thanks,
Ryan
12:20 p.m.
Ryan,
When we're rehearsing with an actual Bass player,
I'd like to turn off
the Bass line and let the real Bass player play over the top (I realise
this last case is a little different, but it would be good if this
feature were also integrated into the same tool).
I think it would be easier just
to disconnect the bassline in kaconnect
when the bass player is present.
I'm imagining the script/program needs to
interpret the midi data in
order to route it. Is that a simple matter or a difficult one?
Quite simple. A
proof-of-concept implementation is attached. It's sort
of crude, but you can glean the basic technique from it.
Close to the top you'll find the configuration: It consists of a number
of lists of sequencer clients, one for the input source, and one for
each MIDI channel. In such a list, the more desirable sound sources are
listed first. The tool will create one output port for each channel that's
listed, plus one output port that'll catch everything that's not routed
to any of the other ports.
The names of clients don't have to be exact; capitalization doesn't matter,
and it's enough to give a substring of the name you're after (as long as
it's long enough to distinguish it from other names).
I believe this is the basic functionality you're after. Let me know if
you have any questions or comments.
Peter
PS: You'll need my PySeq library to run this:
http://www.math.tu-berlin.de/~brinkman/software/pyseq/
7055
days inactive
7057
days old
linux-audio-user@lists.linuxaudio.org
3 comments
2 participants
participants (2)
-
Peter Brinkmann -
rheise＠it.uts.edu.au