Hi all ..im running Cake bBL and an RME Fireface UFX..Ive got the Cake audio pref set at 48K for new projects
but it keeps going back to 44K when i initiate a new project..
i have to keep remembering to go to the asio panel of the RME (from within cake)
and set that to 48K..strangely it always remembers to be 24 bit.
If i set the sample rate and save the project it will remember..but if i dont remember to 
do it i can find myself 3hours down the track and everything ive done is 44K...
very frustrating.. any thoughts?  
Thanks 

What is set on the RME? Also is this an empty project? I would try making my own template that has things as you want them. If you are using the built in template they could be set to 44.1. 

thanks..but  edit/preference says 48k...im confused

If your REM is set to 44.1 Sonar will try to match it. Everything needs to have the same value. I am not saying that is the problem only something to check. 

You set the new project default here?

Its working fine on my end, I switched back and forth between 44.1 and 48.
This was in the office with my Babyface, but its the same driver as the Studio UFX.
The Babyface was set to 44.1, I changed the prefs to 48, then opened my "new project" template; 48/24.
That set the Babyface to 48, I changed the prefs to 44.1, then opened "new project" and viola 44.1.
This is with 2018.7 build 13, haven't updated just yet. I'll re-post if that changes anything...
 
T

Sample rate is not stored in the project. A project's sample rate is determined one of two ways:

1. For new projects and projects that do not contain any audio, the sample rate is read from preferences (see image in the message above).
2. For projects that contain audio, the sample rate is read from one of the audio clips in the project.

IOW, until there are audio clips in the project, its sample rate will always conform to the current "Sampling Rate" set in preferences. Saving a project does not set the sample rate for future sessions, saving a project with at least one audio clip in a track does.
 

For exactly the reasons Steve described, my 48k template has a 1 sec audio clip of "silence" to lock it at 48.
 
T

Not sure, but can't other apps like Windows Media Player change the sound card sample rate?  So could jumping between CbB and other media apps cause the issue the OP is having?

Jimbo 88
Not sure, but can't other apps like Windows Media Player change the sound card sample rate?  So could jumping between CbB and other media apps cause the issue the OP is having?

I think so. One reason I have the internal sound chip working for things other than my DAWs. Its a simple matter to route a DAW to your good sound card.

DeeringAmps
You set the new project default here?

Its working fine on my end, I switched back and forth between 44.1 and 48.
This was in the office with my Babyface, but its the same driver as the Studio UFX.
The Babyface was set to 44.1, I changed the prefs to 48, then opened my "new project" template; 48/24.
That set the Babyface to 48, I changed the prefs to 44.1, then opened "new project" and viola 44.1.
This is with 2018.7 build 13, haven't updated just yet. I'll re-post if that changes anything...
 
T

 WOWZER! That's some shockingly crazy high latency report. Is there any reason you need 2048 samples in your buffer? I honestly can't think of any.
I have my Focusrite Scarlett 18i20 gen 2 set at 24 bit 48 k/Hz and buffer size set to 128, CbB can take anything I throw at it, 8 audio tracks at a time with audio FX running in real-time recording, on top of Additive Drums 2, Rapture Pro or what ever, and stay rock solid with no audio artifacts, and the effective recording latency is 2.7 msec, roundtrip 12.6 msec @ 604 samples.
Latency drops down to 0.7 msec set to 24/96, but there's no humanly detectable difference in performance or sound quality, so why waste the hard drive space with the extra HUGE project files?
 Do NOT try setting your buffer size to 128 without an 8 core high performance workstation, but I've never had to set up a mid grade Intel i5 computer for anyone and have to set the buffer size to over 512 on any computer built in the past 7 years or so, and NONE ever ran over 20 msec effective recording latency, even with very inexpensive M-Audio audio interfaces.
 Don't nobody be laugh'in at or hat'in on M-Audio just because they're inexpensive.
 
 
 Yes, Windows Media Player will automatically select the format, bit rate, and sample rate that the audio file was recorded at. Windows Media Player runs entirely in Windows drivers.
It has absolutely nothing to do with the ASIO drivers used for your DAW.
 
Don't forget to hit the "Apply" button before hitting the "OK" button. This setting only applies to Cakewalk opening a new project.
 
 If the "last" project you opened/ran was recorded @ 44.1 than the DAW will stay there until you open a different project recorded at a different sample rate.
 
 If you're not having problems while recording or mixing, don't worry about it.
 Throughout the years I have recorded and collaborated on many different projects set anywhere from 44.1 k/Hz to 96 k/Hz and SONAR/Cakewalk has always automatically clocked out where it's supposed to be and at the appropriate bitrate.
 
 If you are having problems while recording or mixing because of this, I'd recommend updating or reinstalling your RME driver package before messing around with the DAW.
 Just because you may be running the latest drivers available for your audio interface doesn't mean they haven't somehow been corrupted.