| Summary: | Support loading pulseaudio modules | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma-pa | Reporter: | Bastian Köcher <bugs.kde.org> |
| Component: | general | Assignee: | David Rosca <nowrep> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | kde, lorenzo, nate, nicolas.fella, plasma-bugs-null, sitter |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=425814 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Bastian Köcher
2017-04-20 06:43:12 UTC
We kinda do. "Automatically switch all running streams..." setting is basically a front end to enabling the module switch-on-connect. I'm happy to expand on that; I'm not convinced generalising this is going to be a good idea. A lot of modules need extra settings, we want nice human readable names etc. Can you expand on your "for example" list. So we can deterimine what UI works best. From Bug 425814, another requested one which seems reasonable is the Compressor module. *** Bug 425814 has been marked as a duplicate of this bug. *** I agree with David. Adding settings for individual modules can make sense, but I would object to a generic module UI I would go a step further and argue that there needs to be a very carefully drafted reasoning for why a given module setting should be in the default UI. The way I see it most modules are serving very advanced use cases that had better been catered to by purpose built apps like pulseeffects. That said, agreed that we don't want a generic UI. |