Re: Jack Problems
"Thomas Brand" <[email protected]> Wed, 27 Mar 2019 17:52:15 +0100
| Newsgroups | gmane.comp.audio.jackit |
|---|---|
| Message-ID | <[email protected]> |
On Wed, March 27, 2019 17:35, Kjetil Matheussen wrote: > On Wed, Mar 27, 2019 at 5:19 PM John Rigg <[email protected]> wrote: >> On Wed, Mar 27, 2019 at 03:44:07PM +0100, Kjetil Matheussen wrote: >> >>> Clutterered or not, this functionality is something >>> pulseaudio/windows/osx all provide, but not jack. Is jack better >>> because it doesn't provide this? No, it's worse. >> >> No, it's decidedly better IMO. Complexity isn't always an improvement. >> > This should be considered an essential feature expected to be there. > Do you think the windows/pulseaudio/osx peple don't know what they are > doing? Do you think Fons' zita-mu1 program is not an improvement? > Thinking out loud .. we could ship a tool / example client with jack that is similar to alsamixer but for jack. A simple command line tool (no GUI issues) with a configurable number of ports, eventually it could even catch all connections to system:playback if requested. Eg. the program jack_capture (which i think is one of the best recorders) offers connection logic that will for instance record everything that goes to system:playback (it involves to manage connections). Bonus points if the jack_mixer could also set alsa parameters of the alsa device in use, eg. set levels to 100%. You could then scale everything inside jack and have minimal control on the device's volume. Greetings Thomas