Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I think it may be happening when a new device is connected. Which happens every time I hook to HDMI or remove HDMI. So if I shut it down, run it somewhere else with no HDMI device then I think it triggers this. Then when I bring to my HDMI location is does it again. It doesn't do it every time, but I am thinking of disabling the audio completely on that hdmi device if I can.
-
@Demolishun That can be it, I have a monitor that when it goes into standby disconnects and it fucks over windows as well (pretty sure linux doesn't care)
-
@BordedDev I have audio pipes in my rig so I can do audio processing with a synth program. It will also randomly change the volume on those. I also suspect even though I told it to not make adjustments to default communication output, that it still does. I installed another program that monitors all outputs so I can see what it tweaked on me in a glance. Unfortunately it doesn't show input channels. Not sure those are getting changed though.
-
@Demolishun That's definitely true, whenever I plug in my ps5 controller it immediately tries to make that speaker + mic even though I've disabled them multiple times in the sound control panel
Every once in a while the volume for my default audio output decides to max out on login. How this can happen is apparently a mystery. Other than its a shitty OS called Windows 11. Windows 10 never did this shit, or if it did it was fixed quickly and never did it again. So there is always a non-zero chance of logging into windows and getting ear raped if you have headphones when playing any audio.
Enter SetVol.exe. Apparently open source and can be run in a batch script. So now I have this kludge of every time I login a task is run to call my bat file to fix this garbage. This is the worst case of quality control I have seen in any supported product. Not a single MS helper in any channel online has had a good fix for this. This is a fundamental design issue in how they handle volume settings. Absolute garbage.
Everyone from ma and pa to audio engineers are screaming about this. How? How does it get this bad?
rant