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: Fri, 8 Sep 2017 10:02:33 +0200	[thread overview]
Message-ID: <20170908080233.GA27279@www.stare.cz> (raw)
In-Reply-To: <20170907193153.GA44664@www.stare.cz>

On Sep 07 21:31:53, hans@stare.cz wrote:
> > >> 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
> > 
> > Hi Jan,
> > Yeah, that’s what I would expect :-)
> > 
> > > 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?
> > 
> > Sure, here you go:
> > https://we.tl/lRpO2tMTxu
> 
> Listening to this file with "play output.wav remix 1" etc, I hear:
> 
> 	1 silence
> 	2 voice
> 	3 static
> 	4 silence
> 	5 voice
> 	6 static
> 
> Note that the channels are not "reversed" as you said, it's 2 3 1.
> Can you also try with two different 3ch files to see
> if it behaves consistently?
> 
> > I must say, I’ve only checked in Audacity, but I doubt that would matter...

Just to be sure: using Audacity, you do hear the very same
in the channels as I describe above, right?


------------------------------------------------------------------------------
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-08  8:02 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
2017-09-07 18:43       ` Bouke / VideoToolShed
2017-09-07 19:31         ` Jan Stary
2017-09-08  8:02           ` Jan Stary [this message]
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=20170908080233.GA27279@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).