9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix nusb/audio /dev entries
Date: Thu, 21 Dec 2023 08:53:50 +0100	[thread overview]
Message-ID: <CAFSF3XNN4r-Hpza-ipyr9zfCVkuNF6kJ9QfHLcKXzo-br__yXA@mail.gmail.com> (raw)
In-Reply-To: <E382EA11-6205-40AD-9361-7987E413831D@ftrv.se>

agreed.
just it should also not crap out on writes when there is no audio
device at all. at first i thought like you, but now i slept about it
for a night and i realize khm was correct. usb audio is too flakey and
we don't want errors in other applications for intermittent usb crap.

On 12/21/23, Sigrid Solveig Haflínudóttir <sigrid@ftrv.se> wrote:
> Write a tool (script?) that watches usbevent and does that. Run it in the
> right place so that namespace is updated properly for your programs.
> Bonus: a tool (I'd suggest separate from mixfs) that does that but also
> provides its own /dev/audio that never craps out on writes unless there is
> no audio devices at all, and can be configured in runtime to point at
> different "real" devices for input and output.
> That might be more useful than nusbrc running nusb/audio and modifying the
> namespace when one least expects it.
>
> On December 20, 2023 7:53:57 PM GMT+01:00, Arne Meyer
> <meyer.arne83@netcologne.de> wrote:
>>Hello qwx,
>>
>>> qwx@sciops.net hat am 20.12.2023 17:44 CET geschrieben:
>>>
>>> Thanks for the patch.  One could argue against the previous behavior
>>> -- what is your use case?
>>
>>I have a thin client with hda audio that is not quite working with the
>> 9front driver. So
>>I use a cheap usb sound card to get audio. In this case I could probably
>> do
>>'unmount #A' in a namespace file and have it work as intended?
>>
>>> 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
>>>
>>
>>Yes, those are all good points.
>>
>>>
>>> What do you think, would that work in your case?
>>
>>If I plug in a usb device I expect it to become the default device. Maybe
>> mixfs
>>can do some clever stuff here?
>>
>>>
>>> Cheers,
>>> qwx
>

  reply	other threads:[~2023-12-21  7:55 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
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 [this message]
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=CAFSF3XNN4r-Hpza-ipyr9zfCVkuNF6kJ9QfHLcKXzo-br__yXA@mail.gmail.com \
    --to=23hiro@gmail.com \
    --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).