Session problem: Sample rate on external clock didn't match sonar session

I recorded a session with my converters set to 88.2 (which is the sample rate I want the session to be) and not noticing Sonar's project rate was set to 44.1 (the default project sample rate had been accidentally changed). Project plays back fine in Sonar with external clock set to 88.2. Plays back incorrectly when external clock is set to 44.1 When I export the session to 44.1 16 bit the exported file (displays as 44.1 16 bit in CD architect) plays back incorrectly (very very slow)and of course the song length is twice as long as it should be, incorrect sample rate. I'm a little confused as to what is going on. I'm pretty sure the wav files are in 44.1 What I'd like to happen is for the project to be in 88.2 24 bit and play back and export (to 44.1 16 bit) and burn to a cd properly. Thanks for your time.

The problem is that now the wave files themselves are identified internally as 44.1, which is what SONAR thought they were when it created them. Any playback software that subsequently reads the internal sample rate from the file header and sets the hardware accordingly will therefore play it back at the wrong speed. The only fix is to convince the wave file itself that it's an 88.2 file (which it is) so that it reports itself as such. Then you can re-import it into an 88.2 project and have it work correctly. 

The way you do that is to change the data in the wave file headers. I understand that several audio editors have this capability, including Audacity, Adobe Audition and Sony Sound Forge. However, I only have experience doing this with a generic hex editor, so I can only tell you how to do it that way.

Be sure to back up your project before editing any files. The 3-byte sample rate can be found at byte offset 24 (decimal). If you look in there you'll see 44 AC 00, which is 44100 in hexadecimal (lsb first). Change that to 88 58 01 (88200 in hex), and now the file will report itself to hosts as being an 88.2KHz file. Create a new 88.2 project and import the files and all should be well again.

(Personally, I'm with Cactus on this: working exclusively at 44.1 KHz does avoid a lot of potential complications.)

Thanks Dave, I new I was not being silly by sticking with 44.1. In the past I tried 48 and my problem was having 2 DAW's and 2 interfaces. One defaults to 44/1 and will not let me change to 48. ( M Audio fast track pro) Even though it say's it can do 48 Sonar rejects it and you get the " the rate has been changed to 44.1 as recommended by the driver". I'm one to worry a lot more about my musical performance than sample rates.It was not that long ago I was using a cassette machine. To me 44.1 is a ride on a rocket ship.

swingfingers, because this is such a surprisingly common problem and because many forum users have Sound Forge,  it might be useful to future problem researchers if you could document the steps required in Sound Forge.