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 E9893C36001 for ; Fri, 21 Mar 2025 23:24:22 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [45.14.194.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id E925760340; Sat, 22 Mar 2025 00:24:09 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz E925760340 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1742599460; bh=3qq7j+mHHRn0s1NB8PxpQqMJfgQF2cUWMk6oQKFpUlc=; h=From:To:In-Reply-To:References:Subject:Date:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From; b=kqBSJTDIaiDxHXfRPKexp+ZV7mvfomsX5vq2YSdFnDDNN0aRP36iwUzu8THu1ahh7 cG581fWTmAomEDW1wSu9FMIko8G/7pVkmB2UjvzC+epjZNk/FRmHGt+CJ7hCpQ4f8k Sff+syw+JXyMvG6630L822WaK57BX3SKt2qcFz44= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 26032F805C5; Sat, 22 Mar 2025 00:23:46 +0100 (CET) Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id 188FFF805C3; Sat, 22 Mar 2025 00:23:46 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id BE98CF8025A; Sat, 22 Mar 2025 00:23:42 +0100 (CET) Received: from webhooks-bot.alsa-project.org (vmi2259423.contaboserver.net [45.14.194.44]) by alsa1.perex.cz (Postfix) with ESMTP id 1602CF800BD for ; Sat, 22 Mar 2025 00:23:40 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 1602CF800BD MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: GitHub issues - opened To: alsa-devel@alsa-project.org Message-Id: <182ef4f0bd524500-webhooks-bot@alsa-project.org> In-Reply-To: <182ef4f0bc499e00-webhooks-bot@alsa-project.org> References: <182ef4f0bc499e00-webhooks-bot@alsa-project.org> Subject: arecord --max-file-time behavior Date: Sat, 22 Mar 2025 00:23:42 +0100 (CET) Message-ID-Hash: AW5I3X6JBHHCVH3GE7N57BAGH4TI2QQN X-Message-ID-Hash: AW5I3X6JBHHCVH3GE7N57BAGH4TI2QQN X-MailFrom: github@alsa-project.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 X-Mailman-Version: 3.3.9 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: alsa-project/alsa-utils issue #296 was opened from thk686: I do environmental sound recordings where arecord runs for months to years with --max-file-time set to something like 15 minutes. It is very nice to have this feature, yet there is one aspect that is problematic. It is not simple to know which file is currently being written. One can time stamp the file names and ignore the most recent, which is probably the simplest. Nonetheless, I wonder if it could be the case that the current write file could be named something else, such as the file name but preceded by a . or other indicator, and have it renamed to its intended name once it is closed and arecord has moved on to another file. Issue URL : https://github.com/alsa-project/alsa-utils/issues/296 Repository URL: https://github.com/alsa-project/alsa-utils