28 Mar
2019
28 Mar
'19
2:54 p.m.
On 28.03.2019 21:27, Kjetil Matheussen wrote:
On Wed, Mar 27, 2019 at 8:55 PM Filipe Coelho
<falktx(a)gmail.com> wrote:
This has been debated to death already, you are just not willing to
listen and quickly dismiss the other side.
I am not adding more fuel to the fire, let's stop the discussion here
since, as I said, it will just not happen.
On 27.03.2019 19:22, Holger Marzen wrote:
So, what do you think is wrong with number 2? It's a simple
modification to jack that might give a lot of benefit. Also, it would
certainly solve problem that it's impossible to create a client mixer
for jack now. Pulsaudio/window/osx has it, it's a very natural tool to
expect. 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_*
As the current jack
maintainer I can already give you the heads up.
It is option 1, no such API is going to be added, ever.
And what are your opinion about functions for
providing
default output ports? That would also solve the client mixer problem.
The "default" ports should be set via meta-data.
I said this before on this mailing list just a few emails back, not sure
if you noticed...