Cakwalk has trouble closing down, and closing audio engine

Make sure Windows and SONAR use the same sample rate.

Jarsve

scook
Make sure Windows and SONAR use the same sample rate.

Wow.
 
UA doesn't see 44,1 and 48 as the same, as every other soundcard I've have had. Every other soundcard i have had play 44,1 under 48 and visa versa.
 
We learn something new everyday. Thanks for that.
 
And now i wonder why. Is that because of the FX engine in the card?

This is a common issue. I have to manually switch the sample rate in my interface to go from Windows to DAW or vice versa. I am sure I didn't use to have that issue a long time ago and was able to have the DAW loaded at 48 and playback audio in win media player at 44. I am not sure if there is a work around.

I have no idea what Windows uses as a default but that is not the issue. I believe some interfaces are stickier than others when it comes to changing sample rate and interfaces can only run at one sample rate at a time. Having all the drivers use the same sample rate eliminates the need for the interface to switch.

scook
I have no idea what Windows uses as a default but that is not the issue. I believe some interfaces are stickier than others when it comes to changing sample rate and interfaces can only run at one sample rate at a time. Having all the drivers use the same sample rate eliminates the need for the interface to switch.

Yeah. It has to be something along this line.
 
I had a Roland card. You could hit it with any samplerate you had (96 and below) and it made sound.
 
My MOTU card was also more forgiving than the UA Apollo card. For this card 4401 and 48 was the "standard" that it could work on. If the card was in 48 mode, it could work on anything 44,1.
 
For a long time tho. I have used the built in card on the motherboard to manage Windows sounds.

Sorry,I misread your previous post. I have used the sample rate drop down in the playback device properties described above on several versions of Windows including Win10. Never had a problem.

msmcleod
Windows 10 has a nasty habit of reverting the sample rate on windows updates, so something to bear in mind.
 
I installed the latest windows update last week, and as expected, my laptop's sample rate had reverted again.
 
M.
 

I put this as helpful. Maybe something we need to take to Microsoft.
As a Insider I might do.

This must then be a audio chip thing. I remember my MOTU card had this troubles too, but 44,1/48 was the same thing for the card/driver/chip. But now for my UA card it even stop work if it is on 48 and the app/Windows feed it 44,1. Same thing the other way around.

Maybe we could make a list over the cards that can handle this and those that dont.

Psychlist1972
I haven't see any Windows Update reset audio sample rates. If you've run into this, please LMK what update # did it so I can check into it.
 
I run my 2408mk3 and 2x 24 i/o at 96khz and use for both DAW use and Windows audio. To do this, I made sure that *every* port, in and out, was set to 96. As I recall, it took a reboot for the MOTU to properly sync this, but it has worked well ever since.
 
It took a bit to make sure I had the same on all, though. Then, I set all my DAWs (I use/test a bunch) to use that same sample rate with ASIO or WASAPI. Same sample rate in every app and OS works best.
 
44.1/48: I've found in the past that my MOTU did not treat those the same. They worked, but played slower when you had them mismatched. The MOTU device would show a different sample rate vs Windows and would get a bit confused.
 
Pete

Oh. Thats strange abut the 44,1/48. I didn't have that problem. There is some time since I had the MOTU card, so maybe there is a new thing in the Windows 10 Audio handling. I replaced the in late June 2017 with the Apollo Twin card.
 
On the using one card for Windows Audio and one for the DAW I newer have had any problem with different sample rate. They are always treated as to separate taskes. As long as i don't load the driver I use to the Windows apps and programs in the DAW.
 
I'm always on the latest Microsoft official release. Not on Insider on the DAW machine.
 
By the way. How well does the 96 work for you? I had some trouble when I used it years ago. The PC was a Intel X99 one with a Core i7 with 6/12, so I don't think it was the PC that was to weak to handle the workload. I dont remember so much at the moment. I am sick at the moment, so my thought are not clear. So sorry if I say something stupid.

Jarsve
Oh. Thats strange abut the 44,1/48. I didn't have that problem. There is some time since I had the MOTU card, so maybe there is a new thing in the Windows 10 Audio handling. I replaced the in late June 2017 with the Apollo Twin card.
 
On the using one card for Windows Audio and one for the DAW I newer have had any problem with different sample rate. They are always treated as to separate taskes. As long as i don't load the driver I use to the Windows apps and programs in the DAW.
 
I'm always on the latest Microsoft official release. Not on Insider on the DAW machine.
 
By the way. How well does the 96 work for you? I had some trouble when I used it years ago. The PC was a Intel X99 one with a Core i7 with 6/12, so I don't think it was the PC that was to weak to handle the workload. I dont remember so much at the moment. I am sick at the moment, so my thought are not clear. So sorry if I say something stupid.

No worries. The 44.1/48 happened in 7/8/8.1/10 so I think it's more about the drivers, or maybe some combination of things. I think the difference for me is that I had ASIO thrown in the mix. For straight up sample rate conversion, our stack will do that for you, assuming it's not operating in Windows 10 low latency mode. IIRC, low latency (small buffers) takes the converter out of the path, but I'd need to double-check that.
 
96khz has been working very well for me for the couple years I've had it going. CPU is a Skylake 6700K quad core at 4ghz, so nothing overly special.
 
I do run insider builds on it (slow ring) so I get full upgrades every month or so. Haven't had any sample rate changes. But I *have* had disabled audio devices, like my monitor, reenabled and made default as a result of the upgrade. I just need to disable them again when that happens. It's only happened on full upgrades, though, not regular updates.
 
Pete
Microsoft

Sorry fro the last post there. God mode is not a modified shortcut, but a modified folder. It's really a long time ago i made that folder, so sorry about that.
 
Enable God Mode in Windows 10
Make sure your system account has administrative privileges
Right-click on the Windows 10 desktop and choose New > Folder
Name the folder:
GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
and hit enter/return to make it stick
 
Here is a link to Windows Central about it:
https://www.windowscentral.com/how-enable-god-mode-windows-10