From: Glenn English <ghe2001@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: multitasking
Date: Wed, 25 Oct 2017 20:25:10 +0000 [thread overview]
Message-ID: <CAKS_MTv+4gfQ3+PaRS-EZmXnxMzwdSgYMuPRex4bBbf+c96Q9A@mail.gmail.com> (raw)
In-Reply-To: <20171025180735.GA49885@www.stare.cz>
On Wed, Oct 25, 2017 at 6:07 PM, Jan Stary <hans@stare.cz> wrote:
> $ sox input output effect1 effect2 effect3 ...
Thanks
> A single SoX process will run on a single CPU.
Thanks again.
> The effects are applied in the order you specify them.
And again.
> But you don't have a billion little flacs, you have one huge flac.
> (BTW, why? Is this the complete Nibelungs?)
No. But it's The Girl Who Kicked the Hornet's Nest and the like. It
comes in a billion little wavs that get converted to a billion little
flacs and them cat'ed into one huge flac (SoX, BTW, has no trouble
with a command line with 250+ params). They all have to be cat'ed for
the effects to be consistent throughout.
> A single instance of SoX will perform the effects in sequence.
> You can try running a pipeline of many SoX instances instead:
> $ sox input - effect1 | sox - - effect2 | ... | sox - output effectN
> Then your operating system could assign each SoX process to a separate CPU.
That's kinda what I thought -- pipes.
> It would be simpler if you isolated your SoX problem to just that.
> The rest of your program has nothing to do with this.
I'm having no problem at all (well, just a bit at first) with SoX.
It's a delightful piece of software.
Back in the analog days, I once spent all fall editing and splicing up
a project that took all summer to record (Homer's Iliad). Easily a
left arm for the likes of SoX/Python back then :-)
> I'm not sure you understand: there is no "self sorting".
There is if I need to specify the effects in a rational order. EQ
before compression before normalize, for example.
> The sequence of effects (or the order of the pipeline)
> is determined by your SoX command.
That assumes a little sorting or the command line by me. A mortal.
> You still haven't told us what exactly
> you want to do with the single input file.
I don't know yet. There are a lot of decisions to be made, probably
different for every file/user. I want to prepare a sort of menu for
the user of various options of some of SoX' effects, then give the
list of desired effects to SoX to do, probably overnight.
--
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
next prev parent reply other threads:[~2017-10-25 20:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 19:00 multitasking Glenn English
2017-10-24 19:44 ` multitasking Jeremy Nicoll - ml sox users
2017-10-25 0:29 ` multitasking Glenn English
2017-10-25 18:39 ` multitasking Jeremy Nicoll - ml sox users
2017-10-25 18:07 ` multitasking Jan Stary
2017-10-25 19:49 ` multitasking Jan Stary
2017-10-25 20:25 ` Glenn English [this message]
2017-10-25 21:11 ` multitasking Jeremy Nicoll - ml sox users
2017-10-26 2:35 ` multitasking Glenn English
2017-10-26 7:39 ` multitasking Jeremy Nicoll - ml sox users
2017-10-26 9:51 ` multitasking Jan Stary
2017-10-26 14:41 ` multitasking Glenn English
2017-10-26 18:57 ` multitasking Jan Stary
2017-10-26 19:17 ` multitasking Glenn English
2017-10-26 20:27 ` multitasking Jeremy Nicoll - ml sox users
2017-10-26 22:05 ` multitasking Glenn English
2017-10-26 9:43 ` multitasking Jan Stary
2017-10-26 14:26 ` multitasking Glenn English
2017-10-26 9:48 ` multitasking Jan Stary
2017-10-26 14:34 ` multitasking 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=CAKS_MTv+4gfQ3+PaRS-EZmXnxMzwdSgYMuPRex4bBbf+c96Q9A@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).