26 Feb
2005
26 Feb
'05
2:01 p.m.
Hi,
It's complaing because you haven't resampled to the
new rate. I'm trying to think of the easiest way for
you to create a working session with the new sample
rate but I'm not sure if it'll work.
I suggest, making a backup of the current session and
then 'cd sessionname/sounds' and convert the sample
rates from 44100 to 48000 with 'sndfile-resample -to
48000 inputfilename.wav outputfilename.wav'.
The remaining problem is that sndfile-resample can't
output with the same name of the input file so you
have to manually 'mv outputfilename.wav
originalfilename.wav' which is the filename that's in
the Ardour session file somename.ardour.
Maybe the way to test this method is to create a
simple Ardour session at 44100 and with one track.
Then do the above to that session. If it works, great.
At least you'll know what's gotta happen. If you've
gotta alot of sessions to convert then it might be
worth the time to do some scripting.
ron
You've already got libsndfile installed which
includes
sndfile-resample. I'm not sure if you can
convert
the
rates, start jack at the new rate and open the
Ardour
session without having Ardour complain.
well. In fact, ardour *complains* with warnings. How
can I avoid it? The result is that the song is read at a different
speed+pitch because
it was recorded as 44100 and now it is played at
48000. I can't
understand what do you mean.
__________________________________
Do you Yahoo!?
Yahoo! Sports - Sign up for Fantasy Baseball.
http://baseball.fantasysports.yahoo.com/
In theory it
makes sense that you can because Ardour shouldn't
care
about samplerate. It should look at jackd for the
currently running rate and examine the files to see
what rate they are. If they are the same, open
session
and run. I guess you'll need to test that.
ron
>but it's not debian-packaged yet and I'm too lazy
>now...
>maybe ecasound? but I'm afraid it doesn't consider
>so much things as
>sr-convert...
>
>