I accidentally created a project and had gotten pretty far along when my Audio engine started really struggling. Discovered I had used a sampling rate of 96000 and my audio interface (Audient iD14) just isn't liking it. Is there a way to shift all the audio to a lower sampling rate? How do I get this project into a useable one? Thanks for any help

SOLVED
Never mind. I did a little research which I should have done before and found this https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=AudioPerformance.05.html

annifarkle
I did a little research which I should have done before...

 
Actually I'm kind of glad you didn't, this question gets asked a lot so it never hurts to remind people there's an easy solution.
 

That link should be updated, since it is repeating the export (Steps 1-3) and can be done in one fell swoop. If you select all audio tracks, in the export dialog and select Source Category as "Tracks" then whatever you type into the "File name" field prefaces the given track name on export.
 
This does still muck up track ordering and force a game of "go fish" as well as setting up the new to look like the old (yada, yada). SONAR does SRC on import as it is, so is hard to see why SONAR cannot simply "release" the audio engine/driver and convert a cwp "in place" - just call up the import algorithm for all audio in the project with the audio interface fully disengaged. For those audio interfaces requiring sample rate changes at the interface, at least the project could be saved, closed, and the interface adjusted before reopening (and look exactly like the original, just at a new sample rate). Basically a "convoluted bounce procedure."

mettelus
SONAR does SRC on import as it is, so is hard to see why SONAR cannot simply "release" the audio engine/driver and convert a cwp "in place" - just call up the import algorithm for all audio in the project with the audio interface fully disengaged. For those audio interfaces requiring sample rate changes at the interface, at least the project could be saved, closed, and the interface adjusted before reopening (and look exactly like the original, just at a new sample rate).

 
Well I've only changed sample rates on one project in the past five years so I'm not an expert, but IIRC if the project uses groove clips or some types of DSP, you won't get the results you expect simply by converting the underlying audio. Rendering, bouncing, and re-importing is the only way I can think of to retain these kinds of in-project changes that point to audio files. 
 

Now I am sort of confused, as you say the "solution" is easy, and only done it once? Then you have "made a conclusion" for CAKEWALK which is definitely not in the interest of end-users... a bounce in place works on groove clips now (you just have to re-groove them), and what DSP functions at one sample rate but not at others?
 
 

mettelus
Now I am sort of confused, as you say the "solution" is easy, and only done it once?

Well don't you think it's easier than what some others have suggested about taking the files in the project audio folder and sample rate converting them in a program like Audacity or Sound Forge...especially since if you do that, which is what I tried first, there can be problems? I found exporting/importing much easier as I explained in this thread, where also, Noel explains why the kind of anomalies I experienced can occur, and why sample rate converting outside of SONAR isn't a good idea. Although I have not had lots of personal experiences with sample rate converting projects, I've read about peoples' experiences with trying to do the same in multiple threads.
 

 Then you have "made a conclusion" for CAKEWALK which is definitely not in the interest of end-users... a bounce in place works on groove clips now (you just have to re-groove them), and what DSP functions at one sample rate but not at others?

 
See the thread referenced above. Also note that I presented no "conclusion," everything I said was heavily qualified..."I'm not an expert"..."IIRC"..."is the only way I can think of" but after finding the thread referenced above that discussed this topic, it looks like I did indeed recall correctly.
 
I realize the necessity for the OP to change sample rates due to computer limitations, but if that's not a factor, it's just so much easier to mix a project at its native sample rate, then sample rate convert the final mix. And for those who are concerned about potential degradation due to sample rate conversion, it's also better to sample rate convert a two track master than each track being mixed (not that I think anyone would notice a difference, but you never know).

OK I did the exporting (each file individually since I didn't know about the ability to do them all at once) and then tried to bypass the "making a new project file". And even though the files I imported were at the sampling rate I wanted, Sonar wouldn't let me change the sample rate for the project. So I created the new file, and imported the audio. This left me with five racks of midi and synths to move to the new file. I then added back effects, eq settings, changed the colors on tracks and placed them in the right order, etc. All told it ate up a good bit of time. I don't understand why this process hasn't been streamline by just auto converting audio to the sample rate when you change it so that you don't have to recreate the whole damn project.

BTW most of the tech talk above was over my head. I did get a few things in it - like don't use other software to convert sample rates.  Thank you for the replies

I'm not saying it's easy but there should be ways to simplify the process like saving track templates then loading them, having two projects open at the same time and dragging effects between them, saving a ProChannel's settings as a "temp" preset then bringing it into the other project, etc. I may investigate this further, I have a couple projects at high sample rates and can see what works and what doesn't. Might make a good "Friday's Tip of the Week" if there's a relatively easy way to do it.
 
However, I don't know how often people need to do this...setting sample rate and bit depths are kind of fundamental things to do when starting a project. As I mentioned, I've needed to do this once in five years, but I don't know if that's typical or whether there's a genuine and frequent need to be able to change sample rates around while in mid-project. Doesn't seem like it would happen that often, but I don't have any idea...where are Cakewalk's analytics when we need them? 

Anderton
I'm not saying it's easy but there should be ways to simplify the process like saving track templates then loading them, having two projects open at the same time and dragging effects between them, saving a ProChannel's settings as a "temp" preset then bringing it into the other project, etc. I may investigate this further, I have a couple projects at high sample rates and can see what works and what doesn't. Might make a good "Friday's Tip of the Week" if there's a relatively easy way to do it.
 
However, I don't know how often people need to do this...setting sample rate and bit depths are kind of fundamental things to do when starting a project. As I mentioned, I've needed to do this once in five years, but I don't know if that's typical or whether there's a genuine and frequent need to be able to change sample rates around while in mid-project. Doesn't seem like it would happen that often, but I don't have any idea...where are Cakewalk's analytics when we need them? 

It may be that it only happens once in awhile but when it does... depending on the size of the project it could be really awful for someone who has a huge project. Mine was relatively small and was still a pain. Also - I did open two windows and drag and drop the midi. I didn't even think to try to do the same with the plugins. It would be great if could just drag all the synth instrument tracks along with the midi from one to the other. Didn't try that either. Thanks for your comments Anderton and I look forward to hearing the results of your experiments with this.