From: Jan Stary <hans@stare.cz>
To: sox-users@lists.sourceforge.net
Subject: Re: multitasking
Date: Thu, 26 Oct 2017 11:48:36 +0200 [thread overview]
Message-ID: <20171026094835.GB55294@www.stare.cz> (raw)
In-Reply-To: <CAKS_MTv+4gfQ3+PaRS-EZmXnxMzwdSgYMuPRex4bBbf+c96Q9A@mail.gmail.com>
On Oct 25 20:25:10, ghe2001@gmail.com wrote:
> > 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.
(Ah, it's you.)
> It comes in a billion little wavs that get converted
> to a billion little flacs
Surely not a billion. I would says tens or at most hundreds,
being a reading of a book ...
> and them cat'ed into one huge flac (SoX, BTW, has no trouble
> with a command line with 250+ params).
OK, hundreds then.
> They all have to be cat'ed for
> the effects to be consistent throughout.
I understand that you need to e.g. normalize the whole thing,
as opposed to normalizing each piece first and then concating.
But that assumes the individual pieces are well mastered,
e.g. the relative volume of each is what it is supposed to be.
> > 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.
That's the opposite of what you said before: you have one huge file,
so what "every file" do you mean? And if you want to process each
of the pieces differently, why do you have the one huge file?
------------------------------------------------------------------------------
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-26 9:48 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 ` multitasking Glenn English
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 ` Jan Stary [this message]
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=20171026094835.GB55294@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).