KLV-Spectr-RT with full real-time kernel 6.1.38-rt13c

[rockedge]

right click on the volume icon opens Pavucontrol

right-click is working for me, only the percentage value digits are missing. Otherwise pipewire audio is working and pavucontrol is running smoothly.

[Sofiya]

Installed Pipewire as described by @fredx181 viewtopic.php?p=99178#p99178 .

I don't remember where I read that pnmixer xbps-install -Su pnmixer works well with Pipewire. The test showed that this is indeed the case
pnmixer is registered in autostart .spectrwm.conf

when viewing in lxtask, it was noticed that the process with wireplumber exists and is running. Therefore, it was commented out in xinitrc .
if I uncomment it there, then I will have a high load on the processor.

The sound works well, the only thing is that my favorite equalizer does not work now.

Code: Select all

pipewire &
pipewire-pulse &
#wireplumber &
/usr/local/bin/start-up &
spectrwm

[Sofiya]

registered in autostart .spectrwm.conf removed in xinitrc

amendment:
no, it’s still better if they are in xinitrc - pipewire and pipewire-pulse

[geo_c]

Pictured here is a further trimmed down key-binding file with only the key strokes and action. I have it pasted in a gtk-dialog script, which is less than ideal. It displays the text when the window is floated, but when in the stack the text is not visible or only partly visible. When I float the window it comes out huge, far beyond the text boundaries, and has to be resized.

Since wmctrl is installed, I wonder if I could add lines that float the window automatically, and maybe size it? Spectr is limited in what it accepts from wmctrl I believe.

Spectr-keybindings-small.fake.gz

(2.26 KiB) Downloaded 12 times

However it does work once floated.

You'll notice I also have a gtk-dialog displaying the system name and clock. I have both of these in /root/Startup so they open on boot in workspace 1.

[Sofiya]

Works well so far
It seems like Pipewire is better than Pulse

[Sofiya]

I can’t understand why the parameter ( --list-targets ) shows that the parameter is unrecognized .The volume is adjustable, everything else also works, but the output does not work We have some kind of wrong Pipewire or something?

/root/.config/polybar/scripts/pipewire.sh

Code: Select all

#!/bin/bash

function main() {
    # Pipewire
    SOURCE=$(pw-record --list-targets | sed -n 's/^*.*"\(.*\)" prio=.*$/\1/p')
    SINK=$(pw-play --list-targets | sed -n 's/^*.*"\(.*\)" prio=.*$/\1/p')
    VOLUME=$(pactl list sinks | sed -n "/${SINK}/,/Volume/ s!^[[:space:]]\+Volume:.* \([[:digit:]]\+\)%.*!\1!p")
    IS_MUTED=$(pactl list sinks | sed -n "/${SINK}/,/Mute/ s/Mute: \(yes\)/\1/p")

    action=$1
    if [ "${action}" == "up" ]; then
        pactl set-sink-volume @DEFAULT_SINK@ +5%
    elif [ "${action}" == "down" ]; then
        pactl set-sink-volume @DEFAULT_SINK@ -5%
    elif [ "${action}" == "mute" ]; then
        pactl set-sink-mute @DEFAULT_SINK@ toggle
    else
        if [ "${IS_MUTED}" != "" ]; then
            echo " ${SOURCE} |   MUTED ${SINK}"
        else
            echo " ${SOURCE} |    ${VOLUME}% ${SINK}"
        fi
    fi
}

main $@

/root/.config/polybar/config

Code: Select all

[module/pipewire]
type = custom/script
label = "%output%"
label-font = 2
interval = 2.0
exec = ~/.config/polybar/scripts/pipewire.sh
click-right = exec pavucontrol &
click-left = ~/.config/polybar/scripts/pipewire.sh mute &
scroll-up = ~/.config/polybar/scripts/pipewire.sh up &
scroll-down = ~/.config/polybar/scripts/pipewire.sh down &
format-underline = #3EC13F
format-foreground = ${colors.foreground}
format-background = ${colors.background}

################################################################################

[Sofiya]

and everything is clear why https://github.com/polybar/polybar-scripts/issues/369
ruined everything all around well, let's use pnmixer

[Sofiya]

I’m increasingly noticing that there is no consistency, everyone does what they want. I wanted to insert the code, I wanted to throw it out, and you just sit and write new scripts. Idiocy . for that matter, there is nothing better than Pulseudio .I’m already thinking that at some point something will happen to Vayland

[geo_c]

I’m increasingly noticing that there is no consistency, everyone does what they want. I wanted to insert the code, I wanted to throw it out, and you just sit and write new scripts. Idiocy . for that matter, there is nothing better than Pulseudio .I’m already thinking that at some point something will happen to Vayland

Do you mean pipewire? Or are there components of wayland in pipewire that are problematic in X?

I like pulse audio also. It's proven to work well with gui controls allowing quick switching between audio inputs/outputs and applications.

pipewire to me seems interesting as a replacement for jack audio server because it allows piping audio streams between applications.

