sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: "Bouke \(VideoToolShed\)" <bouke@videotoolshed.com>
To: <sox-users@lists.sourceforge.net>
Subject: Re: Merge and pipe channel assignment madness
Date: Mon, 4 Sep 2017 12:07:29 +0200	[thread overview]
Message-ID: <A12AB7F449D0479890921A21D34207E6@HPKANTOOR> (raw)
In-Reply-To: 20170904082148.GA80251@www.stare.cz

---- Original Message ----- 
From: "Jan Stary" <hans@stare.cz>
To: <sox-users@lists.sourceforge.net>
Sent: Monday, September 04, 2017 10:21 AM
Subject: Re: [SoX-users] Merge and pipe channel assignment madness


> On Sep 01 23:24:20, bouke@videotoolshed.com wrote:
>> Hi guys,
>> Trying to merge multiple mono and poly Wave files while piping (to add 
>> custom padding to each input file.)
>> Whatever I do, on input poly files the output channel order is totally 
>> unpredictable.
>>
>> I’m using something like sox -M “| sox 3ch.wav -p pad 1” “|sox 
>> 5ch.wav” -b 24 output.wav
>> I would expect to get the same order of output as in the order of the 
>> input / pipe, but that does not happen.
>
> What happens if you pad the files first
> and then do the merge without any extra piping?

Hi Jan,
That would create a lot of temp files, and take time.
However, I think I have it resolved by putting all inputs as mono into a 
(very long) pipe:
eg
sox - M “| sox 3ch.wav -p pad 1 remix 1" “| sox 3ch.wav -p pad 1 remix 2" “| 
sox 3ch.wav -p pad 1 remix 3" “| sox 5ch.wav -p pad 1 remix 1 ...... etc...

That seems to do the trick!

thx,
Bouke

> Jan
> 

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

  reply	other threads:[~2017-09-04 10:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 21:24 Merge and pipe channel assignment madness Bouke / VideoToolShed
2017-09-04  8:21 ` Jan Stary
2017-09-04 10:07   ` Bouke (VideoToolShed) [this message]
2017-09-05 15:17 ` Jan Stary
2017-09-06 13:38   ` Bouke / VideoToolShed
2017-09-07 15:51     ` Jan Stary
2017-09-07 18:43       ` Bouke / VideoToolShed
2017-09-07 19:31         ` Jan Stary
2017-09-08  8:02           ` Jan Stary
2017-09-08 15:05             ` Bouke / VideoToolShed
2017-09-08 15:53               ` Jan Stary
2017-09-08 22:28                 ` Jeremy Nicoll - ml sox users
2017-09-10 18:26                   ` 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=A12AB7F449D0479890921A21D34207E6@HPKANTOOR \
    --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).