Re: Jack Problems
Kjetil Matheussen <[email protected]> Thu, 28 Mar 2019 21:15:59 +0100
| Newsgroups | gmane.comp.audio.jackit |
|---|---|
| Message-ID | <CAC6niEJhK4gBK=XPEYZzX_9NPo==yzwxGOxTZtKTwSUN=9ewyQ@mail.gmail.com> |
On Wed, Mar 27, 2019 at 7:44 PM John Rigg <[email protected]> wrote: > > On Wed, Mar 27, 2019 at 05:54:31PM +0100, Kjetil Matheussen wrote: > > On Wed, Mar 27, 2019 at 5:51 PM Fons Adriaensen <[email protected]> wrote: > > > > > > On Wed, Mar 27, 2019 at 05:35:04PM +0100, Kjetil Matheussen wrote: > > > > > > > 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? > > > > > > It is NOT an improvement. It is an application which you can use > > > if and when you need the functionality. > > > > You seem to misunderstand. We were talking about the type of > > functionality that zita-mu1, pavucontrol, etc. provides. Clearly you > > would think zita-mu1 is an improvement, if not you wouldn't have made > > it. > > This is sophistry. Having zita-mu1 to use when required is an > improvement over not having it. Adding its functionality to jack > when zita-mu1 (along with other solutions) already exists is not an > improvement, but a redundant increase in complexity. > > This is starting to sound like a systemd vs. traditional init argument. > Not everyone wants multiple functions added to software when there's > already a purpose-specific equivalent that works. > Currently you have to setup zita-mu in order to use it. We lack a program that does everything automatically for you when you start it, so we don't really have it.