That being said, at this point I'm content and even prefer to use audio applications that aren't jack dependent.

[Sofiya]

in /root/.config/polybar/config

Code: Select all

[module/pipewire-control-output]
type = custom/script
tail = true
;label-padding = 2
format-underline = #3EC13F
format-foreground = ${colors.foreground}
format-background = ${colors.background}

# Icons mixed from Font Awesome 5 and Material Icons
# You can copy-paste your options for each possible action, which is more
# trouble-free but repetitive, or apply only the relevant ones (for example
# --node-blacklist is only needed for next-node).

exec = pipewire-control --icons-volume " , " --icon-muted " " --node-nicknames-from "device.description" --node-nickname "alsa_output.pci-0000_00_1b.0.analog-stereo:  Speakers" --node-nickname "alsa_output.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.analog-stereo:🎧  Headphones" listen 
click-right = exec pavucontrol &
click-left = pipewire-control togmute
click-middle = pipewire-control --node-blacklist "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra2" next-node
scroll-up = pipewire-control --volume-max 110 up
scroll-down = pipewire-control --volume-max 110 down

################################################################################

in /usr/local/bin

[Sofiya]

[geo_c]

added these two keybindings to spectrwm.conf. I guess they got lost in the shuffle:

Code: Select all

 bind[iconify]			= MOD+MOD1+i
 bind[uniconify]		= MOD+Shift+i
 

When uniconify is used, it brings up dmenu as the bar and lists all the open windows, I suppose one could use rofi just as easy, but the keystrokes are probably quicker.

As primitive an approach as it is, my gtkdialog window displaying keybindings is very helpful. Once floated and sized is always there for reference.

[rockedge]

@Sofiya I like pulseaudio in KLV-Spectr, and when it's up and running works well. But I have yet to see the pulseaudio daemon start consistently during the system startup. So I am testing out pipewire but added on with an SFS so it can be removed and only pulseaudio will be used.

If I can get a mechanism that will start pulseaudio correctly every time at system boot then I'd consider having 2 versions or just have the pipewire as an option by adding the SFS.

No matter what I have as a script or what method I am trying to automatically start up pulseaudio with, sometimes it works and sometimes it doesn't. I also have pulseaudio daemon just disappearing on occasion.

We fix that then we can stick with a pulseaudio version with the possibility to switching to pipewire. As of now because no matter what sleep value I use or what autostart method to trigger pulseaudio, it is working around 50% of time during the boot cycle and I have to manually start it. Sometimes as spot some times as root.....all I know it's bothersome and a drag that I've been looking at for awhile now.

[Sofiya]

@Sofiya I like pulseaudio in KLV-Spectr, and when it's up and running works well. But I have yet to see the pulseaudio daemon start consistently during the system startup. So I am testing out pipewire but added on with an SFS so it can be removed and only pulseaudio will be used.

If I can get a mechanism that will start pulseaudio correctly every time at system boot then I'd consider having 2 versions or just have the pipewire as an option by adding the SFS.

No matter what I have as a script or what method I am trying to automatically start up pulseaudio with, sometimes it works and sometimes it doesn't. I also have pulseaudio daemon just disappearing on occasion.

We fix that then we can stick with a pulseaudio version with the possibility to switching to pipewire. As of now because no matter what sleep value I use or what autostart method to trigger pulseaudio, it is working around 50% of time during the boot cycle and I have to manually start it. Sometimes as spot some times as root.....all I know it's bothersome and a drag that I've been looking at for awhile now.

mm... this is strange, I’ve been using Spectrwm for 5 days now and I haven’t had any crashes with Pulseudio, either when loading or when idle and working

[Sofiya]

in the vastness of Github I came across darls-10.0.84, which is somewhat similar to our Spectrwm
production @dimkr

[rockedge]

@Sofiya can you show me what your pulseaudio setup looks like? The start scripts and there are no pipewire pieces at all in the rootfs?

I need a fresh rootfs that only has pulseaudio going. This way we can develop the pipewire in the background and release an ISO that has pulseaudio solid and is separate.

I think we can leave the pipewire components in and just start pulseaudio and not pipewire unless the SFS is added in.

[Sofiya]

@Sofiya can you show me what your pulseaudio setup looks like? The start scripts and there are no pipewire pieces at all in the rootfs?

I need a fresh rootfs that only has pulseaudio going. This way we can develop the pipewire in the background and release an ISO that has pulseaudio solid and is separate.

I think we can leave the pipewire components in and just start pulseaudio and not pipewire unless the SFS is added in.

I already have full Pipewire. I don’t have sfs. And this is already saving

[rockedge]

you have pipewire installed but only a pulseaudio startup script in /root/Startup ?

I also have all of the pipewire parts installed in the rootfs, but the pipewire startup scripts are in the SFS.

[Sofiya]

you have pipewire installed but only a pulseaudio startup script in /root/Startup ?

I also have all of the pipewire parts installed in the rootfs, but the pipewire startup scripts are in the SFS.

Code: Select all

#!/bin/sh

