3 Feb
2008
3 Feb
'08
2:54 p.m.
On Feb 1, 2008 1:34 PM, Kjetil S. Matheussen <k.s.matheussen(a)notam02.no> wrote:
Fons Adriaensen:
Absolutely. I think a new function for jack would be
better than an environment variable though:
int jack_autoconnect_playback (jack_client_t *,
int portnum,
const char *source_port);
int jack_autoconnect_record (jack_client_t *,
int portnum,
const char *destination_port);
The reason is that this API will make it easier
for programs to make autoconnection configurabe.
Autoconnecting the old way (which includes finding
the physical ports and/or checking environment variables
for ports to connect to, etc.) is a lot more
hassle than just calling the functions above.
If I understand your API above correctly, jackd would need to know
what playback ports it would allow autoconnection to, right? For
example, I'd like to be able to tell jackd that I have a pair of
physical outs connected to my power amp, and I will allow client to
auto-connect to those:
jackd [normal options] --allow-autoconnect --main-monitors
alsa_pcm:playback_3,alsa_pcm:playback_4
One instance where I've found auto-connect useful is with a simple
sample auditioner I wrote that uses gstreamer with the jack sink. I
want the auditioner to require as few clicks as possible, so I can
quickly start it up and check out a bunch of samples without having to
think about connecting it, etc.
In most other situations, I find auto-connect to be completely annoying.
You can be as much of a professional user as you
want to.
It doesn't change the fact that other professionals might
not want the system to behave like you do.
Which again means it should be configurable.