9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [patch] nusb/audio /dev entries fix v2
Date: Fri, 29 Dec 2023 22:54:56 +0100	[thread overview]
Message-ID: <C9B951B6DE99359B120C0CA036CDE49B@felloff.net> (raw)
In-Reply-To: <1214862762.3763294.1703871281266@comcenter.netcologne.de>

> I liked Sigrid's solution: There should be a new program that sits between the devices
> like #A, nusb and mixfs and supplies a file system compatible with a #A. Something like this:

isnt that basically what mixfs does?

anyway, my concern about this change is that it will
break an existing usecase where when you plug in
usb soundcard that it becomes the default,
without any other action needed.

i agree that the way we do it right now makes
it impossible to have multiple usb soundcards.

but i really would like to preserve the property
that stuff will just freaking work.

so here you go:

http://felloff.net/usr/cinap_lenrek/mixfs.diff

on startup, it scans /dev/audio* which will pick
up usb soundcards as well. (here, now it just
freaking works!).

the active audio device is available in /dev/volume:

term% cat /dev/volume
dev /dev/audio
mix 100 100

you can then change it like:

echo dev /dev/audioUxxxx > /dev/volume

even while audio is currently playing.

when the device errors on write
(like when you pull the usb soundcard),
it will rescan /dev/audio* and switch to
whatever it finds first.

--
cinap

  reply	other threads:[~2023-12-29 21:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 16:00 Arne Meyer
2023-12-29 17:10 ` cinap_lenrek
2023-12-29 17:34   ` Arne Meyer
2023-12-29 21:54     ` cinap_lenrek [this message]
2023-12-30  1:53       ` hiro
2023-12-30 13:25       ` Arne Meyer
2024-01-06 16:04         ` Arne Meyer
2024-01-06 19:43           ` cinap_lenrek
2024-01-06 20:41             ` Arne Meyer
2024-01-06 19:58           ` cinap_lenrek

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=C9B951B6DE99359B120C0CA036CDE49B@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.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).