From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
Jeff Chua <jeff.chua.linux@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: linux-6.4 alsa sound broken
Date: Wed, 3 May 2023 22:00:37 +0200 [thread overview]
Message-ID: <ZFK9ZSm34Z3hQPF4@ugly> (raw)
In-Reply-To: <7b80ef1e-23dd-c523-0663-4bf311c1823a@perex.cz>
On Wed, May 03, 2023 at 09:32:02PM +0200, Jaroslav Kysela wrote:
>On 03. 05. 23 18:10, Takashi Iwai wrote:
>> The dmix uses the silence_size=boundary as a fill-all operation, and
>> it's a free-wheel mode, so supposedly something was overlooked in your
>> code refactoring.
>>
>> Could you check it and address quickly? I'd like to fix it before
>> 6.4-rc1 release, so if no fix comes up in a couple of days, I'll have
>> to revert the change for 6.4-rc1.
>
>I would revert this patch.
> It seems that this "do silence right after the playback is finished"
> mechanism is not handled in the updated code (and I overlooked that,
> too):
>
no, there is nothing wrong with the code _per se_.
what's happening is that the dmix plugin doesn't update the application
pointer, and somehow gets away with it.
that means that it would have never worked with thresholded silencing
mode, either, but, well, it uses top-up mode.
anyway, this means that we need to revert the code path for top-up mode,
which means reverting most of the patch's "meat".
i think i can do better than your proposal, but not today anymore.
fwiw, the echo results from the plugin apparently summing up the samples
in the buffer without clearing it first, that is, it relies on the
auto-silencing doing the clearing, which the patch broke under the given
circumstances. rather obvious in retrospect.
regards
next prev parent reply other threads:[~2023-05-03 20:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 3:59 linux-6.4 alsa sound broken Jeff Chua
2023-05-01 4:36 ` Bagas Sanjaya
2023-05-01 6:35 ` Takashi Iwai
2023-05-01 13:16 ` Jeff Chua
2023-05-01 14:52 ` Takashi Iwai
2023-05-01 15:03 ` Jeff Chua
2023-05-03 4:40 ` Bagas Sanjaya
2023-05-03 5:42 ` Jeff Chua
2023-05-01 13:08 ` Jeff Chua
2023-05-01 7:17 ` Oswald Buddenhagen
2023-05-01 15:05 ` Jeff Chua
2023-05-03 4:34 ` Bagas Sanjaya
2023-05-03 4:37 ` Bagas Sanjaya
2023-05-03 6:06 ` Takashi Iwai
2023-05-03 12:19 ` Jeff Chua
2023-05-03 13:44 ` Takashi Iwai
2023-05-03 15:06 ` Jeff Chua
2023-05-03 15:47 ` Takashi Iwai
2023-05-03 16:10 ` Takashi Iwai
2023-05-03 19:32 ` Jaroslav Kysela
2023-05-03 20:00 ` Oswald Buddenhagen [this message]
2023-05-03 20:17 ` Jaroslav Kysela
2023-05-04 6:15 ` Takashi Iwai
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=ZFK9ZSm34Z3hQPF4@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=bagasdotme@gmail.com \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.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