ALSA-only purists: Question, new GUI app for the mixer and EQ?

g4sra · Yesterday 09:47:46

@stultumanto, spot the deliberate error in your 01:49:25 code block posting

stultumanto · Today 09:40:04

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?!

g4sra · Today 13:27:40

@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

greenjeans · Today 17:20:39

^^^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"
}

g4sra · Today 17:51:18

@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 (Today 17:53:06)

greenjeans · Today 18:38:02

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.

The officially official Devuan Forum!

#51 Yesterday 09:47:46

Re: ALSA-only purists: Question, new GUI app for the mixer and EQ?

#52 Today 09:40:04

Re: ALSA-only purists: Question, new GUI app for the mixer and EQ?

#53 Today 13:27:40

Re: ALSA-only purists: Question, new GUI app for the mixer and EQ?

#54 Today 17:20:39

Re: ALSA-only purists: Question, new GUI app for the mixer and EQ?

#55 Today 17:51:18

Re: ALSA-only purists: Question, new GUI app for the mixer and EQ?

#56 Today 18:38:02

Re: ALSA-only purists: Question, new GUI app for the mixer and EQ?

Board footer