6 Jun
2008
6 Jun
'08
10:42 a.m.
Greetings:
I want to convert an entire directory of 80 bpm loops to 100 bpm loops.
Alas, rubberband does not have a nice simple "change to tempo X"
function (AFAICT) so I need to know:
1. What formula should I use for either the -t or -T options ?
2. How do I use rubberband to process the whole directory ?
Actually I can figure out #2, but I'm open to suggestions for the most
efficient shell script. I'd like to keep the names and append "-100" so
that "80bpm-loop.wav" becomes "80bpm-loop-100.wav".
Let the games begin...
Best,
dp
6 Jun
6 Jun
10:51 a.m.
Dave Phillips a écrit :
2. How do I use rubberband to process the whole directory ?
Usually when the program doesn't support off the shelf wildcarding I use
awk whose output I redirect to a script that I run after I checked it
looks right
here's an example with mv:
ls *.wav | awk '{ print "mv "$1".wav "$1"-100.wav"
}' > doit.sh
chmod +w doit.sh
./doit.sh
hope this helps
Marc
11:02 a.m.
On 06/06/2008, M-.-n <nostromo(a)arkaos.net> wrote:
[...] a script that I run after I checked it looks
right
In that situation (where I'm not totally confident of my syntax) I
generally just start off using "echo" or something equally innocuous
instead of the command I really want to run.
e.g. for the loop I mentioned in my previous mail, start by running
for x in *.wav; do
echo -t 0.8 "$x" "${x%%.wav}-100.wav"
done
then if that looks right, just up-arrow and replace echo with
rubberband or whatever your program is.
Doesn't work if your first argument happens to be one of those also
accepted by echo, of course. Also doesn't tell you whether you've
handled spaces in the filenames correctly or not.
Chris
11:13 a.m.
Am Freitag, den 06.06.2008, 14:02 +0100 schrieb Chris Cannam:
On 06/06/2008, M-.-n <nostromo(a)arkaos.net>
wrote:
Regarding spaces in file names - took me a while to learn but now it
comes in very handy (again Bash):
export IFS=$'\n'; for i in *.wav; do rubberband -T1.25 $i ${i%.wav}-100.wav; done
Cheers,
Jan
[...] a script that I run after I checked it
looks right
In that situation (where I'm not totally confident of my syntax) I
generally just start off using "echo" or something equally innocuous
instead of the command I really want to run.
e.g. for the loop I mentioned in my previous mail, start by running
for x in *.wav; do
echo -t 0.8 "$x" "${x%%.wav}-100.wav"
done
then if that looks right, just up-arrow and replace echo with
rubberband or whatever your program is.
Doesn't work if your first argument happens to be one of those also
accepted by echo, of course. Also doesn't tell you whether you've
handled spaces in the filenames correctly or not. 
11:38 a.m.
On Fri, 06 Jun 2008 15:13:13 +0200
Jan Weil <Jan.Weil(a)web.de> wrote:
Am Freitag, den 06.06.2008, 14:02 +0100 schrieb Chris
Cannam:
i spent far too long looking for that little gem myself. you want to be careful
to restore the IFS if running in your shell and not a script though. it might affect
later commands. </pedantry>
also, i've since found that you can achieve the same result by quoting the output
expansion string, ie:
for i in *.wav; do rubberband -T1.25 $i "${i%.wav}"-100.wav; done
because wildcarded filenames are parsed as a whole on the input side, regardless of
spaces.
cheers,
pete.
On 06/06/2008, M-.-n <nostromo(a)arkaos.net>
wrote:
Regarding spaces in file names - took me a while to learn but now it
comes in very handy (again Bash):
export IFS=$'\n'; for i in *.wav; do rubberband -T1.25 $i ${i%.wav}-100.wav; done
[...] a script that I run after I checked it
looks right
In that situation (where I'm not totally confident of my syntax) I
generally just start off using "echo" or something equally innocuous
instead of the command I really want to run.
e.g. for the loop I mentioned in my previous mail, start by running
for x in *.wav; do
echo -t 0.8 "$x" "${x%%.wav}-100.wav"
done
then if that looks right, just up-arrow and replace echo with
rubberband or whatever your program is.
Doesn't work if your first argument happens to be one of those also
accepted by echo, of course. Also doesn't tell you whether you've
handled spaces in the filenames correctly or not. 
12:35 p.m.
Hallo,
Chris Cannam hat gesagt: // Chris Cannam wrote:
e.g. for the loop I mentioned in my previous mail,
start by running
for x in *.wav; do
echo -t 0.8 "$x" "${x%%.wav}-100.wav"
done
then if that looks right, just up-arrow and replace echo with
rubberband or whatever your program is.
Doesn't work if your first argument happens to be one of those also
accepted by echo, of course.
Just leave the command name in your test command line like:
for x in *.wav; do
echo rubberband -t 0.8 "$x" "${x%%.wav}-100.wav"
done
and then instead of replacing the "echo" with "rubberband", just
remove
the "echo" altogether.
Ciao
--
Frank Barknecht _ ______footils.org__
1:09 p.m.
On 06/06/2008, Frank Barknecht <fbar(a)footils.org> wrote:
Just leave the command name in your test command line
like:
[...]
and then instead of replacing the "echo" with "rubberband", just
remove
the "echo" altogether.
Uh, now you mention it, that _is_ what I normally do... I wondered
why the command looked funny when I wrote it in the email, and why I
hadn't had to worry about echo's arguments before...
Chris
10:52 a.m.
Hi Dave,
Am Freitag, den 06.06.2008, 08:42 -0400 schrieb Dave Phillips:
I want to convert an entire directory of 80 bpm loops
to 100 bpm loops.
Alas, rubberband does not have a nice simple "change to tempo X"
function (AFAICT) so I need to know:
1. What formula should I use for either the -t or -T options ?
2. How do I use rubberband to process the whole directory ?
Actually I can figure out #2, but I'm open to suggestions for the most
efficient shell script. I'd like to keep the names and append "-100" so
that "80bpm-loop.wav" becomes "80bpm-loop-100.wav".
using Bash:
for i in *.wav; do rubberband -T1.25 $i ${i%.wav}-100.wav; done
Cheers,
Jan
11:16 a.m.
Jan Weil wrote:
using Bash:
for i in *.wav; do rubberband -T1.25 $i ${i%.wav}-100.wav; done
Short & sweet, just what I was looking for. It works perfectly. Bash rules.
And now I know how to calculate the tempo conversion. :)
Thanks, Jan, and thanks also to Chris C and Marc for their suggestions.
Btw, I was working with Ardour2 last night, using the new time-stretch
stuff with librubberband. Wow, very sweetly done there too, but not the
most efficient way to convert about 200+ WAV files. Thanks for the great
utility, Chris, we owe you another one. :)
Best,
dp
10:58 a.m.
On 06/06/2008, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
I want to convert an entire directory of 80 bpm loops
to 100 bpm loops.
Alas, rubberband does not have a nice simple "change to tempo X"
function (AFAICT)
No, it doesn't. I might well add one (well, "change from tempo X to
Y" -- I don't intend to make it calculate the current tempo) for the
next release.
1. What formula should I use for either the -t or -T
options ?
-t 0.8 or -T 1.25
2. How do I use rubberband to process the whole
directory ?
Actually I can figure out #2, but I'm open to suggestions for the most
efficient shell script. I'd like to keep the names and append "-100" so
that "80bpm-loop.wav" becomes "80bpm-loop-100.wav".
I would probably use a loop somewhat like
for x in *.wav; do
rubberband -t 0.8 "$x" "${x%%.wav}-100.wav"
done
(caution: untested, assumes bash).
Chris
6016
days inactive
6016
days old
linux-audio-user@lists.linuxaudio.org
9 comments
6 participants
participants (6)
-
Chris Cannam -
Dave Phillips -
Frank Barknecht -
Jan Weil -
M-.-n -
pete shorthose