Settings issueshttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues2024-01-21T06:27:24Zhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1172Default audio device and disabling audio devices2024-01-21T06:27:24ZtabzlockDefault audio device and disabling audio devices<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/docs/CONTRIBUTING...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/docs/CONTRIBUTING.md#communication-guideline
-->
Detailed description of the feature. Put as much information as you can.
This is something that has really been bugging me lately I agree that its useful to auto switch to new devices when they are plugged in. But this becomes a real issue for me and many users when we have a set headphones and microphone setup and I don't want to add startup scripts every time just to set a default audio device!
adding this feature I think it would also make sense to consider issue #830 as it would also be helpful to be able to disable audio devices you never use.
this is similar to the issue #801 and I really think we need a physical button to set defaults or make sure that audio devices are saved when you log out or turn off your device.
I have tested to see if gnome saves devices after logout as some people have suggested it does I haven't been able to replicate this on any of my gnome installs: "fedora,manjaro,arch,pop_os"
my current audio setup features a microphone with an input and output one for monitoring and headphones that output to my soundcard
## Example:
![gnome_sound_example](/uploads/26c14d1eae54ef6303866784d91181c0/gnome_sound_example.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1687Use PulseAudio device.description if available to provide audio device names2023-11-21T11:47:27Zjgcodes2020Use PulseAudio device.description if available to provide audio device names<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/docs/CONTRIBUTING...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/docs/CONTRIBUTING.md#communication-guideline
-->
The `pavucontrol` application uses the `device.description` property for device names instead of the typically wordy `device.product.name` if it is provided for a device. As `device.description` is modifiable, it can thus be assigned a much shorter and more readable name (e.g. "Built-in Sound" instead of "Tiger Lake-LP Smart Sound Technology Audio Controller").
While adding this feature doesn't require adding any new options, it would also be nice to be able to rename PulseAudio sinks/sources through the settings menu somehow.https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/206User is forced to manually change the sound output device2021-01-01T23:53:17ZmjourdanUser is forced to manually change the sound output deviceUsing an HDMI audio power amplifier, there are frequent problems until the user manually changes the output device in the settings:
- when the amp is on, the sound still goes through the internal speakers
- when the amp is off, there is...Using an HDMI audio power amplifier, there are frequent problems until the user manually changes the output device in the settings:
- when the amp is on, the sound still goes through the internal speakers
- when the amp is off, there is no sound at all
## How to reproduce
Fedora 28.
0. Turn on your laptop and open a GNOME session
1. Connect the computer to the audio amplificator through hdmi
2. Turn on the amp
The laptop screen turns off and on again.
3. open settings
5. go to audio settings
6. select the amp
Now you have audio throuhgh HDMI.
7. Turn off the computer
8. Disconnect HDMI and power off the amp
9. Power on the computer and open a new session
10. Use the keyboard shortcuts to set the sound level
The OSD shows the audio output is still HDMI, so there is no sound.
## Actual behavior
* The laptop screen flips when the amp turns on
* The audio output has to be manually changed every time the user connects or disconnects HDMI
## Expected behavior
The most relevant audio output is automatically selected: HDMI when available, then internal speakers
Ping @aday as I know he is working on the sound settings panel.https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2046Sound settings design updates2023-10-09T11:04:20ZAllan DaySound settings design updatesI've come up with some [updated designs for the Sound settings](https://gitlab.gnome.org/Teams/Design/settings-mockups/-/blob/master/sound/sound.png). They aim to resolve the main complaints that we get about the sound settings, and shou...I've come up with some [updated designs for the Sound settings](https://gitlab.gnome.org/Teams/Design/settings-mockups/-/blob/master/sound/sound.png). They aim to resolve the main complaints that we get about the sound settings, and should theoretically resolve #501, #817, #1305, #1762, #1584, #1910, #2033.
The main changes:
* Move the app volume levels into a secondary window
* Use standard AdwComboRows for device selection
* Remove the "system volume" slider, and move it into the device section, as "Output Volume"
* Move alert sound selection into a secondary windowhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/817Add test dialog for microphones2023-10-08T12:43:37ZOndrej HolyAdd test dialog for microphonesIt would be nice to have a "Test" dialog for input devices (i.e. microphones) similarly to what we have currently for output devices. The idea is to enable PulseAudio Loopback Device so one can check what is heard. I use [PulseAudio Loop...It would be nice to have a "Test" dialog for input devices (i.e. microphones) similarly to what we have currently for output devices. The idea is to enable PulseAudio Loopback Device so one can check what is heard. I use [PulseAudio Loopback Device](https://extensions.gnome.org/extension/954/pulseaudio-loopback-device/) extension for this purpose currently but would be nice to have this embedded.
/cc @adayhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2466Do not ask again for Select Audio Device2024-03-25T03:38:32ZPanderDo not ask again for Select Audio DeviceWhen using the audio jack a lot, mainly with the same type of device, i.e. headphones or head set, the user has to choose which audio device to use. This is dialogue could be omitted if the user indicates not to be ask about this anymore...When using the audio jack a lot, mainly with the same type of device, i.e. headphones or head set, the user has to choose which audio device to use. This is dialogue could be omitted if the user indicates not to be ask about this anymore.
This option is shown in the first mockup and will only be offered once the user has made at least one selection (between headphones or head set previously) with this dialogue.
Also once the user has made at least one choice, the option in to ask or not ask about this in the audio settings will appear, as shown in the second mockup.
A typical use case would be that a user with a laptop connecting at the same or multiple locations with a sound system. A related use case would be when a crappy audio plug or an accidental reconnect of the plug causes this selection dialog to appear (in the middle of a movie for example).
Implementing this will save the user time and prevent possible annoyance regarding this.
Proposed Mockups:
![select-dialog](/uploads/0f74bddf7607cb0c63fc5b34510fe1fd/select-dialog.png)
![select-settings](/uploads/1f4eb6b1c90d969a04f941fb69320ce0/select-settings.png)
## Design Tasks
* [ ] design tasks
## Development Tasks
* [ ] development tasks
## QA Tasks
* [ ] qa (quality assurance) taskshttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2317Ellipsized device and codec labels2024-03-14T15:34:36Zpiegamesgit@piegames.deEllipsized device and codec labelsThe content is clamped to a width that is too low, resulting in both poor screen space utilization and heavily ellipsed text.
The width is the same in all sub-panels, but I'll use the sound panel as an example because it has the largest...The content is clamped to a width that is too low, resulting in both poor screen space utilization and heavily ellipsed text.
The width is the same in all sub-panels, but I'll use the sound panel as an example because it has the largest content:
![image](/uploads/e352ff10af5366228ee2441832193484/image.png)
This is especially annoying because a) there is no way to enlarge the content and b) there is no way to read the ellipsed content. In my case, there are multiple values in the drop-down that start with the same text, the distinguishing part is cut off.https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/745Mouse-Scroll-Wheel Alters Drop-Down Selections During Scroll Navigation2021-03-09T19:34:47ZLonnie BestMouse-Scroll-Wheel Alters Drop-Down Selections During Scroll NavigationThe Gnome Sound Settings tab contains enough options to where you must scroll down to see them all.
Since the scrollbar is so narrow, I use my mouse-scroll-wheel to achieve this scroll navigation.
However, while scrolling with the inte...The Gnome Sound Settings tab contains enough options to where you must scroll down to see them all.
Since the scrollbar is so narrow, I use my mouse-scroll-wheel to achieve this scroll navigation.
However, while scrolling with the intention of "navigation", if the mouse-cursor passes over the Output Device drop-down-menu, or any of the slider controls, it inadvertently changes these settings.
The ability to change drop-down-menu selections, using the mouse-scroll-wheel is convenient in some cases, but it becomes problematic when the user is simply intending to do scroll navigation.
I can see a non-advanced user accidentally changing sound settings that they had no intention of changing in this design. Plus, even if they do notice the inadvertent changes, they may not know "what to change the settings back to".
A possible solution would be to disable modifications via scroll-wheel until the user has first explicitly clicked an option's sub-section.
Here's a video showcasing this issue:
https://youtu.be/Z6jNCCxC4hA
Downstream at Ubuntu: https://bugs.launchpad.net/bugs/1849880
![sound](/uploads/d11e0b807b1869ee27b302a639dcf020/sound.png)
```
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Fri Oct 25 12:29:32 2019
InstallationDate: Installed on 2019-10-19 (6 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
```https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/237Testing speakers with bluetooth HSP/HFP profile.2021-03-03T12:56:41ZGhost UserTesting speakers with bluetooth HSP/HFP profile.When I connect a bluetooth headset, set it as default sound output and set it to HSP/HFP profile, then click test button and click 'Mono' button in the appearing dialog, noise is played. paplay, mplayer and VLC play normal sound, (with d...When I connect a bluetooth headset, set it as default sound output and set it to HSP/HFP profile, then click test button and click 'Mono' button in the appearing dialog, noise is played. paplay, mplayer and VLC play normal sound, (with deteriorated quality as expected when using HSP/HFP) so this is a testing application issue. Problem exists both with native pulseaudio HSP support and with HFP support via ofono.https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2905Don’t split sentences2024-02-15T23:15:06ZAlexandre FrankeDon’t split sentencesIn [`panels/sound/cc-speaker-test-button.c`](https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/main/panels/sound/cc-speaker-test-button.c?ref_type=heads#L216)
```
/* Translators: This is the tooltip for a speaker test button, %s...In [`panels/sound/cc-speaker-test-button.c`](https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/main/panels/sound/cc-speaker-test-button.c?ref_type=heads#L216)
```
/* Translators: This is the tooltip for a speaker test button, %s is an already translated
speaker position, like "Front Left" or "Rear Center". */
tooltip_text = g_strdup_printf (_("%s Speaker"), pa_channel_position_to_pretty_string (position));
```
That may make it impossible to properly translate in some languages. [Never split sentences](https://wiki.gnome.org/TranslationProject/DevGuidelines/Never%20split%20sentences).https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2856Unable to get selected option when text is too long in sound panel2024-01-22T18:26:52ZKeyu TaoUnable to get selected option when text is too long in sound panel<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
Detailed description of the issue. Put as much information as you can, potentially
with images showing the issue.
-->
## Relevant information
* GNOME Settings version
<!-- Find with the command "gnome-control-center --version" -->
gnome-control-center 45.2
* Operating system (distribution)
<!-- Find with the command "cat /etc/os-release" -->
Arch Linux
* Error message
<!-- Reproduce the issue while running with the command "G_MESSAGES_DEBUG=all gnome-control-center" -->
N/A
* Backtrace (if you are experiencing a crash)
<!-- Check for instructions at https://wiki.gnome.org/GettingInTouch/Bugzilla/GettingTraces -->
N/A
* Screenshots
![image](/uploads/3572f8367a196db5a7a91efbd3c11fce/image.png)
(It's impossible to tell which configuration is chosen for my bluetooth earphone inside gnome-control-center, as here actually the AAC one is chosen)
## Steps to reproduce:
1. Open GNOME Settings and select Sound panel
2. Click on any CcProfileComboBox, and don't move mouse.
3. The first option is always highlighted even though another option is chosen (active).
## Note
This is also the case in gtk4-demo -> Combo Boxes, but not in "Lists -> Selections" (GtkDropDown). As GtkComboBox has been deprecated since Gtk 4.10, I guess a migrate from GtkComboBox to GtkDropDown or AdwComboRow might be necessary to help resolve this issue.
Some related discussion:
- https://discourse.gnome.org/t/gtk-combobox-dropdown-etc-no-longer-pre-select-active-item-on-popup/15445
- https://gitlab.gnome.org/GNOME/gtk/-/issues/5911
However, as GtkComboBox has been deprecated, I'm really not sure if I shall submit an issue to GNOME/gtk instead (seems not like a regression inside Gtk4, as I have tested with a Ubuntu 22.04 box, and looks like this behavior has been existed at least since Gtk4 4.6.9)...https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2344Sounds: Alert Sound row displays "Unknown" sound theme when Settings is opene...2023-11-22T11:51:10ZAutomeris naranjaSounds: Alert Sound row displays "Unknown" sound theme when Settings is opened for the first time## Steps to reproduce
1. Install GNOME OS Nightly
2. Open Settings > Sound
## Seen behavior
Alert Sound row displays a sound theme labeled as "Unknown". This only happens in a fresh install, when Settings is opened for the first time.
...## Steps to reproduce
1. Install GNOME OS Nightly
2. Open Settings > Sound
## Seen behavior
Alert Sound row displays a sound theme labeled as "Unknown". This only happens in a fresh install, when Settings is opened for the first time.
/cc @melix99
## Additional info
- GNOME OS Nightly
- Settings 44.alphahttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1283Switching default output device inconsistency2022-05-10T02:20:12ZTobias Frischjacki@thejackimonster.deSwitching default output device inconsistency<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/docs/CONTRIBUTING...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/docs/CONTRIBUTING.md#communication-guideline
-->
This issue got forwarded from [Pipewire](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/676) because it relies on a wrong behavior of gnome-control-center which Pulseaudio can handle with a [work-around](https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blob/master/src/modules/module-stream-restore.c#L2043) which is planned to be deleted.
So please fix this issue for more consistency with Pulseaudio and Pipewire.
------
Version, Distribution, Desktop Environment:
* pipewire 0.3.21-1, Archlinux, GNOME
Description of Problem:
* When I start video or audio in Firefox with multiple tabs, pause them and switch the default audio output device, not all tabs consistently change the output device.
* Also switching the default audio device doesn't visually reconnect anything in Carla (opened with pw-jack).
How Reproducible:
* Using a web browser with multiple tabs, playing multiple different audio sources (or video sources) while switching default audio output device.
Actual Results:
* The inactive tabs seem to keep old audio connections to the last device.
Expected Results:
* The tabs should use the given default device for playing audio if not set specifically different.https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1178Microphone Volume Over-Amplification Not Reflected in Settings2024-01-21T06:28:43ZRachit Keerti DasMicrophone Volume Over-Amplification Not Reflected in Settings<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version
* Does this issue appear in XOrg and/or Wayland
-->
Version Information
- OS: Ubuntu 20.10
- GNOME Version: 3.38.1
- Affected Versions: Wayland (XOrg not tested)
### Bug summary
The Microphone Volume allows over-amplification when the over-amplification option is switched on in Tweaks. However, the same is not reflected in control-center. While recording, one can increase the volume beyond 100% through the system dialog in top bar. However, control-center still shows Mic Volume as 100%.
### Steps to reproduce
1. Allow Over-Amplification in `gnome-tweaks`
2. Try to record something(Using Sound-Recorder or any other app) so that the mic indicator appears in the Top Bar
3. In the system dialog, increase mic volume to greater than 100%.
4. Open the sound panel, in settings. Observe mic volume is still showm as maximum(i.e. 100%).
### What happened
<!--
What did GNOME Shell do that was unexpected?
-->
Microphone volume is still shown as maximum(i.e. 100%).
### What did you expect to happen
Microphone Volume to be displayed correctly
### Relevant Screenshots
![Screenshot_from_2020-11-03_23-54-24](/uploads/f4e14d041f365a72f20fd2bbef06d82e/Screenshot_from_2020-11-03_23-54-24.png)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/898'sound' settings require changing device and back again2020-06-02T09:56:35ZMax Waterman'sound' settings require changing device and back again0. Plug in usb headphones
1. Open the settings
2. select 'sound'
3. observe 'output device'
4. attempt 'test' - notice no sound on 'output device'
5. attempt 'test' - notice sound on system speakers
6. switch output device to system spea...0. Plug in usb headphones
1. Open the settings
2. select 'sound'
3. observe 'output device'
4. attempt 'test' - notice no sound on 'output device'
5. attempt 'test' - notice sound on system speakers
6. switch output device to system speakers - no change
7. switch output device to usb headphones - 'test' sound is now on usb headphones
Ref: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1865862
I have two actual audio devices plugged in: 1. speaker under my monitor plugged into the 3.5mm headphone jack, 2. a set of USB headphones.
The 'Sound' settings panel shows three devices:
1. Headphones - built in audio
2. Digital output (s/pdif) - Jambra UC Voice 750 MS
3. Headphones - Jambra UC Voice 750 MS
(I don't really know what 2 is - I usually ignore it)
Normally, after plugging the headphones in, it has 3 selected, but the 'Test' button still plays through 1.
I have to change the 'output device' to 1, then back to 3 in order to make it work on 3.
So, this bug is that the control centre does not reflect reality when you launch it. It looks like it is automatically selecting the headphones just plugged in, but it hasn't actually changed.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 3 17:59:30 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-07-19 (227 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to eoan on 2019-10-28 (127 days ago)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/801Set default audio output device2024-01-21T06:27:24ZDavidSet default audio output deviceUbuntu 19.10
Open Control Panel
* Sound
* Output
* Set output device to the non-default device
* Music plays out ok
* Reboot PC
* Default device has changed back to first device
* Music does not play out ok :(
* Follow this gui...Ubuntu 19.10
Open Control Panel
* Sound
* Output
* Set output device to the non-default device
* Music plays out ok
* Reboot PC
* Default device has changed back to first device
* Music does not play out ok :(
* Follow this guide: https://rastating.github.io/setting-default-audio-device-in-ubuntu-18-04/
* It's bugging with Powermate Volume Device now.
If this has already been reported apologies.https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/784Use a minimum width for the volume sliders in Audio2023-01-24T14:56:45ZJimmy SciontiUse a minimum width for the volume sliders in AudioHi!
Look at this screenshot of the Audio panel: ![Schermata_da_2019-11-20_20-42-30](/uploads/471773be67ae08b915fca3e60231aadd/Schermata_da_2019-11-20_20-42-30.png)
Volume sliders are useless when that DosBox-etc is running.
Can you pl...Hi!
Look at this screenshot of the Audio panel: ![Schermata_da_2019-11-20_20-42-30](/uploads/471773be67ae08b915fca3e60231aadd/Schermata_da_2019-11-20_20-42-30.png)
Volume sliders are useless when that DosBox-etc is running.
Can you please set either a maximum width for the app-name label or a minimum width of the sliders?
Thanks!
edit:
Actually the issue also affects the other sliders in the same panel:
![Schermata_da_2019-11-20_20-46-22](/uploads/5bfb6e33f8ef29fa2580407ffaab9e71/Schermata_da_2019-11-20_20-46-22.png)https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/658PulseAudio Sink Selector2019-12-16T15:37:04ZAaron HoneycuttPulseAudio Sink SelectorI've noticed that when I switch audio devices in Settings app that the sink to which the audio is flowing is not always the same device that's selected for output. I work around this by selecting some other output device and then re-sele...I've noticed that when I switch audio devices in Settings app that the sink to which the audio is flowing is not always the same device that's selected for output. I work around this by selecting some other output device and then re-selecting the desired output device.
```
NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco
pulseaudio:
Installed: 1:12.2-9~disco1
Candidate: 1:12.2-9~disco1
Version table:
*** 1:12.2-9~disco1 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
1:12.2-2ubuntu3 500
```https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/494Custom audio routing is broken when changing default output devices2020-03-06T16:50:47ZWellington WallaceCustom audio routing is broken when changing default output devicesHi! PulseEffects https://github.com/wwmm/pulseeffects developer here
Gnome Control Center doesn't just change the default output device. It is also iterating over all audio apps and moving them to this new default. I understand this may...Hi! PulseEffects https://github.com/wwmm/pulseeffects developer here
Gnome Control Center doesn't just change the default output device. It is also iterating over all audio apps and moving them to this new default. I understand this may be interesting for users that do not apply any kind of effects to their sound. But when you move applications around like that you also totally break the custom audio routing done by dsp software like PulseEffects.
In my tests there was no problem using Pavucontrol. So the user could just use it instead of Gnome Control Center to change the default device. But I still think that it should at least be clear in Gnome Control Center interface that it isn't only changing the default Pulseaudio device.
Best regards,
Wellingtonhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2953sound: Enable users to use a custom alert sound2024-03-15T10:20:46Zdelthassound: Enable users to use a custom alert sound<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUC...<!--
Not following the communication guidelines [1] will mean your issue or comment
will be removed. Read it carefully before submitting this issue.
[1] https://gitlab.gnome.org/GNOME/gnome-control-center/blob/main/docs/CODE_OF_CONDUCT.md#communication-guidelines
-->
Following discussion in https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/2345 wrt adding back an alert sound that was previously in Gnome, @jimmac has suggested to enable users to select a custom alert sound.
@jimmac has designed a mockup in: https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commit/51233c745522260f35f85fe21a73a8891c8686dc
As shown in the design, the feature would have several aspects:
- Enable users to pick a file from the alert sound panel
- Enable users to select that picked sound or another, default sound
- Copy the file internally so that it still works after the file is deleted by the user