Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[Poll] what is the plan for gnome 43 #258

Closed
ryzendew opened this issue Sep 7, 2022 · 54 comments
Closed

[Poll] what is the plan for gnome 43 #258

ryzendew opened this issue Sep 7, 2022 · 54 comments
Labels

Comments

@ryzendew
Copy link

ryzendew commented Sep 7, 2022

image
as you can see they really made gnome 43 menu ugly and i am hoping you guys don't give up and fix this mess

@kgshank
Copy link
Owner

kgshank commented Sep 7, 2022

Tried creating a Poll, but couldn't get it work. So react to the following comments and I can understand your expectations

@kgshank
Copy link
Owner

kgshank commented Sep 7, 2022

React to this comment, if you want me to
Continue maintaining the extension as is for Gnome 43
(Might me delayed as new gnome shell code is completely reworked)

@kgshank
Copy link
Owner

kgshank commented Sep 7, 2022

React to this comment, if you want me to
Augment Gnome 43 with additional features
(Comment on your desired features, so it will be easier for porting)

@kgshank
Copy link
Owner

kgshank commented Sep 7, 2022

React to this comment, if you want me to
not maintain the Extension for Gnome 43
(Will be maintained for Gnome < 42)

@kgshank kgshank changed the title what is the plan for gnome 43 [Poll] what is the plan for gnome 43 Sep 7, 2022
@kgshank kgshank added the Poll label Sep 7, 2022
@ryzendew
Copy link
Author

ryzendew commented Sep 7, 2022

Weird we can’t react ..

@kgshank kgshank pinned this issue Sep 7, 2022
@kgshank
Copy link
Owner

kgshank commented Sep 7, 2022

Weird we can’t react ..

I am not sure whats wrong, can you add an +1 comment with the option you need

@frandieguez
Copy link

frandieguez commented Sep 9, 2022

Augment Gnome 43 with additional features

The default look now is awesome but I lack your extension preferences. So if you basically allow users to change which elements are shown in the menu (show audio profiles, show/hide icons, hide certain output devices), I'm happy with it.

@thesmallcreeper
Copy link
Contributor

So from what I see Gnome 43 allows functionality familiar to "Integrate selector with slider", haven't tested it yet.
https://www.omglinux.com/gnome-43-makes-it-much-easier-to-switch-audio-device/

In my opinion, since Gnome is willing to offer such functionality, additional features should be added to Gnome directly (not via extension). However that can be difficult because Gnome maintainers might don't want to get user experience bloated. So
augment Gnome 43 with additional features might be the only option.

@ryzendew
Copy link
Author

gnome 43 did a horrible ugly job nothing changes that it's like it was made by a child and doesn't look good at all so i hope you fix it and de-ugly it

@YangtseSu
Copy link

Add the selection of audio inputs.

@razzeee
Copy link

razzeee commented Sep 25, 2022

I would really like to see current input output levels on each device, as that would make selecting the correct one easier. And it might also lead to the gnome devs being able to see if that's something they want to expand on.

@hendersj
Copy link

hendersj commented Sep 27, 2022

I would agree that audio input/output levels per device would be nice. Also being able to rename the devices with a descriptive name (I don't know which monitor my "HDMI / DisplayPort 3" device is, but if I can name it "Dell Widescreen Monitor" once and forget about it, that would make life so much easier).

Input devices also would be very good to have. It's one of the things I really like about this extension.

@razzeee
Copy link

razzeee commented Sep 27, 2022

The gnome implementation has input devices. But they are only showing, if it's active, so you have to have an app that's actually accessing the input, for it to show up in quick settings.

@hendersj
Copy link

That's kinda ugly, though, if you're wanting to select your input device before you start, say, a Zoom meeting....

@razzeee
Copy link

razzeee commented Sep 27, 2022

Feel free to voice your oppinion here then https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5913
I guess we'll can get it to open up again if enought people feel like that.

@hendersj
Copy link

I'd be fine if this extension did it instead. Doesn't have to be part of the core GNOME functionality. :)

@skgsergio
Copy link

I've been testing GNOME 43 and, design aside, what I mostly miss is the Input/Mic selector even when it is not in use.

I use this since my Headset has two profiles (Headphone and Handsfree) and for example, Microsoft Teams Web if the input change is not done beforehand when a call kicks in it doesn't list the Handsfree input device (yes, it is probably MS Teams fault, but I bypass this by changing first the input to the Handsfree).

@jim-moe
Copy link

jim-moe commented Oct 15, 2022

I have found your extension to be a reliable way to change the sound in-/output. Using the Gnome settings for sound rarely actually changes the setting; quite annoying. With the advent of Gnome 43, I have no way to change the sound settings.

@sezcl
Copy link

sezcl commented Oct 16, 2022

+1 gnome 43 support.

@kpfleming
Copy link

The most recent release of GNOME Shell for GNOME 43 does have the ability to choose an output device from the Quick Settings widget (whether it works for @jim-moe or not is a different question!). It does not have the ability to do so for the input device unless an application is actively capturing input, which was the primary reason why I used this extension in the first place.

If we can convince the GNOME Shell team to give us a way to have the input device selector always visible in Quick Settings then I'd be satisfied with that and would not need an upgraded version of this Extension. It's sad to say that as it has served me very well for man years...

@jim-moe
Copy link

jim-moe commented Oct 18, 2022

Hmm @kpfleming. I presume you mean the settings menu at the top left (of my screen)? If so, there is no option for selecting an in- or output device.

@kpfleming
Copy link

image
This is what the new Quick Settings widget looks like on my system with GNOME 43; the arrow to the right of the volume slider for the output is what I can click to select an output device.
image

@jim-moe
Copy link

jim-moe commented Oct 18, 2022

Well. I fell silly. So it is here as well.

@kpfleming
Copy link

No worries, it's not as obvious as it could be and the GNOME team has some more work to do there. It's still not as good as the extension is, for example right now I have two 'Analog Output' devices listed in the Quick Settings panel with no way to distinguish them (not even a tooltip when hovering over them).

@carlwgeorge
Copy link

Augment Gnome 43 with additional features

This approach seems like it would make far more sense. Doing anything else would probably make the extension harder to maintain and more likely to break with subsequent Gnome Shell releases.

(Comment on your desired features, so it will be easier for porting)

The most important feature for me personally would be the ability to hide/disable some input/output devices. For example, I never want to select my webcam's microphone, yet Gnome 43 seems to default to that on my workstation.

@muttleyxd
Copy link

One thing that is missing in Gnome 43 is any kind of hint, which device is the 'host' of given audio output/input.

I have several different audio output devices (microphone with loopback, HDMI/DisplayPort, integrated sound card, external DAC) and I can't tell which "Digital Output (S/PDIF)" is the one, that I want.

Gnome 43 audio settings

This extension was doing that just fine on Gnome 42, so I think that's one place where it could extend Gnome 43.

@darkdragon-001
Copy link

One thing that is missing in Gnome 43 is any kind of hint, which device is the 'host' of given audio output/input.

I have several different audio output devices (microphone with loopback, HDMI/DisplayPort, integrated sound card, external DAC) and I can't tell which "Digital Output (S/PDIF)" is the one, that I want.

Gnome 43 audio settings

This extension was doing that just fine on Gnome 42, so I think that's one place where it could extend Gnome 43.

@muttleyxd This looks like something which should be filed as a bug upstream as well. Of course this shouldn't stop this extension from fixing this until an upstream patch is ready.

@skgsergio
Copy link

Regarding no distinction between outputs/inputs there is a bug filled upstream and a maintainer said that it will be fixed in 43.1: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5829

@skgsergio
Copy link

As expected the disambiguation of inputs/outputs landed at 43.1:

image

@lviggiani
Copy link

As expected the disambiguation of inputs/outputs landed at 43.1:

image

Hi I just wanted to try it on gnome 43.1 (I've got it on Arch). I see that there's a branch named 43 but it seems identical to master also metadata.json doesn't list 43 among the compatible versions. So the question is, can I manually add 43 to metadatra.json in master or branch 43 or is there anything else I have to do? Thanks!

@razzeee
Copy link

razzeee commented Nov 9, 2022

@lviggiani that has been fixed in gnome itself and not in this extension

@lviggiani
Copy link

lviggiani commented Nov 9, 2022 via email

@carlwgeorge
Copy link

@lviggiani The easiest way to test would be to set the key /org/gnome/shell/disable-extension-version-validation to false using either the dconf-editor app or the dconf CLI tool. Then Gnome will allow you to load extensions who don't list the current shell version as compatible in their metadata.json file.

@lviggiani
Copy link

@lviggiani The easiest way to test would be to set the key /org/gnome/shell/disable-extension-version-validation to false using either the dconf-editor app or the dconf CLI tool. Then Gnome will allow you to load extensions who don't list the current shell version as compatible in their metadata.json file.

Sorry maybe I said that badly. I managed "starting" the extesion by adding the entry to metadata.json, but it gives this error:
this._aggregateMenu is undefined that I think has to do wtih GS 43 compatibility

@feimosi
Copy link

feimosi commented Nov 13, 2022

It'd be great to have this extension working because the new Gnome 43 menu doesn't allow switching the microphone source :/

@razzeee
Copy link

razzeee commented Nov 13, 2022

@feimosi *when your not using the microphone

@skgsergio
Copy link

@razzeee yes, but for some use cases is important to have it when not using it.

For example in MS Teams Web if I change my Bluetooth headset from the headphones profile (high audio quality, no mic) to headset (audio+mic) once it started capturing the mic I have to re join the meeting to start using the headset mic instead the laptop mic.

I used to change the audio output and input before joining a meeting with this extension.

For me, permanent input selection is the only thing I miss in vanilla GNOME 43.

@razzeee
Copy link

razzeee commented Nov 13, 2022

@skgsergio we already talked about that above and I think someone also raised the issue on the gnome tracker.

@ryzendew
Copy link
Author

ryzendew commented Nov 14, 2022

Gnome never gives us what we need but this extension can plus even if they did it would never be done right { salty clowns can’t handle the truth as always }

@jwest75674
Copy link

Additional Feature Request:
Would love to prioritize input and output devices, such that both are decided upon automatically.

@lig
Copy link

lig commented Nov 15, 2022

@jwest75674 that would be really neat feature to have. I've ended up blacklisting some devices in pulseaudio and configuring fallbacks manually to achieve what I need.

@jrom99
Copy link

jrom99 commented Nov 17, 2022

Another thing that's really nice about this extension is the ability to select different profiles within a device, as this enables a soft profile reset, as well as the ability to hide useless devices and profiles.

My laptop has a nasty bluetooth bug where it changes my output device to a headset, but since GNOME doesn't recognize this change, the default A2DP profile is still selected. With the extension I was able to easily change profiles within A2DP and it'd go back to normal. Bonus points that I could also hide the headset device option, since my headphone doesn't even have a microphone.

@pablorq
Copy link

pablorq commented Nov 29, 2022

Just move the extension outside the new gnome panel and make it accessible directly. It also make the extension free from future changes on gnome.
I could be a new icon on the top bar, like pulse-audio-shortcuts extension.

@enricojonas
Copy link

Additional Feature Request:

Have 3 lists:

  • output devices (just like in current extension)
  • input devices (just like in current extension)
  • profiles (a link between input and output devices).

So we should be able to link input and output devices together. In my case I use 4 devices mainly:

  • stereo speaker output and webcam mic input
  • headset output and input

That means I always need to switch input AND output devices when I put on my headset (which is kind of annoying). Instead it would be great to have profiles so we can link inputs and outputs together and both get automatically selected if you select a profile.

If this feature would be implemented there should be an option to hide input / output list and only display profile list.

So yes for now I am stuck with going to the settings menu to change mic (as I just updated to Ubuntu 22.10).

@QmwJlHuSg9pa
Copy link

QmwJlHuSg9pa commented Dec 6, 2022

Just move the extension outside the new gnome panel and make it accessible directly. It also make the extension free from future changes on gnome.

Agreed. The Quick Settings menu is overloaded as it is (in both functionality and visual noise). Given that this extension is geared towards "power users", a bespoke, customisable menu would be ideal--in terms of ease-of-use and muscle memory.

It would also be nice to have options for the following:

  • Force the location of volume sliders (absolute top, absolute bottom, or default behaviour),
  • Expand device lists by default (either output, input, or both),
  • As others have mentioned, profile selection directly from the device lists

@kgshank
Copy link
Owner

kgshank commented Dec 6, 2022

Thanks for all the suggestions. Making it as a separate indicator makes more sense going forward, than depending on the Gnome implementation for volume sliders and device selection. I wanted to push some update before November, but couldn't spend much time with the extension. Unfortunately, I have other plans till end of January, so the updates will be further delayed. I hope to push something before the next Gnome release at least.

@iadegesso
Copy link

The one in GNOME 43 is buggy,, please port your extension to the newest GNOME

@esa1975
Copy link

esa1975 commented Jan 1, 2023

My vote is to augment the existing layout in 43. I don't mind the direction they are taking but I do miss being able to easily choose audio devices. Thanks for asking for feedback from your users. Happy new year to you!

Edit: I hadn't read all the conversations above. I agree that a separate icon that allows switching makes the most sense and hopefully simplifies development a bit which might make time available for things like defaults with automatic switching and profiles.

@jmswick
Copy link

jmswick commented Jan 18, 2023

The primary feature I really liked using this extension for was to disable the automatic switching to certain devices. I have a USB Video capture device that has its own audio i/o, and don't want my system switching to those when I plug it in.

The default/fallback feature would be a nice addition to designate a device to always switch to when connected. For example, I have a Makie Studio monitor w/USB audio that I switch between multiple computers, and would like to have a way to ensure when that device is plugged in, it is always switched to for audio in/out.

@7system7
Copy link

7system7 commented Feb 11, 2023

For me, the GNOME 43's solution has been worked until the first minor version. Since then, I have one chance to change the sound output. 🤣 After that I have 2 options

  1. I satisfied my chosen option forever
  2. Reboot my computer or restart the shell and change again
  3. Actually I have a third option: go to the global sound settings and change the output there
Screencast.from.2023-02-11.12-16-49.webm

Jokes aside; it is so boring that, in 2023 the GNOME team cannot implement anything without a massive bug. So.. I created a shortcut for the sound options.

@altsalt
Copy link

altsalt commented Feb 13, 2023

I find this extension incredibly useful and am torn between spending additional time on features and just getting it out the door for 43. Either way, thanks to everyone for putting their time into it!

Two feature requests I'd like to see eventually:

  1. Detection of status and quick links to restart underlying sound services without opening a terminal.
  2. Integration with something like Helvum to do enable a visual patchbay interface.

@kgshank
Copy link
Owner

kgshank commented Mar 14, 2023

I had to take a longer break from the development than I expected, due to both personal and professional reasons. The sad part that code that I was working for v43 was lost, as I had to format my machine. Now I am starting again from scratch. So I might have to skip 43 already completely and probably release for 44 directly. I hope there are no delays further. Thanks everyone for your support and participation

@brianjmurrell
Copy link

Hopefully preaching to the choir here but also hopefully the lesson learned is to create a branch on GH for your development and push to it frequently (i.e. at least daily). In that case, even with a re-format of your machine, your work would not have been lost.

@jose1711
Copy link
Contributor

I think has to do wtih GS 43 compatibility

Yup, namely this commit removing aggregateMenu: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/a4134e1559c3f59bd0d553703e5d3b1f7a28d703

Repository owner locked and limited conversation to collaborators Sep 13, 2023
@kgshank kgshank converted this issue into discussion #271 Sep 13, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests