sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
To: sox-users@lists.sourceforge.net
Subject: Re: multitasking
Date: Tue, 24 Oct 2017 20:44:55 +0100	[thread overview]
Message-ID: <82af7d1a9ad07b0bd46d7d9c99ddcf75@wingsandbeaks.org.uk> (raw)
In-Reply-To: <CAKS_MTtNd3hryf5h920F_0DiZ3wEan3ZGTNqtcn+BpsZNSZcDw@mail.gmail.com>

On 2017-10-24 20:00, Glenn English wrote:
> I'm writing a wrapper around SoX, and I've come to the point where a
> number of it's capabilities are required at the same time (eq,
> bandpassing, speech rate change, etc.) and I'm confused about the best
> way to get these all done.

I can't answer the question, but I think whoever does will need to know
more.  Are these multiple capabilities needed on different pieces of
audio, but all being processed at the same time?

  - which to me would suggest one sox command per audio stream,
    and surely they'd be likely to run on different cores

Or do you mean that for one audio source a whole sequence of things
are to be done to it?

  - which seems to me to be one sox command with various effects
    coded one afetr another

Or something else?



> There's talk of a 'chain' in the dox consisting of a number of args
> with ':' between them, but I'm not sure what this means. Does just
> asking for a number of actions enable some kind of threading, using
> several cores in parallel? And if so, does it sort them so
> normalization happens after eq after concatenation, etc.?


There two sorts of chain mentioned; one is the "chain of effects" which
is (I think) analogous to having a whole series of effects boxes wired
up so that sound after it is processed by the first box is cabled to
the next box which does something else, then that output is cabled to
the next one...   Anywhere you see a series of effects each with their
parameters specified, is that sort of chain.

Effects like normalisation, eq etc happen in the order you specify them,
except for the automatic processing implicit in various ways (say) of
combining input files.  (I think.)


The ones with ":" between them confuse me too.  Although I can sort of
see how the ones in the manual might work, I don't think I'm capable of
working out other ways to use ":".



-- 
Jeremy Nicoll - my opinions are my own

------------------------------------------------------------------------------
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-10-24 19:45 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 ` Jeremy Nicoll - ml sox users [this message]
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     ` 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=82af7d1a9ad07b0bd46d7d9c99ddcf75@wingsandbeaks.org.uk \
    --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).