29 Dec
2004
29 Dec
'04
4:19 a.m.
Hi,
On Sun, 2004-12-26 at 12:30 -0500, Joe Hartley wrote:
I beg to differ.
Selecting the input device is seldom interesting to do from the softsynth. The routing is
primarily done by the host program or a specifically crafted routing app, like qjackctl or
kaconnect.
Infact, when using lots of softsynths from a sequencer it is a nouisance when the
softsynth has made a default connection to the input device. In my opinion, they should
just register themselves (most have this as an option).
The only case where you want the synth to directly connect itself to another device is
when you are
doing realtime playback from an external keyboard and not using any other stuff, more or
less a special case.
/Robert
Programs default to the first MIDI device, which
is on the Audiophile,
and not all programs will easily allow one to change the input device.
Which programs are these, other than ZynAddSubFX? That's a bad bug,
that would render such programs unusuable to a professional. And
there's no excuse for it, it should be trivial to add support for
selecting the MIDI device to use.
Please report this bug to the author(s) of said program(s).
Lee
29 Dec
29 Dec
7:42 a.m.
New subject: [linux-audio-user] MIDI confusion
On Wed, 29 Dec 2004 09:21:14 +0100
"Robert Jonsson" <rj(a)spamatica.se> wrote:
Lee Revell wrote:
After spending a few days on this, I found that I started in Lee's camp,
bpt fairly quickly moved to Robert's. While it's non-intuitive to a
total MIDI n00b such as myself, once I realized that I use the connection
program of my choice (qjackctl, in my case), it is a straightforward thing
to make the connections.
ZynAddSubFX is at least consistent in its approach; it doesn't make any
connections to audio output channels, either. You have to use a Jack
routing program for that as well.
--
======================================================================
Joe Hartley - UNIX/network Consultant - jh(a)brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa
On Sun, 2004-12-26 at 12:30 -0500, Joe Hartley
wrote:
I beg to differ.
Selecting the input device is seldom interesting to do from the softsynth.
The routing is primarily done by the host program or a specifically crafted
routing app, like qjackctl or kaconnect. Programs default to the first MIDI device, which
is on the Audiophile,
and not all programs will easily allow one to change the input device.
Which programs are these, other than ZynAddSubFX? That's a bad bug,
that would render such programs unusuable to a professional. And
there's no excuse for it, it should be trivial to add support for
selecting the MIDI device to use. 
10:56 a.m.
New subject: [linux-audio-user] MIDI confusion
After spending a few days on this, I found that I
started
in Lee's camp, bpt fairly quickly moved to Robert's. While
it's non-intuitive to a total MIDI n00b such as myself,
once I realized that I use the connection program of my
choice (qjackctl, in my case), it is a straightforward
thing to make the connections.
ZynAddSubFX is at least consistent in its approach; it
doesn't make any connections to audio output channels,
either. You have to use a Jack routing program for that as
well.
I think that it would be hellpful if programs would remember
the last used connections and would off the possibility to
make audio and MIDI connections from within a popup or
similar in the program. This would really increase the
accessibility and usability of audio applications and make it
easier for starters.
Just my two Cents,
ce
12:41 p.m.
New subject: [linux-audio-user] MIDI confusion
On Wed, 2004-12-29 at 06:42 -0500, Joe Hartley wrote:
On Wed, 29 Dec 2004 09:21:14 +0100
"Robert Jonsson" <rj(a)spamatica.se> wrote:
The original poster said that some programs always connect their input
port to the first MIDI out port, and that can't be changed. If they
just registered themselves, it would be OK, or if they let you choose
the port to connect to it would be OK, but always connecting to the
first device seems boneheaded.
Maybe I am confused.
Lee
Lee Revell wrote:
After spending a few days on this, I found that I started in Lee's camp,
bpt fairly quickly moved to Robert's. While it's non-intuitive to a
total MIDI n00b such as myself, once I realized that I use the connection
program of my choice (qjackctl, in my case), it is a straightforward thing
to make the connections.
ZynAddSubFX is at least consistent in its approach; it doesn't make any
connections to audio output channels, either. You have to use a Jack
routing program for that as well.
On Sun, 2004-12-26 at 12:30 -0500, Joe Hartley
wrote:
I beg to differ.
Selecting the input device is seldom interesting to do from the softsynth.
The routing is primarily done by the host program or a specifically crafted
routing app, like qjackctl or kaconnect. Programs default to the first MIDI device, which
is on the Audiophile,
and not all programs will easily allow one to change the input device.
Which programs are these, other than ZynAddSubFX? That's a bad bug,
that would render such programs unusuable to a professional. And
there's no excuse for it, it should be trivial to add support for
selecting the MIDI device to use.
1:11 p.m.
New subject: [linux-audio-user] MIDI confusion
The original poster said that some programs always
connect
their input port to the first MIDI out port, and that can't
be changed. If they just registered themselves, it would
be OK, or if they let you choose the port to connect to it
would be OK, but always connecting to the first device
seems boneheaded.
Hm, of course, if a program behaves this way, it's not as good
as it could be.
But let's take a single desktop computer (or even notebook)
which gets used as softsynth or sequencer.
A program could remember the last used connections (even if
these have been made with aconnect or qjckctl) and reconnect
automatically.
Of course, these bindings should appear in aconnect or
jackconnect and it should be possible to change it there.
If there are any apps which do not behave this way, why not
politely contact the author and ask if it couldn't be
changed? Probably the author has never has been in need to do
so so he simply didn't think about it.
Best regards
ce
1:32 p.m.
New subject: [linux-audio-user] MIDI confusion
Christoph Eckert writes:
If you use qjackctl, you probably want to know that the active patchbay
feature is exactly one solution for this. There you edit a patchbay
definition specifying the individual client and port connections you want
to preserve. Once active, qjackctl will automagically check for the
defined patchbay definition and try to (re)connect each one as soon those
client/ports become available. The matching is made against the actual and
registered JACK/ALSA client/port names, using regular expressions.
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
The original poster said that some programs
always connect
their input port to the first MIDI out port, and that can't
be changed. If they just registered themselves, it would
be OK, or if they let you choose the port to connect to it
would be OK, but always connecting to the first device
seems boneheaded.
Hm, of course, if a program behaves this way, it's not as good
as it could be.
But let's take a single desktop computer (or even notebook)
which gets used as softsynth or sequencer.
A program could remember the last used connections (even if
these have been made with aconnect or qjckctl) and reconnect
automatically.
Of course, these bindings should appear in aconnect or
jackconnect and it should be possible to change it there.
If there are any apps which do not behave this way, why not
politely contact the author and ask if it couldn't be
changed? Probably the author has never has been in need to do
so so he simply didn't think about it.
5:13 p.m.
New subject: [linux-audio-user] MIDI confusion
If you use qjackctl, you probably want to know that
the
active patchbay feature is exactly one solution for this.
There you edit a patchbay definition specifying the
individual client and port connections you want to
preserve. Once active, qjackctl will automagically check
for the defined patchbay definition and try to (re)connect
each one as soon those client/ports become available. The
matching is made against the actual and registered
JACK/ALSA client/port names, using regular expressions.
Sounds great; I guess I'll dive deeper in it as soon as I got
jackd working in realtime.
And BTW: Thanks a lot for qjackctl which makes musicians live
a lot easier!
Thanks for the hint & best regards
ce
7066
days inactive
7066
days old
linux-audio-user@lists.linuxaudio.org
6 comments
5 participants
participants (5)
-
Joe Hartley -
Lee Revell -
mchristoph.eckert＠t-online.de -
Robert Jonsson -
Rui Nuno Capela