Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for pulse client handling #20

Closed
haasn opened this issue Aug 4, 2017 · 1 comment
Closed

Add support for pulse client handling #20

haasn opened this issue Aug 4, 2017 · 1 comment

Comments

@haasn
Copy link

haasn commented Aug 4, 2017

This is a really cool tool, but it seems to be missing the IMO most important part of a pulse mixer: The ability to play around with individual client streams. (i.e. sink inputs / source outputs in pulse terminology)

Basically, I'm missing this tab from pavucontrol:
pavucontrol

It needs the ability to

  1. Change which audio device a program is playing on / recording from
  2. Change the volume of that application

bonus points for also distinguishing between “applications only” and “all streams (including virtual streams)” like pavucontrol does.

@haasn
Copy link
Author

haasn commented Aug 4, 2017

Actually, disregard this. Upon closer inspection, it seems that pulsemixer covers this functionality: the individual applications are listed as “subitems” of the device they're on, and they allow movement as a context menu item. It seems I overlooked this when trying out pulsemixer.

@haasn haasn closed this as completed Aug 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant