Volume module

[olifloof]

A volume module with a popup widget that has a slider. option to choose backend (wpctl, pactl, etc). usage of on-scroll events to change volume without opening the widget.

[JakeStanger]

Happy to add this. I'd like to see if I can get a proper mixer too (like the Win7 one) allowing you to change input/output/program volumes individually where supported (ie Pulse or Pipewire).

[olifloof]

That would be nice

[p00f]

Happy to add this. I'd like to see if I can get a proper mixer too (like the Win7 one) allowing you to change input/output/program volumes individually where supported (ie Pulse or Pipewire).

What if you just open pavucontrol on click

[JakeStanger]

That could be achieved currently with the custom module without much work.

My intention for any "proper" modules is that they offer a more integrated experience, and don't rely on external software where possible. Also, I've started work on the client code for this already :)

[JakeStanger]

Going to push this back to the next milestone because PulseAudio is painful to work with and it's draining. Want to work through some of the issues to avoid stagnation. I'll stick up a temporary custom module config that works with pavucontrol in the meantime.

[Phant80m]

how do i get the buttom to display the audio.

[JakeStanger]

Nothing has been implemented yet

[yavko]

I think a good starting point would be replicating what kde does, though I think kde's design isn't perfect so maybe could be built on

[Phant80m]

hmmmm

[Pyvonix]

A bar that already implement a good volume's widget is the waybar with its PulseAudio plugin that offer an easy to:

• format the current volume,
• select an icon depending the used sound output/input,
• let the user choose its sound mixer.

That could be a good reflection way.
And will be amazing to see something similar in Ironbar!

[yavko]

A bar that already implement a good volume's widget is the waybar with its PulseAudio plugin that offer an easy to:

• format the current volume,
• select an icon depending the used sound output/input,
• let the user choose its sound mixer.

That could be a good reflection way.
And will be amazing to see something similar in Ironbar!

Waybar's doesn't have a GUI tho. Plus you could already do the same as waybar does with ironbar's built in features.

[Pyvonix]

Waybar's doesn't have a GUI tho.

Both bars are made on the top of GTK. It's true that Waybar doesn't have real "GUI" (if you mean possibility to pop a box or container), but with some Wayland's trick (catching the window' name) you could make the mixer appear as floating windows the desired position. Realized with pavucontrol on Sway the result is transparent.

Plus you could already do the same as waybar does with ironbar's built in features.

Not completely agree.
After a very painful configuration, I was able to achieve something "like" a mixer using: button, label and progress based on the doc's example. But why doesn't offering {volume} keyword like the sys_info module did?

And I will point out for the moment I haven't found a way dynamically changes an icon depending the audio output (e.g. headphones, speakers, etc... ) or the audio level (e.g. mute, low, high, ...).
I didn't look into using an external script because I really don't like doing it that way.

I'd really like ironbar and there are little things that could make it even better.

[JakeStanger]

But why doesn't offering {volume} keyword like the sys_info module did?

This is achievable using an ironvar and/or script currently.

And I will point out for the moment I haven't found a way dynamically changes an icon depending the audio output (e.g. headphones, speakers, etc... ) or the audio level (e.g. mute, low, high, ...).

Image sources in the custom module are dynamic strings, which means you can set them via script or ironvar and they will update automatically (in theory).

I understand not wanting to rely heavily on scripts, as it does add some performance and maintenance overhead. That's why I want a native module :)

The thing is with the volume module is almost all the work is getting a working client. Once that's done, the rest of the implementation should be relatively straightforward; I may not release a full mixer interface immediately but I'd want the ability to show and change master volume for the current output device at a minimum. Unfortunately I've not had much time recently to look at this, and any previous attempts have mostly involved banging my head against walls so it might be a while still.

[JakeStanger]

I've just opened a draft PR (linked above) with the initial version of the module. It's not quite complete, but stable enough to start playing around with. Full details in the PR.