From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8907CC77B75 for ; Wed, 3 May 2023 20:02:06 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 6C3761404; Wed, 3 May 2023 22:01:13 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 6C3761404 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1683144123; bh=kJXPEBNI8Pvc30qg7qwOQUVOUdbv3Bq+bxX4qD9lC1U=; h=Date:From:To:Subject:References:In-Reply-To:CC:List-Id: List-Archive:List-Help:List-Owner:List-Post:List-Subscribe: List-Unsubscribe:From; b=h1Rl2nAwHW3wqgtwaONyfCT80EaSVqpnYAoIJPESTPWwyB30eusB7N5K/0ICje7PU ETjnDZKt+DygoVcyqkDq32NaSpsFramy1ofIel+rEjgcMbZSy5xhQsemqUcAVtDpWA DccYUHIP9edcpM0/nW/R3TiR6WeKSq+chGDeCp5Y= Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id BF2A5F8049E; Wed, 3 May 2023 22:00:47 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 89010F8049E; Wed, 3 May 2023 22:00:44 +0200 (CEST) Received: from bluemchen.kde.org (bluemchen.kde.org [IPv6:2001:470:142:8::100]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id B818FF80087 for ; Wed, 3 May 2023 22:00:40 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz B818FF80087 Received: from ugly.fritz.box (localhost [127.0.0.1]) by bluemchen.kde.org (Postfix) with ESMTP id 3C63B23FA3; Wed, 3 May 2023 16:00:38 -0400 (EDT) Received: by ugly.fritz.box (masqmail 0.3.4, from userid 1000) id 1puIeT-40E-00; Wed, 03 May 2023 22:00:37 +0200 Date: Wed, 3 May 2023 22:00:37 +0200 From: Oswald Buddenhagen To: Jaroslav Kysela Subject: Re: linux-6.4 alsa sound broken Message-ID: Mail-Followup-To: Jaroslav Kysela , Takashi Iwai , Jeff Chua , lkml , Bagas Sanjaya , ALSA development References: <87wn1pmm4d.wl-tiwai@suse.de> <7b80ef1e-23dd-c523-0663-4bf311c1823a@perex.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <7b80ef1e-23dd-c523-0663-4bf311c1823a@perex.cz> Message-ID-Hash: RKT6RIVBJSNBOJFOTRJ2RE7HTO2G34AQ X-Message-ID-Hash: RKT6RIVBJSNBOJFOTRJ2RE7HTO2G34AQ X-MailFrom: ossi@kde.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-alsa-devel.alsa-project.org-0; header-match-alsa-devel.alsa-project.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Takashi Iwai , Jeff Chua , lkml , Bagas Sanjaya , ALSA development X-Mailman-Version: 3.3.8 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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