• SONAR
  • Multiple Sample Rates
2016/03/26 13:36:46
brconflict
I've got a strange issues (for me) with multiple sampling rates. I've recorded a session where the sampling rates of the input differed from the Project's sampling rate. Not all tracks recorded this way. There was no Imported audio. For example, the project is 44.1Khz, but the A/D was set to 96khz. Recording all tracks was good, and the playback is good in Sonar. However, Export is a different matter. No matter what sampling rate I choose in the export, it results in a file that plays back very slow.

Sonar doesn't give me any indication as to which tracks are recorded at what sampling rates, or what sampling rates they are at now--or at least, I can't find where to look.
 
Any ideas how to fix this so that the Export plays the same as Sonar plays the mix?
2016/03/26 15:57:50
Klaus
brconflict
 
Sonar doesn't give me any indication as to which tracks are recorded at what sampling rates, or what sampling rates they are at now--or at least, I can't find where to look.


I can't help you with your main issue but for checking the sample rate of clips in your project,
you can use SONARs browser > Project Audio Folder > then select a file and look at the bottom of the browser window to see sample rate, bit depth, etc.
 
HTH a bit,
Klaus
2016/03/26 17:42:52
slartabartfast
Header investigator will allow you to read and change the sample rate header in wave files. The files that are playing too slowly need to have their headers reset to match the rate at which the interface was recording them. All of the track/wave files that you export from Sonar will have the same sample rate in the header, since Sonar did not know that your interface was sending data collected at a different sample rate than the project rate. So you need to export the tracks as waves, find the ones that are screwed up, and change the sample rate header for those files to 96K. They should now play at normal pitch/speed in a wave player like Windows Media Player. Then re-import them into Sonar and they will be re-sampled to the project rate. Note that you do NOT want to re-sample the files with the erroneous headers themselves as R8Brain or a Sonar import will do until you have changed the header. Resampling will keep the speed/pitch the same and change the sample rate. You want to keep the data unchanged but tell programs that load the wave files to use the appropriate playback speed. 
 
http://www.railjonrogut.com/HeaderInvestigator.htm
 
2016/03/26 19:27:34
wst3
that is so much easier than editing in a hex editor - thanks much!
2016/03/27 12:21:38
brconflict
slartabartfast
Header investigator will allow you to read and change the sample rate header in wave files. The files that are playing too slowly need to have their headers reset to match the rate at which the interface was recording them. All of the track/wave files that you export from Sonar will have the same sample rate in the header, since Sonar did not know that your interface was sending data collected at a different sample rate than the project rate. So you need to export the tracks as waves, find the ones that are screwed up, and change the sample rate header for those files to 96K. They should now play at normal pitch/speed in a wave player like Windows Media Player. Then re-import them into Sonar and they will be re-sampled to the project rate. Note that you do NOT want to re-sample the files with the erroneous headers themselves as R8Brain or a Sonar import will do until you have changed the header. Resampling will keep the speed/pitch the same and change the sample rate. You want to keep the data unchanged but tell programs that load the wave files to use the appropriate playback speed. 
 
http://www.railjonrogut.com/HeaderInvestigator.htm
 


Man, that's a great suggestion! Unfortunately, it could not open the .wav files I have. Error Code 11. :/


Nevermind, I had the files open in Sonar - DOH!!
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account