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

This is a sound card/sound card ship specific issue, I guess.
What sound card do you use?

Jarsve

35mm

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

I don't think the default sample rate for Windows can be changed?

Right click the Sound icon beside the clock on taskbar. Click the "playback devices" and the sound setting window shows up.
Now you can mark the soundcard you use by clicking on it, or right click on it, then click on properties.
In the properties window for you sound card showing up you, click the advanced tab.
And there you have Windows system sound settings.
 
Works for Windows 10.
 
Tips. In the previous window that still is up you can rename your sound cards. Change their icon. Disable unwanted monitor sound drivers.
 

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.
 

35mm
 
I've tried that before but no way of changing the default sample rate for me.

It only changes the Windows playback sample rate.
The one that Windows sounds use, the one that Edge/Firefox/Chrome use for Youtube and so on. It also change the sample rate for Spotify (if you put 96 in Windows 10 Spotify will play the songs wrong).
Cakewalk and Sonar, on the other hand, Does not use Windows audio, but use the core of the audio card drivers, (that’s why you can get so low latency) and it overrun Windows audio because of this. Safest thing is to make the DAW turn of the driver for anything else than the DAW. But in Sonar/Cakewalk you can turn it on. This is very helpful if you are using an extern audio editor etc.

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.

Jarsve
 
What sound card do you use?

I have modified the Windows sample rate using Realtek, M-Audio, Presonus and RME interfaces. Currently using an RME Babyface Pro.

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.

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

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

35mm
 
I've tried that before but no way of changing the default sample rate for me.

It only changes the Windows playback sample rate.
The one that Windows sounds use, the one that Edge/Firefox/Chrome use for Youtube and so on. It also change the sample rate for Spotify (if you put 96 in Windows 10 Spotify will play the songs wrong).
Cakewalk and Sonar, on the other hand, Does not use Windows audio, but use the core of the audio card drivers, (that’s why you can get so low latency) and it overrun Windows audio because of this. Safest thing is to make the DAW turn of the driver for anything else than the DAW. But in Sonar/Cakewalk you can turn it on. This is very helpful if you are using an extern audio editor etc.

At the moment I am using an old M-audio ProjectMix. I have to manually change the sample rate in its control panel and that changes the sample rate in Windows. When it's at 44.1k I get Windows sound. If I open Windows Playback Devices and go to properties > advanced it only lets me select 44.1k but gives me a choice of bit rates. If I set the PM's control panel to 48k (what I use when running a DAW) the Windows advanced properties only lets me select 48k with a choice of bit rates. But Windows will not playback audio at 48k - no windows sounds and no sounds from a browser. So I have to manually switch sample rates in the PM controller depending what I am doing. I've got used to doing that, but I am sure in the past I didn't have to. It's the same too for my Focusrite Pro 40. I think something must have been changed in a windows update at some point.

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