Re: [Jack-Devel] Hook for master volume

PrevNext  Index
DateMon, 14 Jul 2014 06:48:23 +0200
From Holger Marzen <[hidden] at marzen dot de>
ToAdrian Knoth <[hidden] at drcomp dot erfurt dot thur dot de>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToAdrian Knoth Re: [Jack-Devel] Hook for master volume
On Sun, 13 Jul 2014, Adrian Knoth wrote:

> On Sun, Jul 13, 2014 at 03:05:09PM +0200, Holger Marzen wrote:
> 
> > a master volume fader is missing in JACK. Some audio interfaces don't
> 
> You couldn't be more wrong. Firstly, there is no master, which renders
> your entire message invalid.
> 
> Then, JACK moves audio between apps and occasionally from and to
> physical ports that may or may not be on the same machine.
> 
> Under no circumstances would JACK fiddle with the data itself, that is,
> change its volume.
> 
> If you want to change some volume, add any of the many JACK mixers into
> the signal flow, and you're set. We have a flexible and modular approach
> for that, and it's intended behaviour that the user has to ask for
> whatever he needs.

This would be a kind of a mixer application that watches clients
connecting to system/playback_1 & 2, disconnects them, reconnects them
to its own input while itself outputting to system/playback_1 & 2.

Additionally, ALSA and Pulse clients could be redirected to the mixer
via .asoundrc and jack audio sink in Pulseaudio.

Sure it can be done on application level. It would be easier if
there was a system/send_1 & 2 (readable) and a system/return_1 & 2
(writable) that are connected by default (or not, depending on an option
switch). This way a master volume application wouldn't have to
change other clients' connections.
PrevNext  Index

1405314707.8015_0.ltw:2, <alpine.DEB.2.11.1407140636120.2591 at regen dot intern dot marzen dot de>