From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=-1.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_LOW, SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id B2A5C1F452 for ; Tue, 17 Oct 2023 12:15:25 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=sourceforge.net header.i=@sourceforge.net header.a=rsa-sha256 header.s=x header.b=mausHqGl; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=sf.net header.i=@sf.net header.a=rsa-sha256 header.s=x header.b=VnMO3khf; dkim-atps=neutral Received: from [127.0.0.1] (helo=sfs-ml-1.v29.lw.sourceforge.com) by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1qsiyb-0001eJ-0X; Tue, 17 Oct 2023 12:15:07 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1qsiyZ-0001eD-Hh for sox-users@lists.sourceforge.net; Tue, 17 Oct 2023 12:15:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ggAe+TYj8gH2fwYNb/cfYYVQt3tBXHCeJM99vNvlAHc=; b=mausHqGljmmNi7VIAyidDoChqV 737dhMThuYU2l6tbZpGtlkL8EGhdOOPJnzaCULhJcux7rI6hPjygmg0jHEb0bZHpxQIvr//KwrgMv keg+3zvQhLFNlacpwILHYwHdmElg1tcuVi0rjYXkh23E0Vk2EUYnp7dqgPrLulMZO15Q=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To: From:Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=ggAe+TYj8gH2fwYNb/cfYYVQt3tBXHCeJM99vNvlAHc=; b=VnMO3khfrViWH0tB+VYzVr4FqH xS/c5L9Pa5v1l+z6uwyy8lK3IT8nmXFPmuTLHmKlEpewISsycp1J7bg/9yvtPPrqRv7JKG1PG4fI9 uoU9FnGtaTj5nrihOK9QJwVGGMqql/xzS3/p2UWgXl22Nsv52fcaazy0PKCj5+M/mbPM=; Received: from uvt.stare.cz ([185.63.96.79] helo=mx.stare.cz) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1qsiyX-0000XV-Hf for sox-users@lists.sourceforge.net; Tue, 17 Oct 2023 12:15:06 +0000 Received: from localhost (stare.cz [local]) by stare.cz (OpenSMTPD) with ESMTPA id 86a66b99 for ; Tue, 17 Oct 2023 14:14:49 +0200 (CEST) Date: Tue, 17 Oct 2023 14:14:49 +0200 From: Jan Stary To: "Ulf A. S. Holbrook via Sox-users" Message-ID: References: <510211ee-553e-9016-08af-b3e2b9f4bf7c@u-l-v.org> <61c9fb0e-a403-015d-6e6f-74f6ae05c28c@u-l-v.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <61c9fb0e-a403-015d-6e6f-74f6ae05c28c@u-l-v.org> X-Headers-End: 1qsiyX-0000XV-Hf Subject: Re: Help with --combine merge X-BeenThere: sox-users@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: sox-users@lists.sourceforge.net Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: sox-users-bounces@lists.sourceforge.net On Oct 16 13:10:07, sox-users@lists.sourceforge.net wrote: > I think you'd be on to something! The for-loop probably calls sox at each > loop and causes some issues. You don't need any loop. > However, if I run > sox --combine merge *.WAV merged.wav > or write to a different directory, it still merged everything into the last > file in the list /and /it creates a new file. I don't belive that's what happens. I believe you run sox --combine merge *.WAV >> merged.wav instead, which would be consistent with such behaviour. > So, I have files labelled 1.wav ... 90.wav Each are 1 minute long. When > running the merge command, the last file in the list becomes the one > everything is merged into, and ends up having 89 channels and not 90. The > new merged.wav ends up being 8 seconds long, yet have 178 channels, ie 89 > x2. So somewhere along the line the loop is doubled, and I cannot understand > how. If my suspition is correct, SoX never touched the merged.wav; it got written with the >> output redirection, so it now contains the textual output of the SoX command. cd /tmp for i in 1 2 3 4 ; do sox -n file$i.wav synth 10 sin $(($i * 100)) ; done sox -M file*wav out.wav soxi out.wav sox -M file*wav >> out.wav soxi out.wav _______________________________________________ Sox-users mailing list Sox-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-users