sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jan Stary <hans@stare.cz>
To: sox-users@lists.sourceforge.net
Subject: Re: Merge and pipe channel assignment madness
Date: Thu, 7 Sep 2017 17:51:15 +0200	[thread overview]
Message-ID: <20170907155114.GA36094@www.stare.cz> (raw)
In-Reply-To: <D8D430F8-118F-4CF3-9A1A-4EC397E3977A@videotoolshed.com>

> >> 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.
> > 
> > I cannot reproduce this behaviour.
> > 
> > What version of SoX are you using?
> > Does it also happen with the current version

> https://we.tl/4XNMXikv0J
> Y:\sox-14-4-2\sox -M "| Y:\sox-14-4-2\sox J:\Torsten\tst\T72.WAV -p pad 0" "| Y:\sox-14-4-2\sox J:\Torsten\tst\T72.WAV -p pad 1" -b 24 J:\Torsten\tst\output.wav
> 
> The file has ch1 (a bit) static, ch2 silence, ch3 voice
> On merge, the input tracks are reversed (but other files behave random.)

With my installation of SoX, running

	$ sox -M "|sox T72.WAV -p pad 0" "|sox T72.WAV -p pad 1" output.wav

creates an output file with 6 channels, containing (in this order):

	1 static
	2 silence
	3 voice
	4 static
	5 silence
	6 voice

so I still cannot reproduce your problem.
I also tried with the "-b 24" which should be irrelevant - no change.

Can you please also upload your output file?

	Jan


------------------------------------------------------------------------------
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-07 15:51 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)
2017-09-05 15:17 ` Jan Stary
2017-09-06 13:38   ` Bouke / VideoToolShed
2017-09-07 15:51     ` Jan Stary [this message]
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=20170907155114.GA36094@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).