Bit Depths, Sample Rates

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)

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...? 

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.

I believe your question hit the same time as my post. The transport displays the bit depth for what will be recorded. Has nothing to do with the bit depth of what has been recorded or what the driver is sending to SONAR.

scook
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.

AHA!!!!  Thank you!!

Thanks, I had no idea about file, audio data settings, It did worked.
 
wave profiler for wasapi, wdm, shows only 16 bit, and then converts file, when importing? I do know that mu realtek internal, i creative x fi usb, are 24 bit in\out ..for some reason, wave profiler detetec only 16 bit.
i mean, cards are not pro, but still. is there is something in the code that tell them, you better use 16 bit...just wondering. because, sonar is right to insist on 16 bit....

thank you so much. This was an issue, i did not disable internal card, and sonar lock the 16 bit. i did disable something, but not all....now wdm, wasapi show in profiler 24 bit...thank you o much for you time, and persistance in explaing.it loks easy, but it was not for me

Great explanation Steve.  Thanks for helping us all get a grip on this sample rate/bit depth stuff as it applies in Sonar.

So to sumup:
1. Pref - Audio - Audio Driver Bit Depth is grayed out when using ASIO if interface only allows one setting for ASIO.
2. Transport screen displays Pref - File - Audio Data - Record Bit Depth setting for any new recorded audio.
3. Interface may follow Sonar's setting and may not depending on the interface.
4. Frozen tracks will contain FX if set to do so by rightclicking the Freeze button.
 
What is the Transport screen actually displaying for Bit Rate and how is it changed?

Good stuff, I've been following. Today I've been getting to know my new Scarlett 18i20 2nd gen today and one goal was to ensure sample rates and bit depths were consistent in the chain without hunting all screens.
I have SPLAT on new laptop now, Windows 10. Always desktops until now and firewire FA-101interface. Been using Producer, X1, etc for maybe (7?) years

Thanks!