Sample Rate Mismatch! (clock 44.1, PT 48)

[RhodesB3]

Hi,

How does one fix this issue:

I recorded a session where pro tools was set to 48k and the clock was set to 44.1. When I bounce, the files play at the wrong speed. My assessment is that the files are actually at 44.1, but pro tools thinks they are 48. How do you rename the file headers so that they are seen as 44.1?

What do you do??? (other than always check the big ben... I think it used to give me an error message?)

[MoritzRock]

Originally Posted by RhodesB3

Hi,

How does one fix this issue:

I recorded a session where pro tools was set to 48k and the clock was set to 44.1. When I bounce, the files play at the wrong speed. My assessment is that the files are actually at 44.1, but pro tools thinks they are 48. How do you rename the file headers so that they are seen as 44.1?

What do you do??? (other than always check the big ben... I think it used to give me an error message?)

Try importing it into another session set at 44.1, not sure it will work you might get a slower playback if so try to uncheck the convert SR box when you import it. not sure you can BTW. never been in the situation.

I am not sure what you mean by when i bounce, are you bouncing at a different SR? is Playback ok?

[RhodesB3]

Thanks Mo,

I've tried that, and it doesn't work. If I create a session at 44.1, and import the files, pt thinks that its at 48, so it wants to do a src. If there is a way to rename the header in the file, that would be the thing to do. but how??

[rafukyo]

HI

I think you will have to pitch shift and time exp/comp to fix it.


Rafi

[Delta Music Belgium]

Create a new session at the correct sample rate (44.1k), use 'Import Session Data' and import the misclocked session tracks. Choose not to do an SRC on the audio.

[hummerZ]

Soundhack can alter the SR flag in the header, if you're on a mac.

http://music.ucsd.edu/~tre/soft//SH896.zip

[ABrooks]

I did this once and I had to adjust the speed. 8% is the difference between 44.1 and 48k. So that's what I did and it worked, but I only had to do it on a VT and not instrumentation thank goodness.

But I know there's a way to make DP or Logic think that a session is a different sample rate from ProTools to correct the issue. I didn't do that personally but a friend of mine had to on some stuff someone else sent him.

[Vedat]

If you have another rig, play out from one and record on the other.
This is the safest way.

[Rail Jon Rogut]

Originally Posted by Delta Music Belgium

Create a new session at the correct sample rate (44.1k), use 'Import Session Data' and import the misclocked session tracks. Choose not to do an SRC on the audio.

This is the correct method.

Rail

[Dizzi45Z]

Originally Posted by Delta Music Belgium

Create a new session at the correct sample rate (44.1k), use 'Import Session Data' and import the misclocked session tracks. Choose not to do an SRC on the audio.

+1. I ran into the exact same problem and a year ago and fixed it with this method as well. It really is the fastest and easiest way to fix the problem.