From: James Trammell <james.trammell@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: which is better / more effective
Date: Sat, 25 Nov 2017 14:28:44 -0500 [thread overview]
Message-ID: <CAB0xix59R-doK3+v1w06WR+urU8jN-AMjXm-VxPxwyjNntU4hw@mail.gmail.com> (raw)
In-Reply-To: <CAKS_MTvb6UWpTMj=tzSpGVoexdTcthP+=q50qGLNwZbzoJDtUQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1793 bytes --]
Hi,
Myself being new to SoX and unfamiliar with the code, my advice would be to
try all three ways, then run a few tests to find any bad behavior. Trust,
but verify.
file A = one call with several switches.
file B = several calls with one switch.
file C = several calls with one switch, piped together.
Null test
Invert the phase of B, combine with A, listen for problems.
Invert the phase of C, combine with A, listen for problems.
Invert the phase of C, combine with B, listen for problems.
Spectrograph
I would also load files A, B and C into spectrograph software to see what
information is present at the very bottom bits of the bit depth.
Try the conversions without dither to see if the spectrographs show
different levels of truncation noise.
-James
On Sat, Nov 25, 2017 at 1:50 PM, Glenn English <ghe2001@gmail.com> wrote:
> I'm getting ready to ask sox to do several things: EQ, compression,
> normalization, speed change, etc. I see on the web, suggestions of
> several different ways to do this: make one call to sox with several
> switches, make several calls to sox with one switch, or pipe those
> several calls together.
>
> Which of these works best? Does it matter? Does sox just figure all
> this out and fork several times if it needs to? (multi-core CPU and
> lots of RAM on Debian Linux, and the file is ~1G FLAC, if any of that
> makes any difference)
>
> --
> Glenn English
>
> ------------------------------------------------------------
> ------------------
> 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
>
[-- Attachment #1.2: Type: text/html, Size: 2702 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 prev parent reply other threads:[~2017-11-25 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 18:50 which is better / more effective Glenn English
2017-11-25 19:28 ` James Trammell [this message]
2017-11-26 12:04 ` Måns Rullgård
2017-11-26 12:36 ` Måns Rullgård
2017-12-01 18:03 ` Glenn English
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=CAB0xix59R-doK3+v1w06WR+urU8jN-AMjXm-VxPxwyjNntU4hw@mail.gmail.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).