Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Kernel Streaming behaves different on Windows 10 (1603) (Read 6457 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Kernel Streaming behaves different on Windows 10 (1603)

Hi! I was wandering if anyone know this... Since my update to Windows 10 1603 (Anniversary update) Kernel Stream behaves different. I'm using a separate DAC over USB and headphones. In the past the default playback device was locked by windows once a sound was played through it. But now it seems that it is freed up while it is not playing something and both the system and foobar can take exclusive control when the other does not use it. To me, that is an improvement. But now it also responds the the volume control on windows, that means the audio stack does alterations to the audio. Not so good... Does anyone know what changed in the MS audio handling in this update? Also, is there a tool that shows locked audio outputs and the bit rate they're running?

Re: Kernel Streaming behaves different on Windows 10 (1603)

Reply #1 –
Why are you using Kernel Streaming on Windows 10 and not Wasapi?  Audio being muted because of Kernel Streaming was more a side effect then a feature.  If you're using anything newer than Windows XP such as Windows Vista, you should be using Wasapi if you want exclusive control of any sound card.

Did you try reinstalling the drivers for your device?  This might fix the issue or might not.  See above.

Re: Kernel Streaming behaves different on Windows 10 (1603)

Reply #2 –
Before this, all mentions of the Anniversary Edition I've seen refer to build 1607, which is the version on my PC as well. Build 1603 would seem to be an earlier Insider update.

Re: Kernel Streaming behaves different on Windows 10 (1603)

Reply #3 –
Quote from: Jailhouse on
Before this, all mentions of the Anniversary Edition I've seen refer to build 1607, which is the version on my PC as well. Build 1603 would seem to be an earlier Insider update.
You are correct. My bad. It is the 1607 version I'm using now. The last official version before that was 1511. 1603 was an actually a version 1511 that included all the updates up until March. Also, 1607 is not a build number. The build number is 14393. 1607 means: the July 2016 version.

Re: Kernel Streaming behaves different on Windows 10 (1603)

Reply #4 –
Quote from: Chibisteven on
Why are you using Kernel Streaming on Windows 10 and not Wasapi?  Audio being muted because of Kernel Streaming was more a side effect then a feature.  If you're using anything newer than Windows XP such as Windows Vista, you should be using Wasapi if you want exclusive control of any sound card.

Did you try reinstalling the drivers for your device?  This might fix the issue or might not.  See above.
Well honestly it is not an issue i'm having. I have no specific USB drivers installed for this DAC. KS and WASAPI both work fine. But since this Windows version I find that KS behaves differently. I want to understand what has changed and how this affects the signal. The fact that I can now change volume indicates my signal is altered by the system. I don't want that.
Why should I use WASAPI instead of KS? I know that the KS plugin is old, but afaik kernel streaming is very much used by Windows 10. They appear to behave the same now.

Re: Kernel Streaming behaves different on Windows 10 (1603)

Reply #5 –
Quote from: jghek on
1607 is not a build number. The build number is 14393. 1607 means: the July 2016 version.
Indeed. I got my terms confused.  :)