From: Bouke / VideoToolShed <bouke@videotoolshed.com>
To: sox-users@lists.sourceforge.net
Subject: Merge and pipe channel assignment madness
Date: Fri, 1 Sep 2017 23:24:20 +0200 [thread overview]
Message-ID: <55982714-FD94-401E-9391-E41BDA42BCC9@videotoolshed.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 577 bytes --]
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.
Now, remix could fix it, but I need to know what logic behind the channel remapping is used, and I am clueless…
Thanks for any insight!
Bouke
[-- Attachment #1.1.2: Type: text/html, Size: 1959 bytes --]
[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next reply other threads:[~2017-09-01 21:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 21:24 Bouke / VideoToolShed [this message]
2017-09-04 8:21 ` Merge and pipe channel assignment madness Jan Stary
2017-09-04 10:07 ` Bouke (VideoToolShed)
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=55982714-FD94-401E-9391-E41BDA42BCC9@videotoolshed.com \
--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).