As a long time use , I'm somewhat unclear on how sonar treats Sample rates and bit depths from a global, vs project by project perspective.
 
Lets say - I started a project a few years back at 48k 24 bit.  Present day I do a lot of work at 48 k 16 bit, and have the record bit depth set to that in preferences.   When I open the old project, the sample rate and bit depth in the control bar show that sonar is running 48/16 - even though the project from a few years ago is at 48/24, This is where I don't understand... It would seem that sonar would chase the original settings of this project?   Now - lets say I add a track, will my new track be at 48/16 - or will it adhere to the projects original settings of 48/24?
 
Who can shed some light on this cavernous chasm of unclarity ?  =-)  (user error)

I don't seem to find any rhyme or reason for what Sonar displays in the Transport Module as it sometimes doesn't coincide with any other setting anywhere. Sonar will set your interface to that setting, tho.
 
For instance, I have a project that's set to 48/24 in Preferences but the Transport Module shows 44.1/24 while the list of audio files in Project - Audio Files... are all 44.1/16.
 
What I also don't get is why the Bit Depth in Sonar Preferences is grayed out at 24 for ASIO when the interface supports 16-64.

https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=AudioPerformance.06.html   which answers alot of my questions... but not my main one....For example - I found this in the help documents... but - as I pointed out - it doesn't seem to add up - as sonar doesn't appear to be chasing the sample and bit rates of pre recorded sessions...? 

You should check whether your audio interfaces allow sample rate and bitdepth changes from software applications

FYI my new MOTU AVBs follow whatever is defined in Sonar i.e. I can open a 44.1 kHz project right after a 96 kHz and Sonar will switch the interfaces to the proper sample rates.

My Roland interfaces (VS700, OctaCapture) did NOT do that. So unless I manually changed settings before opening the project, it would not work!

Regardless of all above I don't see any reason to record at 16 bit if your interface supports 24 bit

thedukewestern
Lets say - I started a project a few years back at 48k 24 bit.  Present day I do a lot of work at 48 k 16 bit, and have the record bit depth set to that in preferences.   When I open the old project, the sample rate and bit depth in the control bar show that sonar is running 48/16...
Who can shed some light on this cavernous chasm of unclarity ?  =-)  (user error)

The transport shows the current "Record Bit Depth" setting from Preferences > File > Audio Data. This is a global setting not a per-project setting. Any new recorded audio will be stored in the project at the value shown in the transport module.  Unlike sample rate, SONAR can work with audio clips at different bit depth settings in the same project.

Thanks guys - that makes sense.  Heres another question regarding rendering.  I recently "froze" a kontakt insance with some processing in the pro channel.  Does sonar render like this with processing in place?  It sounds as if it did.. which I thought it would not

It depends on the state of Track FX in the Freeze Options dialog. Open the dialog by right-clicking freeze icon. I believe Track FX is enabled by default.

scook

thedukewestern
Lets say - I started a project a few years back at 48k 24 bit.  Present day I do a lot of work at 48 k 16 bit, and have the record bit depth set to that in preferences.   When I open the old project, the sample rate and bit depth in the control bar show that sonar is running 48/16...
Who can shed some light on this cavernous chasm of unclarity ?  =-)  (user error)

The transport shows the current "Record Bit Depth" setting from Preferences > File > Audio Data. This is a global setting not a per-project setting. Any new recorded audio will be stored in the project at the value shown in the transport module.  Unlike sample rate, SONAR can work with audio clips at different bit depth settings in the same project.

in preferences shows 24 bit ( gray)  in asio4all  is 24 bit, but in transport bar is 16 bit? How/....we are talking about this for few days, and all answers are incomplete..is it a glitch, is it a reason for this...why it it grey ( you can not change setting_)
 
it drive me nuts, does not see my cards as 24 bit, why? other apps do!

PGM
in preferences shows 24 bit ( gray)  in asio4all  is 24 bit, but in transport bar is 16 bit? How/....we are talking about this for few days, and all answers are incomplete..is it a glitch, is it a reason for this...why it it grey ( you can not change setting_)
 
it drive me nuts, does not see my cards as 24 bit, why? other apps do!

Maybe because you are looking at "Audio Driver Bit Depth" setting in Preferences > Audio > Driver Settings and not the "Record Bit Depth" setting in Preferences > File > Audio Data. The "Record Bit Depth" setting is shown in the transport module. I have never seen that drop down disabled and it has nothing to do with your driver or driver settings.

this info is for US, to see, what is in a preferences....right, if its not the same, what is the reason for it....???