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? 

To make the process of changing sample rates of projects even harder, the render sample rate setting in preferences is currently broken for the bounce to track setting. If you change it after after you have created a project and recorded any tracks it has no effect. If you check the rendered file you will find it is still at the original bit rate. My tip of the week would be for the bakers to fix it.
 
I guess the fact no one has noticed it shows how often people change the sample rate.

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? 

Not trying to hijack the OP here but...
Craig, your last statement illustrates a problem with reliance on analytics to guide product development. I thought the analytics were to be primarily targeted toward accumulating fault information (automated bug tracking) but this seems to imply more than that.
 
Assume for the sake of argument it is not easy to SRC a Sonar project. 
I do SRC outside Sonar for this reason so this is not a hypothetical for me.(I tried it once).
Assume many others do the same.
Yet analytics will show that SRC is of little user interest while in reality users may have simply abandoned that feature because it is too difficult to use (or may not function correctly). It would be difficult to determine how many users  actually desire better project SRC from analytics alone.
Here, I am assuming that the upcoming analytics will simply inform Cakewalk of what features are being used in Sonar (and of errors). If the analytics are complex enough to indicate that in one session a project's SR is 44.1K and next session it is 96K (without an import conversion) therefore the SRC must have been external, then I think we have other issues. The first and foremost being Cake should take the analytics development  time and apply it to features/bugs that have appeared on this forum for years.

Of course, analytics can't show how much people like or don't like features that don't exist. I included the smiley because I wasn't being all that serious...I don't think the analytics as currently described are capable of reading intention.
 
But it's important to remember, as has been stated numerous time by Cakewalk staff, that analytics are only one factor Cakewalk plans to use in trying to determine how people use the program. None of the existing methods, including surveys sent to users, forum monitoring, crash reports, the upcoming feedback portal, etc. will be replaced. 
 
I don't know the details, but I suspect one of the greatest value of analytics will be to test reaction to new features. For example, if no one uses Style Dials, I assume Cakewalk wouldn't develop them any further. But if lots of people use them, I expect we'd see more. This is one kind of data where I think analytics would be much more useful than random opinion sampling in the forums.
 

The first and foremost being Cake should take the analytics development  time and apply it to features/bugs that have appeared on this forum for years.

 
From what I understand the analytics module was designed quite a while ago for another product, has a light footprint, and was simple to fold into Sonar. It's clear Cakewalk is making an effort to clean up bugs and optimize the program, but I suspect all bugs are not equal, and anything that will help the Bakers prioritize their to-do list would be beneficial.
 

I had to change the sample rate on a project some years back.  I use Voxengo's R8brain  http://www.voxengo.com/product/r8brain/ which is free. I used the batch processing to do the conversion. I don't recall it being very difficult. 

John
I had to change the sample rate on a project some years back.  I use Voxengo's R8brain  http://www.voxengo.com/product/r8brain/ which is free. I used the batch processing to do the conversion. I don't recall it being very difficult. 

R8Brain is what I use too. It even has a batch mode.