sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: AE Photos02 <aephotos02@gmail.com>
To: Sox-Users <sox-users@lists.sourceforge.net>
Subject: Re: What´s wrong with my batch script?
Date: Mon, 25 Sep 2017 23:14:58 +0200	[thread overview]
Message-ID: <CAALo0smEt9L3PFtFa_w_q5HofANgS4-nHQtzFvQng=H_g=K_uQ@mail.gmail.com> (raw)
In-Reply-To: <00c1219cb8248be8e0273eec5648333b@wingsandbeaks.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1456 bytes --]

Thanks for your help. I looked into sox now but the issue seems to be in
the for loop in bash. I am getting help on stackexchange for that, lots of
folks to help out.

Thanks again!

On Sun, Sep 24, 2017 at 9:04 PM, Jeremy Nicoll - ml sox users <
jn.ml.sxu.88@wingsandbeaks.org.uk> wrote:

> On 2017-09-24 18:21, AE Photos02 wrote:
>
>> Okay. I see. I'm doing it on a Mac with bash in terminal. Do I need to
>> do a "for each" and an "echo" or something? Or perhaps specify the
>> thing more? I'm new to bash and Sox.
>>
>
> You need to find out what commands the script is issuing. Using echo
> might help.
>
> I have never used bash so I have no idea precisely what is happening.
>
> Maybe just one sox command is being issued, processing all the files at
> once.
>
> Maybe multiple sox commands are being issued but are also processing as
> input the files produced by previous sox commands.  I can't tell.  But
> a good start would be to see what the for loops are actually doing.
>
> --
> 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
>



-- 
Best regards
Kristopher
AE Photos

[-- Attachment #1.2: Type: text/html, Size: 2521 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

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

  reply	other threads:[~2017-09-25 21:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 17:21 What´s wrong with my batch script? AE Photos02
2017-09-24 19:04 ` Jeremy Nicoll - ml sox users
2017-09-25 21:14   ` AE Photos02 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-22 23:26 AE Photos02
2017-09-23 14:10 ` Jeremy Nicoll - ml sox users
2017-09-23 14:27   ` Jan Stary

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='CAALo0smEt9L3PFtFa_w_q5HofANgS4-nHQtzFvQng=H_g=K_uQ@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).