The problem of not indicating that some profiles are partially unplugged will hopefully be solved soon - I have already made a patch for this, I just need to revise it when I get time.

It would probably be a good idea to hide all unplugged profiles in pavucontrol. It should be pretty easy to implement, but I don't expect to do that myself any time soon, so patches welcome.

A better UI than a simple list of profiles should be possible to do, but it's not as simple as it may first seem. There are some difficult cases where e.g. selecting surround output makes any input impossible. It's not obvious how to present such conflicts in the UI.

Excellent.  I'm willing to test from source, and do some coding.

Is the source still at git://anongit.freedesktop.org/pulseaudio/pavucontrol?  Are your patches there?

As far as a better UI goes, I think that for a card with both inputs and outputs (which is probably most of them) it would be nice to be able to select the input and the output independently.  If selecting an output requires that the input be turned off then if that output is selected then the input would be deselected.  There are some issues that would have to be ironed out here, including issues with how pulse audio handles headphone/mic jacks, but I think that this general idea would be better than the current one.

(In reply to Peter F. Patel-Schneider from comment #2)
> Is the source still at git://anongit.freedesktop.org/pulseaudio/pavucontrol?

Yes, that's the right repository.

> Are your patches there?

No, the patch that I mentioned is available here (it's for pulseaudio, not pavucontrol): https://patchwork.freedesktop.org/patch/178102/

> As far as a better UI goes, I think that for a card with both inputs and
> outputs (which is probably most of them) it would be nice to be able to
> select the input and the output independently.  If selecting an output
> requires that the input be turned off then if that output is selected then
> the input would be deselected.  There are some issues that would have to be
> ironed out here, including issues with how pulse audio handles headphone/mic
> jacks, but I think that this general idea would be better than the current
> one.

Just disabling the input when selecting an incompatible output would certainly be one viable way to handle the conflicts.

Note that it's possible to have profiles with multiple sinks and multiple sources, although the default configuration doesn't set up any such profiles. That's an additional source of complexity.

That patch for pulseaudio looks good.  What's holding it up, or it it already pulled in the development version?

Then having pavucontrol be a bit more agressive about labelling profiles with no outputs would be useful.

I'm having trouble compiling pavucontrol because pkg-config isn't finding packages on my Fedora 27 system.

(In reply to Peter F. Patel-Schneider from comment #4)
> That patch for pulseaudio looks good.  What's holding it up, or it it
> already pulled in the development version?

As you can see in patchwork, there were improvement ideas from Georg. I never implemented those, because I got distracted by something else.

> I'm having trouble compiling pavucontrol because pkg-config isn't finding
> packages on my Fedora 27 system.

Do you have the -devel packages installed for the dependencies? On Debian you could use "apt-get build-dep pavucontrol" to install all the build dependencies, I don't know if Fedora has something similar.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/issues/39.