Github messages for voidlinux
 help / color / mirror / Atom feed
From: notramo <notramo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Firefox no sound without PulseAudio
Date: Sun, 21 Aug 2022 22:27:36 +0200	[thread overview]
Message-ID: <20220821202736.SesnPleAgBiya6MIVXlG2POv3vCaJmy3mG__YPAziTo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34596@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

New comment by notramo on void-packages repository

https://github.com/void-linux/void-packages/issues/34596#issuecomment-1221615324

Comment:
I emphasize, I **don't have** `alsa-sndio` installed. It's not needed. Because the OpenBSD devs did it right: the sndiod daemon only opens the card when it plays audio, then it releases when audio playback is stopped. If you control the sound system through ALSA (e.g. volume control via `amixer`), then it's the same as if it were pure ALSA (except you have Firefox working too).
Basically what I did:
1. installed sndio
2. started sndiod
3. it just works like before, plus Firefox works too

I don't say everyone have to follow this configuration. I left these here for users who want minimalist setup. It's worth trying if someone wants this setup, and if it doesn't work, they can move on to other sound systems. It works for me, so it's possible that it will work for others.
I don't say anything from these instructions should be included in the packages or any packages should be changed, so it's pointless to debate.

  parent reply	other threads:[~2022-08-21 20:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 22:26 [ISSUE] " notramo
2021-12-18 14:53 ` mvf
2021-12-20 10:50 ` biopsin
2021-12-20 10:52 ` biopsin
2021-12-20 10:52 ` biopsin
2022-01-23 10:52 ` ErinVoid
2022-01-24 18:38 ` paper42
2022-01-24 18:38 ` [ISSUE] [CLOSED] " paper42
2022-07-15  9:22 ` notramo
2022-07-15  9:23 ` notramo
2022-07-15  9:25 ` notramo
2022-07-15  9:33 ` notramo
2022-07-15  9:34 ` notramo
2022-07-15 16:54 ` mvf
2022-07-15 18:15 ` Duncaen
2022-07-19 20:57 ` notramo
2022-07-19 20:57 ` notramo
2022-07-19 21:17 ` Duncaen
2022-07-19 21:17 ` Duncaen
2022-07-19 21:19 ` Duncaen
2022-07-19 21:21 ` Duncaen
2022-07-19 21:22 ` [ISSUE] [CLOSED] " Duncaen
2022-08-21 18:53 ` notramo
2022-08-21 19:09 ` Duncaen
2022-08-21 19:09 ` Duncaen
2022-08-21 19:10 ` Duncaen
2022-08-21 19:40 ` notramo
2022-08-21 20:07 ` Duncaen
2022-08-21 20:07 ` Duncaen
2022-08-21 20:27 ` notramo [this message]
2022-08-21 20:28 ` notramo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220821202736.SesnPleAgBiya6MIVXlG2POv3vCaJmy3mG__YPAziTo@z \
    --to=notramo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).