[RFC] Per-client flat-volumes control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6 August 2014 12:10, Alexander E. Patrakov <patrakov at gmail.com> wrote:
> 06.08.2014 12:15, Arun Raghavan wrote:
>>
>> On 6 August 2014 10:28, Alexander E. Patrakov <patrakov at gmail.com> wrote:
[...]
>>> Well, I am not sure. The doubt comes out from the possibility of an
>>> incompetent web programmer to create many stupid audio contexts from the
>>> same tab, thus again returning the slider-pollution problem.
>>
>>
>> I think that sort of use should be considered bad behaviour (on any
>> system, creating and not freeing resources will inevitable hit a
>> limit), so trying to deal with that might not make sense.
>
>
> It does make sense. Instead of (or in addition to) the global limit, we
> might introduce a per-group limit or something like that, so that it is hit
> first. But I was talking more about the UI issue, because the limit that is
> _actually_ hit first is the number of UI elements (sliders in pavucontrol)
> that the user is willing to tolerate. I.e. I want to enforce the "one slider
> per tab" rule strictly, even if this means excluding some use cases.

I guess we're in disagreement there. We can discuss this further,
either in a separate thread, or at GstConf (or both), but I would like
to get some more opinions on getting this patch in soon, since it's a
practical fix that we can use now.

-- Arun


[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux