Re: why shouldn't clients autoconnect to jack

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

 



On Mon, 23 Mar 2009 14:43:45 +0000
Damon Chaplin <damon@xxxxxxxxxxxxxxxxxxxx> wrote:

> 
> I think there is a middle-ground here.
> 
> When an application runs for the first time, I think it should show a
> configuration dialog allowing the user to choose connections for the
> input & output ports. These can default to the first available ports, so
> most users can simply hit "OK".
> 
> When the application runs in future, it automatically connects to the
> same ports. Though the user can run the configuration dialog again if
> needed.
> 
> (This is pretty much what many Windows apps do, and it works pretty
> well.)
> 
> 
> While qjackctl may be handy for advanced users, I don't really think it
> is suitable for normal users. (I find it pretty painful to use myself.)
> 
> Damon


I disagree. I use ZynAddSubFX and Rosegarden very heavily.

Sometimes I want the sound from Zyn. only to go to the mains, sometimes
I want it to go via jamin. The same is true for the Rosegarden audio.

I also use external synths and very occasionally a microphone. Again
the routes I take could be many and various.

Each project I build has its own script for making the necessary
connections when I run it. Autoconnect is just a nuisance to me.

Similarly, sometimes when trying things out, I run MIDI direct from my
external keyboard to a soft (or hard) synth. Other times I route
through Rosegarden. I value the choice!

 -- 
Will J Godfrey
http://www.musically.me.uk
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/mailman/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