sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jan Stary <hans@stare.cz>
To: "Ulf A. S. Holbrook via Sox-users" <sox-users@lists.sourceforge.net>
Subject: Re: Help with --combine merge
Date: Tue, 17 Oct 2023 14:05:58 +0200	[thread overview]
Message-ID: <ZS54ptQEMd4DT8ca@www.stare.cz> (raw)
In-Reply-To: <d03d3e06-8090-97e5-b201-368e6050b860@u-l-v.org>

On Oct 16 13:28:13, sox-users@lists.sourceforge.net wrote:
> You are correct.
> But I can't understand why
> sox -M *.WAV out.wav
> would work when
> sox --combine merge *.WAV merged.wav
> won't?

But that's not what you are doing:
sox --combine merge *.WAV >> merged.wav


> On 16/10/2023 12:44, Jan Stary wrote:
> > On Oct 15 15:27:56, sox-users@lists.sourceforge.net wrote:
> > > 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.
> > sox -M *.wav out.wav
> > 
> > > for file in /dir
> > > do
> > > sox --combine merge *.WAV >> merged.wav
> > > done
> > That doesn't make any sense.
> > 
> > > 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.
> > Of course: sox --combine merge *.WAV
> > merges all the given files (arguments) into the last argument.
> > 
> > 
> > 
> > _______________________________________________
> > Sox-users mailing list
> > Sox-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/sox-users
> 
> 
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
> 


_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

      reply	other threads:[~2023-10-17 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15 13:27 Help with --combine merge Ulf A. S. Holbrook via Sox-users
2023-10-15 20:39 ` 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 [this message]

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=ZS54ptQEMd4DT8ca@www.stare.cz \
    --to=sox-users@lists.sourceforge.net \
    /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).