sleep 1
exec pulseaudio --start &

Code: Select all

#!/bin/bash

exec /usr/lib/polkit-1/polkitd --no-debug 

[rockedge]

@Sofiya this is what I have in /root/Startup

Screenshot(31).jpg (21.01 KiB) Viewed 4269 times

Code: Select all

#!/bin/bash
exec /usr/lib/polkit-1/polkitd --no-debug

Code: Select all

#!/bin/sh

sleep 7
exec pulseaudio --start 

[rockedge]

@Sofiya I am not sure yet what got this to happen:

Screenshot(39).jpg (45.27 KiB) Viewed 4245 times

This is underneath the polybar:

Screenshot(37).jpg (10.01 KiB) Viewed 4264 times

[geo_c]

@Sofiya can you show me what your pulseaudio setup looks like? The start scripts and there are no pipewire pieces at all in the rootfs?

I need a fresh rootfs that only has pulseaudio going. This way we can develop the pipewire in the background and release an ISO that has pulseaudio solid and is separate.

I think we can leave the pipewire components in and just start pulseaudio and not pipewire unless the SFS is added in.

For what it's worth, ever since I imported @Sofiya's spectrwm-polybar4.4 scripts (which contain pulse startup scripts) into my Spectr-beta2 PFI build, pulseaudio has been working flawlessly. No pipewire on my system though.

[rockedge]

Right now pulseaudio has been working. I am using spectrwm-polybar4.4 scripts as well. The pipewire stuff is installed but not used

I have to check why there is a bar under polybar all of a sudden.

[geo_c]

Right now pulseaudio has been working. I am using spectrwm-polybar4.4 scripts as well. The pipewire stuff is installed but not used

I have to check why there is a bar under polybar all of a sudden.

Is that the desktop switcher? Maybe you opened it with a keystroke MOD+/

[geo_c]

Right now pulseaudio has been working. I am using spectrwm-polybar4.4 scripts as well. The pipewire stuff is installed but not used

I have to check why there is a bar under polybar all of a sudden.

Is that the desktop switcher? Maybe you opened it with a keystroke MOD+/

I disable Rox as the pinboard in the spectrwm config. I don't use it as a pinboard anymore. That might have something to do with it.

[Sofiya]

@Sofiya I am not sure yet what got this to happen:
Screenshot(39).jpg

This is underneath the polybar:
Screenshot(37).jpg

this should be under the half bar, the size of the top bar should be 30 line 63 in /root/.config/polybar/config
if you are using version 4.4 then everything is set correctly there

[Sofiya]

Right now pulseaudio has been working. I am using spectrwm-polybar4.4 scripts as well. The pipewire stuff is installed but not used

I have to check why there is a bar under polybar all of a sudden.

This is not a strip, this is a spectrwm panel, you can’t put it anywhere, we have it involved in the spectrwm configuration file
if you turn off the spectrwm panel, the top of the windows will hide behind the polybar panel

[rockedge]

I increased the height to 40, which seems to fix it. I reduced the sleep to 1 second on the pulseaudio start up. I commented out the rox --pinboard startup.

I'm not sure I like the MOD4 better than MOD1. With MOD4 configured there is a conflict when running in a QEMU virtual machine with the host F96-CE_4 controls.
To prevent it I must go into full screen mode which is okay but not ideal for me. When MOD1 is configured I have better control with less conflicts between the QEMU machine and the host.

Otherwise I like the overall configuration which I am testing out. I will boot on a bare metal machine once I have the small things fixed up.

[geo_c]

I increased the height to 40, which seems to fix it. I reduced the sleep to 1 second on the pulseaudio start up. I commented out the rox --pinboard startup.

I'm not sure I like the MOD4 better than MOD1. With MOD4 configured there is a conflict when running in a QEMU virtual machine with the host F96-CE_4 controls.
To prevent it I must go into full screen mode which is okay but not ideal for me. When MOD1 is configured I have better control with less conflicts between the QEMU machine and the host.

Otherwise I like the overall configuration which I am testing out. I will boot on a bare metal machine once I have the small things fixed up.

I think MOD4 (if that means the Super) is better than MOD1, because the Alt key conflicts with a lot of applications. My final keybindings are working really well and application's keybindings also working smoothly.

If you want I'll cut them out of my spectrwm.conf and post it with the final keybinding-list.

[Sofiya]

I increased the height to 40, which seems to fix it. I reduced the sleep to 1 second on the pulseaudio start up. I commented out the rox --pinboard startup.

I'm not sure I like the MOD4 better than MOD1. With MOD4 configured there is a conflict when running in a QEMU virtual machine with the host F96-CE_4 controls.
To prevent it I must go into full screen mode which is okay but not ideal for me. When MOD1 is configured I have better control with less conflicts between the QEMU machine and the host.

Otherwise I like the overall configuration which I am testing out. I will boot on a bare metal machine once I have the small things fixed up.

if you are testing on Qemu and trying to configure it, this is a bad idea. I have all the settings exactly set. Launch and configure on normal hardware