I have a lot of projects that are at 48k but I need to drop them down to 44k. Is there a way in Sonar, without having to export as a wav and then re-import into a new project these projects?
 
I have quite a few with saved effects, eq's and other settings, so it would be really annoying to have to basically go back to the start and re-do the project completely.
 
Thanks

I had to do that a couple times, and never found an easy solution. I came pretty close by opening up the clips in Sound Forge from the Utilities menu, changing the sample rate, then saving. This worked really well except for Acidized clips, which I had to convert to regular clips and then it was okay. But some files didn't seem to like the process; one issue I remember in particular was a clip that used DSP to reverse the wave.
 
However, the Sound Forge thing got me 90% of the way there and I think would have gotten me 100% of the way there if some of the clips hadn't used complex processes. I'll be interested to hear if anyone has found a simple way to do this.

Cool, thanks Craig. None are acidized clips, so no probs there. Now, I don't have Sound Forge, but your comment made me think that I DO have Audacity, so I might give that a try.

Re-posting my solution from here:
 
http://forum.cakewalk.com/FindPost/2934357
 
"This is where a 3rd-party sample-conversion application like the free Voxengo R8Brain comes in handy. R8Brain has a batch mode that will create re-sampled copies of all the audio files in place with the original names and add a prefix/suffix to the original files (or delete them if you so choose). Then when you re-open the original project (or a copy of it) with those re-sampled files in the audio folder, SONAR will automatically set the project rate to match the audio it finds, and you're done.
 
Though it does involve using a 3rd-party conversion app, it's by far the fastest and least complicated way of converting a project's sample rate and/or bit depth without altering the project otherwise."
 

Thanks BF - I will definitely try that

One word - Brilliant!  This solution should be a sticky.
 
Thanks again BF.

Anderton
I had to do that a couple times, and never found an easy solution. I came pretty close by opening up the clips in Sound Forge from the Utilities menu, changing the sample rate, then saving. This worked really well except for Acidized clips, which I had to convert to regular clips and then it was okay. But some files didn't seem to like the process; one issue I remember in particular was a clip that used DSP to reverse the wave.
 
However, the Sound Forge thing got me 90% of the way there and I think would have gotten me 100% of the way there if some of the clips hadn't used complex processes. I'll be interested to hear if anyone has found a simple way to do this.

Craig, you said in your post re any other methods - check out BF's solution above - it works and is so easy!
 
Dennis

Cool. Glad to help. I just figured this out a while ago, as I got tired of having to switch my interface to 44.1kHz from my usual 48 to play SONAR demo projects.

Actually now that you mention it...this was a while ago...I do remember that I also tried just changing the sample rates of all the files in the audio folder, again using Sound Forge, and then opening the Sonar project. Sonar could read most of them okay, but again, with reverse and cut up loops it didn't work. I supposed if I bounced everything to "pure" audio it would be fine, but I wanted to keep the project editable, even with the new sample rate.
 
I'll have to try again and get a better handle on what does and doesn't work after converting all the files in the audio folder. There may be some simple thing I'm overlooking. Or maybe just bouncing a few strategic files, or changing the position of reversed files, would do the job.

Yes, I could imagine things might get screwy in a project with non-destructive clip edits/FX/automation in place. I'm not sure how SONAR stores slip-edit and fade locations and such, but if it's by sample position that would be a problem. Unbounced record latency compensation could also throw things off.
 
Caveat emptor.