From: Glenn English <ghe2001@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: which is better / more effective
Date: Fri, 1 Dec 2017 18:03:08 +0000 [thread overview]
Message-ID: <CAKS_MTsVAkKtuwYM71XGgk4opQrdSMkih0do763nAM2YfUCZsg@mail.gmail.com> (raw)
In-Reply-To: <yw1xy3mtw711.fsf@mansr.com>
On Sun, Nov 26, 2017 at 12:36 PM, Måns Rullgård <mans@mansr.com> wrote:
> Sox has very limited support for multi-processing built-in, and it
> doesn't work very well. For a long effects chain, you'll get better
> throughput by piping multiple processes.
>
> If you have a single command like this:
>
> sox in.flac out.flac effect1 effect2 effect3
>
> it can be split up like this:
>
> sox in.flac -p effect1 | sox -p -p effect2 | sox -p out.flac effect3
>
> The end result should be exactly the same.
>
> It probably doesn't make sense to put light-weight effects in a separate
> command as the extra inter-process copying could easily negate any
> gains.
Thank you. The pipes seemed the simplest way (the way my program is
being written), but sox is pretty new to me...
--
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
prev parent reply other threads:[~2017-12-01 18:03 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
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 [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=CAKS_MTsVAkKtuwYM71XGgk4opQrdSMkih0do763nAM2YfUCZsg@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).