Open Sollaze opened 5 months ago
I have good and bad news.
The good news is that this was the expected outcome which means I know how to fix it.
The bad news is that fixing it will take a while. Since the issue likely isn't with Volume Control itself, I'll either have to write my own Core Audio API implementation or wait for a fix from the developer of the one in use right now.
I don't have much free time atm so implementing it myself is off the table - at least for now. I submitted an issue report to the developer of the CoreAudio nuget package (https://github.com/morphx666/CoreAudio/issues/25) so hopefully they'll be able to come through with a fix in the meantime.
Follow-up bug report to #128 and #86.
I just updated to Win11 today and tried with Destiny 2 so I can confirm it's definitely only an issue on the newer version of Windows. I tried the test program you sent (https://github.com/radj307/volume-control/issues/128#issuecomment-1821660367) as you can see in the picture below. None of the commands did anything whatsoever. Now I might well be doing things wrong and if so do let me know but yeah, no luck with it. (For the record, I have also tried with the process ID. No difference.)![image](https://github.com/radj307/volume-control/assets/146455740/f82e6ca9-b736-49bd-8f61-669a20d57ca2)
If I can help test a fix or run some more explorational tests in the meantime, do let me know! I wanna get to the bottom of this.