Re: [9front] [PATCH] Fix nusb/audio /dev entries

[Kurt H Maier <khm@sciops.net>]

On Wed, Dec 20, 2023 at 06:47:57PM +0100, qwx@sciops.net wrote:
> I've relied on this behavior in the past, but it's not always what I
> want for instance, I may connect a usb audio interface for recording,
> then a synth that I'd like to interact with with MIDI but not write
> audio to it; I would have to rearrange the namespace to make sure I
> send audio where I want it, I can't just run play(1) or whatever.
> Importing some other machine's #u, recording from a specific device,
> reopening /dev/audio at runtime, interactions with the plumber...
> There are fringe scenarios.  Point being, yes, but not always.  I
> don't know what the right thing to do is.

Ok, you've convinced me.  I withdraw my objection.

> Well that's the thing, it's the intended behavior.  Should we
> implement a new aaa(1) or just reorder the binds?  Dunno.  In
> my case there are advantages on both sides.

If there's a valid, configured audio device connected, writing to
/dev/audio shouldn't fail.  If the system is doing something which
causes that, then I'd call it a bug.  I understand it's not as simple as
this description, but we should at least have the cases where it happens
identified so we can put them in the faq or a wiki or something. 

khm