module-switch-on-connect: handling virtual sinks

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

 



On 11.11.2017 13:03, Ð?иÑ?аил Ð?овоÑ?елов, Ð?Ñ?малогиÑ? wrote:
> Yes, of course, it's possible to unload module-switch-on-connect, but 
> that is breaking the existimg user setup.
> "a command line switch could be added
> to the module so that it ignores virtual sinks" Will be best. Does 
> this flag exist now?

Please don't top post on that list. No, such a flag does not exist right now
but it can be added rather easily. I'll send you an untested patch, please
check if it works as expected.

>
> 11 ноÑ?бÑ?Ñ? 2017 г. 14:26:21 GMT+03:00, Georg Chini <georg at chini.tk> пиÑ?еÑ?:
>
>     On 11.11.2017 05:28, Ð?иÑ?аил Ð?овоÑ?елов, Ð?Ñ?малогиÑ? wrote:
>
>         Hello, PulseEffects, an application, that can apply different
>         effects or equalize both input and output sound, cannot work
>         properly when module-switch-on-connect is on. PulseEffects
>         creates a virtual sinks, but PulseAudio's
>         module-switch-on-connect makes it a default sinks
>         automatically what severely breaks the logic of PulseEffect's
>         work. Please see
>         https://github.com/wwmm/pulseeffects/issues/99 1) Can we
>         specify that the created sink is a virtual one? 2) Maybe there
>         are other ways to prevent module-switch-on-connect from making
>         a newly created virtual device a default one? I wrote the
>         script Dumacast https://github.com/mikhailnov/dumacast (first
>         of all for my company's (Dumalogiya, http://дÑ?малогиÑ?.Ñ?Ñ;?)
>         internal usage), and starting with the newest version of
>         Ubuntu, where module-switch-on-connect is on, I ran into the
>         same troubles. My script
>         https://github.com/mikhailnov/dumacast/blob/master/usr/bin/dumacast
>         creates virtual sinks via pactl (lines 135-149), and they are
>         also made default and break the logic of how the script works.
>         I currently have no idea how to handle it without unloading
>         module-switch-on-connect. I tried both Ubuntu's 17.10 default
>         PulseAudio and built from dEbian sources PulseAudio 11, the
>         situation is the same with them both. What can be done?
>
>
>     Do you really need module-switch-on-connect? If not, you could just
>     check with
>     "pactl list modules short" if the module is loaded and unload it prior
>     to starting
>     your application. You can also remove it fromdefault.pa <http://default.pa>, so that it
>     never gets
>     loaded.
>
>     If you need module-switch-on-connect, a command line switch could be added
>     to the module so that it ignores virtual sinks. The default behavior
>     however can
>     not be changed, because other applications might rely on the current setup.
>
>     Regards
>                    Georg
>
>
> -- 
> Ð?Ñ?оÑ?Ñ?иÑ?е за кÑ?аÑ?коÑ?Ñ?Ñ?, Ñ?оздано в K-9 Mail. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20171111/4c7efec4/attachment.html>


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

  Powered by Linux