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: Sun, 10 Sep 2017 20:26:14 +0200	[thread overview]
Message-ID: <20170910182613.GA12744@www.stare.cz> (raw)
In-Reply-To: <df788ad6b7f591834f097431c13cead9@wingsandbeaks.org.uk>

On Sep 08 23:28:35, jn.ml.sxu.88@wingsandbeaks.org.uk wrote:
> On 2017-09-08 16:53, Jan Stary wrote:
> 
> > I'll repeat the question: do you hear the same
> > in the individual channels as I describe above?
> > 
> > > (But I need to generate some testfiles first…)
> > 
> > No, use the file you sent me,
> > so that we listen to the same thing.
> > https://we.tl/lRpO2tMTxu
> 
> 
> If there's something odd going on with the way that sound is
> processed/routed on either of your computers,
> 'listening' might not be the best way to
> discriminate between behaviour on different machines.
> Might it not be better to use soxi or the stat/stats effects to report on
> the content of each channel in the multi-channel file?

No. It's three (resp. six) channels of audio that are
so apparently different (silence, scratches, speech)
that just listening to it is the easiest way to tell them apart.

> That file might need rebuilt so that instead of (as I think it may have)
> different
> frequencies of test tones in each channel, it has significantly different
> levels of
> sound on each channel.

It has completely different material in each channel.
Computing peaks/frequencies/whatnot would be completely pointless.

> The isolation of each channel and stat/stats should
> show each such channel's different peak level,
> and the output from those effects
> can be listed here for everyone to see.

The OP has already posted the actual audio output file
for everyone to see.

	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-10 18:26 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
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 [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=20170910182613.GA12744@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).