You are not logged in.
@stultumanto, spot the deliberate error in your 01:49:25 code block posting
Offline
I'll be honest, I don't even remember where I got that snippet. It made the EQ controls appear in greenjeans' app, but I didn't do listening tests. I'm guessing the second block should read type equal, not type plug. Why would someone put a deliberate error in there? Wait... did I get tricked into copying AI slop?!
Offline
@stultumanto
I'm guessing the second block should read type equal, not type plug
I couldn't identify which one was wrong, I have not played with 'equal' and order is important with ALSA or unwanted side-effects occur.
plug->equal->hw
or
equal->plug->hw
Offline
^^^Just for reference with the above posts, here's the new .asoundrc i'm shipping with Vuu-do and in AlsaTune, it's a bit more complex than the old one I used to use as it allows multi-sources to play at the same time.
I actually have version 2.0 of AT packaged and have been testing, but i'm agonizing today over making the soundswitch script more robust and capable to extend it's useability and try to avoid hand-editing of .asoundrc.
# Default: route through dmix > plug > equalizer > hardware
pcm.!default {
type plug
slave.pcm "dmixed_equal"
}
ctl.!default {
type hw
card 0
}
# Equalizer control (for mxeq GUI)
ctl.equal {
type equal
}
# Final EQ stage: applies to mixed output
pcm.dmixed_equal {
type equal
slave.pcm "dmixed_plug"
}
# Plug wrapper for format/rate conversion after dmix
pcm.dmixed_plug {
type plug
slave.pcm "dmixed"
}
# dmix: allows multiple playback streams > direct to hardware
pcm.dmixed {
type dmix
ipc_key 1024
ipc_key_add_uid false # safer than 0
slave {
pcm "hw:0,0"
period_time 0
period_size 1024
buffer_size 4096
rate 44100 # optional: lock rate if needed
}
bindings {
0 0
1 1
}
}
# Optional: dsnoop for multiple capture (mic) apps
pcm.dsnooped {
type dsnoop
ipc_key 1025
slave.pcm "hw:0,0"
}
# Optional: full duplex (for simultaneous play+capture)
pcm.duplex {
type asym
playback.pcm "dmixed_plug"
capture.pcm "dsnooped"
}
# Legacy: old names for compatibility/scripts
pcm.plugequal {
type equal
slave.pcm "plughw:0,0"
}
pcm.equal {
type plug
slave.pcm "plugequal"
}https://sourceforge.net/projects/vuu-do/ New Vuu-do isos uploaded October 2025!
Vuu-do GNU/Linux, minimal Devuan-based Openbox and Mate systems to build on. Also a max version for OB.
Devuan 5 mate-mini iso, pure Devuan, 100% no-vuu-do.
Devuan 6 version also available for testing.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
Offline
@greenjeans, I notice your new pcm.dmixed_equal section (equal->plug) is in the reverse order to your legacy name pcm.equal (plug->equal).
Is that intentional ?
NB Just checked my config, order is plug->equal
Last edited by g4sra (2025-11-25 17:53:06)
Offline
Good eye g4sra, I need to drop that section anyway, had to go over my notes to even remember why it's there, it was a holdover from some early testing I was doing on music player prototypes using aplay.
https://sourceforge.net/projects/vuu-do/ New Vuu-do isos uploaded October 2025!
Vuu-do GNU/Linux, minimal Devuan-based Openbox and Mate systems to build on. Also a max version for OB.
Devuan 5 mate-mini iso, pure Devuan, 100% no-vuu-do.
Devuan 6 version also available for testing.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
Offline
New 2.0 version uploaded : https://sourceforge.net/projects/vuu-do … /AlsaTune/
This has all the upgrades listed above and next version of the soundswitch script, includes the test tone .wav and a generic .asoundrc and updated notes about alsa and this system.

https://sourceforge.net/projects/vuu-do/ New Vuu-do isos uploaded October 2025!
Vuu-do GNU/Linux, minimal Devuan-based Openbox and Mate systems to build on. Also a max version for OB.
Devuan 5 mate-mini iso, pure Devuan, 100% no-vuu-do.
Devuan 6 version also available for testing.
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
Offline
Hi . I have only ALSA installed.
$ aplay --list-devices
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 0: ALC1220 Analog [ALC1220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 1: ALC1220 Digital [ALC1220 Digital]
Subdevices: 1/1
...
card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [VA3456-WQHD]
Subdevices: 1/1
Subdevice #0: subdevice #0
...
When i do a test :
$ aplay /usr/share/sounds/alsa/Front_Center.wav
i hear the sound from my headphones connected to my pc cases 3.5mm jack.
My monitor has speakers and i would like to make my programs use that as 'audio sink'.
How do i do that ?
Changing the card (with F6) in alsamixer i see a list of s/pdif rectangles but i dont know what they represent and also the display only 00.
Devuan(Chimaera)(Daedalus) DS+WM: XorgX11server+StumpVM
Offline
Some modern motherboards detect when headphones are plugged in and require different handling.
Without making alsamixer changes, can you hear sound from the speakers when the headphones are unplugged ?
i see a list of s/pdif
Most likely the HDMI audio output of your graphics card (but one could be optical if your motherboard supports it).
'00' means active, they have no volume setting, when you need to you can toggle to muted 'MM' by tapping 'm'.
Last edited by g4sra (Today 13:22:47)
Offline
Just FYI- I get no "Mic" control when using your mixer, because my system has no mixer element actually named "Mic." I have a "Headset Mic," a "Headphone Mic," and an "Internal Mic," but no "Mic." I also get no controls of any kind with my UMC202HD USB interface, because it uses non-standard element names. I know from experience it would add a lot of complexity to scan the mixer for the actual elements present on the device, but the alternative is going to be a certain number of users like me being unable to use the app with at least some devices.
Some modern motherboards detect when headphones are plugged in and require different handling.
This capability can be toggled on and off with the "Auto-Mute Mode" on many cards. alsamixer should expose this control. If it's "enabled," the speakers should be muted when headphones are plugged in. If you have more than one headphone output, there may be more than one option besides "disabled." It may take some experimentation to figure out which option you need.
Offline