Bounced song slows down when I turn off my Alesis Q2. 44.1/48 issue...Help

[east3rdst]

I know how this happened, I just don't know how to fix it. In order to gain an extra "in" to my 001, I sent a tom through my alesis Q2 optical output into the digi. The session was 24bit 44.1 but it was using the optical port to clock to. I think the alesis default is 48. If im playing back the songs, in say Toast, the song slows down if I shut off the connected Q2 (even with Pro Tools off). And of course the songs play too slow as a CD. I've tried converting the songs using sound app...no help.

[east3rdst]

No one??

[Rail Jon Rogut]

You answered your own question..you had a 44.1kHz session.. then you clocked the session off the SPDIF clock which is 48kHz.. which means the session will run at a speed of 48kHz.. but all sound files created will have a header of 44.1kHz (which is the session sample rate).

There are various ways of fixing the problem.. me I'd just use a utility like SoundHack (or under XP my own utility available at my site for free) which takes the bounced file and changes the sample rate in the header to match the actual data's sample rate (in this case 48kHz). Of course.. you'll end up with a 48kHz file which you can't burn to disk without SRC (yuck).

Rail

[east3rdst]

Thanks. Can I fix it in the original session file? I might just mix it down through the analog outputs.

[east3rdst]

bump

[cecilsound]

I would have to agree with Rail. Although, another work around might be to create a new session with the proper sample/bit rate and try importing your original sessions audio files to the new session. PT should say that they will need to be converted before importing, but it will still do it. You might even be able to do a track transfer from the original session. Any way, once this is done you can either remix or bounce or run for president, whatever you prefer.

[Rail Jon Rogut]

Check out this thread for other options.

Rail