From: "Ulf A. S. Holbrook via Sox-users" <sox-users@lists.sourceforge.net>
To: sox-users@lists.sourceforge.net
Cc: "Ulf A. S. Holbrook" <post@u-l-v.org>
Subject: Help with --combine merge
Date: Sun, 15 Oct 2023 15:27:56 +0200 [thread overview]
Message-ID: <510211ee-553e-9016-08af-b3e2b9f4bf7c@u-l-v.org> (raw)
Hello!
I'm trying to combine a large amount of files into one single file and
wondered if someone could lend a hand. I have individual folders of 90
1-minute files in .wav and want to merge them into one 90-channel file.
I'm running
for file in /dir
do
sox --combine merge *.WAV >> merged.wav
done
I'm getting some unexpected behaviour, it creates the file "merged.wav"
but does not write anything into it. It is the last file in the list
where all the files are combined, overwriting the contents of that file,
as it becomes a 89 channel file and not 90.
Could anyone help me shed some light on what I'm doing wrong?
/u.
--
/*
Ulf A. S. Holbrook
post@u-l-v.org
http://www.u-l-v.org/
+47 99569230
*/
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next reply other threads:[~2023-10-15 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 13:27 Ulf A. S. Holbrook via Sox-users [this message]
2023-10-15 20:39 ` Help with --combine merge Jeremy Nicoll - ml sox users
2023-10-16 11:10 ` Ulf A. S. Holbrook via Sox-users
2023-10-17 12:14 ` Jan Stary
2023-10-16 10:44 ` Jan Stary
2023-10-16 11:28 ` Ulf A. S. Holbrook via Sox-users
2023-10-17 12:05 ` Jan Stary
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=510211ee-553e-9016-08af-b3e2b9f4bf7c@u-l-v.org \
--to=sox-users@lists.sourceforge.net \
--cc=post@u-l-v.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).