On Tue, 14 Mar 2017 00:28:20 +0100, Christopher Arndt wrote: >Am 13.03.2017 um 20:04 schrieb Ralf Mardorf: >> DAW users very seldom need jackdbus and other users very seldom need >> the jack sound server at all. > >That's just your opinion, though. I find jackdbus very useful. I often >switch audio interfaces and JACK's dbus interface makes this a lot >easier. That's ridiculous, jackdbus might have advantages for some usage, but your examples don't cover them. >I wrote a little desktop systray app to switch JACK configrations via >dbus (I already announced this here a while ago): > >https://github.com/SpotlightKid/jack-select Selecting a sound card could be done with qjackctl, ardour, by command line and a lot of other ways, too, when using jackd. >For auto-connecting JACK audio and MIDI ports, I wrote a little helper >too: > >https://github.com/SpotlightKid/jack-matchmaker Connections for jackd audio and midi as well as alsa midi could be stored and restored by e.g. aj-snapshot, too. On Mon, 13 Mar 2017 14:27:09 -0700 (PDT), Len Ovens wrote: >This is a case where the combination of pulse and jackdbus work quite >well. Wanting to have a DAW on the screen and be able to, without >exiting from the DAW, play a u-toob vid... You don't need pulseaudio to do this, but even if it would require pulseaudio, it's a corner case. >There are a number of workflows where a pulse/jack combination is the >only way to make it work. (radio studio that uses skype for callin or >interviews comes to mind) Apart from skype interviews, what are those numerous workflows? How often do you hear skype interviews on radio? This is a corner case. Regards, Ralf _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
