From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 1/2] pcm: hw: reinterpret the drain_silence setting
Date: Mon, 15 May 2023 11:55:12 +0200 [thread overview]
Message-ID: <ZGIBgAN5v/fwwSDB@ugly> (raw)
In-Reply-To: <dfe607f4-2cee-be2d-561f-1674e156edc0@perex.cz>
On Mon, May 15, 2023 at 11:06:54AM +0200, Jaroslav Kysela wrote:
>On 15. 05. 23 10:41, Oswald Buddenhagen wrote:
>> It makes no sense to have a config option which determines the entire
>> silencing time, because useful values strongly depend on the period size
>> runtime setting.
>
>I would prefer a drain silence mode configuration field for this, if the
>interpretation of the positive value is different. The current value is easy
>to understand and it's really a corner case to not use the default (auto)
>code.
>
but why would you *want* that? what would one use it for? what is the
advantage over my proposal?
i don't think "easier to understand" is true. it may seem easier on the
surface, but one cannot make an informed decision without actually
understanding the implications.
>Even the period time may be forced in the configuration, so users can
>compute the right value themselves.
>
that means that only by combining the two options you'd actually get
something that makes sense.
my proposal otoh works both with and without a forced period time.
regards
prev parent reply other threads:[~2023-05-15 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:41 [PATCH 1/2] pcm: hw: reinterpret the drain_silence setting Oswald Buddenhagen
2023-05-15 8:41 ` [PATCH 2/2] pcm: hw: fix excessive silence fill on drain Oswald Buddenhagen
2023-05-15 9:06 ` [PATCH 1/2] pcm: hw: reinterpret the drain_silence setting Jaroslav Kysela
2023-05-15 9:55 ` 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=ZGIBgAN5v/fwwSDB@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