9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix nusb/audio /dev entries
Date: Wed, 20 Dec 2023 17:44:35 +0100	[thread overview]
Message-ID: <7408ADB29853D60644FA44A89191C3B8@wopr.sciops.net> (raw)
In-Reply-To: <1088817250.3535546.1703071432843@comcenter.netcologne.de>

On Wed Dec 20 12:23:12 +0100 2023, meyer.arne83@netcologne.de wrote:

> Hello,
> 
> commit 4bc5793a removed #u from default device binds. Now #u gets bound after #A in nusbrc. Because nusb/audio uses #u to provide its /dev/audio entries this means they are shadowed by the #A device and never picked up. So use 'bind -b' in nusbrc to prefer nusb/audio over #A.
> 
> Greetings,
> Arne

Hi Arne,

Thanks for the patch.  One could argue against the previous behavior
-- what is your use case?

Here are some arguments against it:

- It pulls the rug under you by automatically changing the device you
write audio to, and imho the interaction between #u, #A and mixfs gets
confusing

- If more devices are plugged in, only the last one would be used,
switching output yet again

- If the usb device is disconnected, audio will break for programs
currently writing to /dev/audio and they would have to reopen it

It all amounts to having more control over what happens.  Obviously,
the old behavior might also be desired.  It might make more sense to
have the users themselves control which device to use as needed.  This
could be done automatically by watching /dev/usbevent and switching
accordingly, for instance in a machine-specific termrc or the user
profile, and possibly only for a given device.  One could also always
rearrange the namespace to get #u on top as before.

What do you think, would that work in your case?

Cheers,
qwx

  reply	other threads:[~2023-12-20 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 11:23 Arne Meyer
2023-12-20 16:44 ` qwx [this message]
2023-12-20 17:19   ` Kurt H Maier
2023-12-20 17:47     ` qwx
2023-12-20 17:51       ` Kurt H Maier
2023-12-20 18:11         ` qwx
2023-12-20 18:53   ` Arne Meyer
2023-12-20 23:10     ` qwx
2023-12-21  2:47     ` Sigrid Solveig Haflínudóttir
2023-12-21  7:53       ` hiro
2023-12-21 20:12         ` Arne Meyer
2023-12-21 20:48           ` hiro

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=7408ADB29853D60644FA44A89191C3B8@wopr.sciops.net \
    --to=qwx@sciops.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).