Control: forwarded -1 https://moc.daper.net/node/1600
Control: tag -1 moreinfo

Greetings,

Nick, on 2023-08-13:
>    $ mocp
>    Running the server...
>    Trying JACK...
>    Trying ALSA...
>    mocp: alsa.c:319: alsa_read_mixer_raw: Assertion `RANGE(0, vol, 100)' 
> failed.
> 
>    FATAL_ERROR: Server exited!

Upstream forum post #1600 looks to be the place where discussion
around this issue has been the most involved.  If I trust jcf's
comment, they don't look too keen on working around the problem,
as I understand allowing higher volume settings would make mocp
run into undefined behavior a some places.

I initially thought to tag the bug as "wontfix", as it seems
initial discussions went nowhere.  But, before proceeding, I
attempted to reproduce the bug, and it seems mocp kept running
properly.  From what I saw in ALSA mixer and PA mixer, while the
PA sink overblown the volume, the ALSA mixer remains capped at
100%.  This looks to be sufficient to prevent mocp to run into
the error condition.

My guess is that something in the sound pipeline could have
improved recently the compatibility with direct users of the
ALSA layer.  Does someone reproduce the bug in sid or trixie?

If not, then I guess the issue can be closed.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier <emoll...@debian.org>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-    on air: Porcupine Tree - Even Less

Attachment: signature.asc
Description: PGP signature

Reply via email to