Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH v2 0/8] ALSA: emu10k1: add support for high-bitrate modes of E-MU cards
Date: Mon, 17 Jul 2023 17:32:50 +0200	[thread overview]
Message-ID: <ZLVfIkljpthcLgnd@ugly> (raw)
In-Reply-To: <87ilaiwvgg.wl-tiwai@suse.de>

On Mon, Jul 17, 2023 at 02:53:19PM +0200, Takashi Iwai wrote:
>On Mon, 17 Jul 2023 12:19:49 +0200,
>Oswald Buddenhagen wrote:
>> 
>> you want me to spend additional time
>> on a driver barely anyone still cares about
>> to actively degrade the (my!) user experience
>> to avoid hypothetical / likely obsolete crashes
>> that would happen upon a rare user-controlled event
>> in unspecified buggy (mixer? (!)) applications,
>> while a known-good fallback exists (alsamixer).
>
>Simply put, YES.
>
well, your priorities don't align with the needs of actual users (that 
would be me, in this case).

>If you've ever programmed applications that deal with ALSA
>mixer/control stuff by yourself, you'll notice that it's really tough
>to deal with the dynamic deletion/addition.
>
hot-plugging always requires some care to handle. i don't consider this 
a showstopper, esp. in the year 2023, when udev and pulseaudio/pipewire 
go all crazy on us (and yes, that crashed kmix - big deal). i don't 
think it's sane to set the bar at 1995 standards. even less so when the 
class of potentially affected apps holds no user data of note.

>alsamixer can accept it in the limited manner,
>but it's no fallback for everything, of course.
>
i have no clue what point you're trying to make.

regards

      reply	other threads:[~2023-07-17 15:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 14:45 [PATCH v2 0/8] ALSA: emu10k1: add support for high-bitrate modes of E-MU cards Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 1/8] ALSA: emu10k1: introduce alternative E-MU D.A.S. mode Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 2/8] ALSA: emu10k1: improve mixer control naming in " Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 3/8] ALSA: emu10k1: set the "no filtering" bits on PCM voices Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 4/8] ALSA: emu10k1: make playback in E-MU D.A.S. mode 32-bit Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 5/8] ALSA: add snd_ctl_add_locked() Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 6/8] ALSA: emu10k1: add support for 2x/4x word clocks in E-MU D.A.S. mode Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 7/8] ALSA: emu10k1: add high-rate capture " Oswald Buddenhagen
2023-06-30 14:45 ` [PATCH v2 8/8] ALSA: emu10k1: add high-rate playback " Oswald Buddenhagen
2023-07-10 15:06 ` [PATCH v2 0/8] ALSA: emu10k1: add support for high-bitrate modes of E-MU cards Takashi Iwai
2023-07-11 10:15   ` Oswald Buddenhagen
2023-07-11 11:08     ` Takashi Iwai
2023-07-17 10:19       ` Oswald Buddenhagen
2023-07-17 12:53         ` Takashi Iwai
2023-07-17 15:32           ` Oswald Buddenhagen [this message]

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=ZLVfIkljpthcLgnd@ugly \
    --to=oswald.buddenhagen@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    /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