From: "Grondin Lefebvre Renaud (NHQ-AC)" <Renaud.GrondinLefebvre@CSC-SCC.GC.CA>
To: "'K. H. Hom'" <handwash@protonmail.com>,
"'sox-users@lists.sourceforge.net'"
<sox-users@lists.sourceforge.net>
Subject: Re: Destructive editing?
Date: Thu, 12 Mar 2020 13:52:13 +0000 [thread overview]
Message-ID: <89fdd15210134e4a837eb228cce3ff59@CSC-SCC.GC.CA> (raw)
In-Reply-To: <13949vydQ3L3riLI8FYWQwzzAmNyMMsuVI27Uhw9grc5IYCO665TrR3LyQX4i4wP7BqbNe3yqaHDbH-4Hf252HT4jTUZYzxKT4VpyX5PPtI=@protonmail.com>
If the path contains a space you might want to use double quote like
"X:\Folder Name\File name.wav"
Regards,
-----Original Message-----
From: K. H. Hom via Sox-users <sox-users@lists.sourceforge.net>
Sent: March 12, 2020 9:44 AM
To: sox-users@lists.sourceforge.net
Cc: K. H. Hom <handwash@protonmail.com>
Subject: Re: [SoX-users] Destructive editing?
Thank you VERY much ! That woks (macOS Mojave)
I created a finder action to batch normalise samples:
export PATH=/usr/local/bin:$PATH
for file in "$@"
do
sox $file outfile.wav --norm=-0.1 && mv -f outfile.wav $file done
but there is a problem when the path contains empty space :/ Still need to find a solution for this.
Cheers Hermann
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Sonntag, März 8, 2020 5:09 PM schrieb Peter P. <peterparker@fastmail.com>:
> - K. H. Hom via Sox-users sox-users@lists.sourceforge.net [2020-03-07 14:19]:
>
> > Hi,
> > is it possible to normalize a wav sample and replace the source file, please?
> > Same with Strip silence from end of a file?
>
> I think the best thing is to do it in one line yourself, something
> like
>
> sox infile.wav outfile.wav norm && mv -f outfile.wav infile.wav
>
> on Unix might work.
>
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2020-03-12 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 13:18 Destructive editing? K. H. Hom via Sox-users
2020-03-08 16:09 ` Peter P.
2020-03-12 13:43 ` K. H. Hom via Sox-users
2020-03-12 13:52 ` Grondin Lefebvre Renaud (NHQ-AC) [this message]
2020-03-12 13:55 ` Sylvain Leroux
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=89fdd15210134e4a837eb228cce3ff59@CSC-SCC.GC.CA \
--to=sox-users@lists.sourceforge.net \
--cc=handwash@protonmail.com \
/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).