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: new user trying to set up a processing chain
Date: Mon, 16 Nov 2020 11:47:56 +0000	[thread overview]
Message-ID: <1cd5c375f96efc01a563bd1cf93da940@wingsandbeaks.org.uk> (raw)
In-Reply-To: <CAM4wmjo=Am+UEi4TeBquAM8BZ8YmscxkVaofTgN0pmXq9JzW2w@mail.gmail.com>

On 2020-11-16 10:04, raymond grote wrote:

> As someone who is generally good at putting pieces together, I can
> work out how to do this in a messy way. Basically I would manually
> mix/process each file. But I unfortunately struggle with efficiency
> sometimes, so it would be quite tedious to do this to multiple files.

> So, I'm primarily trying to work out how much I can do with one
> instance of sox, and if multiple instances are required, where would
> they split?

I think your question's a bit too vague to answer easily.

What OS are you using, and what scripting language (or shell?) are you
comfortable with?

Do you have an idea yet of what directories/folders you're planning to
keep files in?

Do you know how you plan to name them? (Eg, are you going to have base
leafnames and add words to imply what changes you've made, so that eg

   mysong.wav

might end up with modified versions named eg

   mysong (shifted 2khz).wav

   mysong (shifted 2khz) (reverb).wav

or could it be ...mysong\file001.wav        (the original)
            and ...mysong\filennn.wav        (the n'th variant)?


Do all the files you want to process have a similar naming style?


As far as sox goes, I am not personally in favour of trying to use 
chains
of commands, because although efficiency may be a problem, stuff can run
while I look for food, have a shower, sleep etc... and simplicity in the
scripts wins over for me.  (I'm a retired professional programmer, so my
"simple" might be more complex than yours. And my scripts are written in
ooREXX and run under Windows.)

It's also (I think) a great deal easier (if you realise later on that a
sequence of effects didn't do quite what you wanted) that you can go 
back
and redo (say) the third change taking the output from the second one.
You can't do that if you no longer have the intermediate files.

Also at the start when you are experimenting, I think you'd want to test
each stage separately.


-- 
Jeremy Nicoll - my opinions are my own


_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

  reply	other threads:[~2020-11-16 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 10:04 new user trying to set up a processing chain raymond grote
2020-11-16 11:47 ` Jeremy Nicoll - ml sox users [this message]
2020-11-17  3:07   ` raymond grote
2020-11-17 11:30     ` Jeremy Nicoll - ml sox users
2020-11-17 16:01       ` raymond grote

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=1cd5c375f96efc01a563bd1cf93da940@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).