Re: jackd and volume control

On Thu, 28 Mar 2019, Kjetil Matheussen wrote:

> On Wed, Mar 27, 2019 at 7:22 PM Holger Marzen <[email protected]> wrote:
> >
> > As far as I understood there are 3 opinions:
> >
> > 1.) Don't change anything
> > 2.) Add some API-calls to control the volume of every port
> > 3.) Add an API-call to control the volume of system:playback_*
> >
> > I'd say that 2.) will introduce too much complexity. This is what jack
> > clients should do.
> >
> > But some time ago I proposed 3.)
> >
> 
> This is an old discussion. It's about default output ports. Jack
> doesn't provide this concept, but it should. If it had, someone would
> have made a mixer program by now. Now it's almost impossible to make
> such a program. You have to hack it together by monitoring ports, but
> it's not nice and probably won't work as well as it should. So that's
> the fourth opinion. The lack of default output ports also causes lots
> of clients to connect directly to system out, which may cause people
> to destroy their monitors.

The problem can be solved with starting "jack_thru main" and
jack-plumbing rules that disconnect clients from system:playback and
connects them to main:input. It's not perfect but it works for me.

A jack beginner can't. Maybe that's one of the reasons why pulseaudio
won the race (and gets in the way of nearly every newbie who wants to
run jack). Since I don't feel to fork jack to add a master volume and a
standard monitor port I simply accept falkTX's decision and try to help
other newbies to solve their problems with tools that are already
available.