vrubleg / soundkeeper

Prevents SPDIF/HDMI digital audio playback devices from sleeping.
https://veg.by/projects/soundkeeper/
MIT License
213 stars 9 forks source link

SoundKeeperSineF10A5 not inaudible (aka total audible) on SoudBlaster Z #10

Closed scyto closed 8 months ago

scyto commented 8 months ago

Just FYI

On SoundBlaster Z using Dolby Digital encoder with Logitech Dolby Digital speakers SineF10A5 is audible as low rumble. This was not the case on sound blaster X4 (USB device) doing encoding. As such seems specific to one type of SoundBlaster doing DD or DTS encoding.

SineF10A0 was silent and worked.

Not sure you care, but just an FYI incase anyone else insists it is audible but cant articulate why :-)

vrubleg commented 8 months ago

Did you try standard non-sine mode? If SineF10A0 works, Zero and Fluctuate also should work and are better.

scyto commented 8 months ago

lemme test, i moved to the X4 due to windows 11 issues (or rather SB issues with win11) and SineF10A5 was all that worked after trying many variants like All - can't remember if tried zero and fluctuate - probably the former and not the latter. BRB.

scyto commented 8 months ago

A few things:

Firstly it seems I can't properly test on SB Z anymore as it seems SB has added some sort of SPDIF keepalive in their encoder / software / driver now (this would be a new thing).

Secondly, I switched over to the onboard Realtek SPDIF to do some testing (using whatever win11 beta channel uses as driver) to make sure the change in SB Z behavior wasn't actually a change in the win11 beta behavior with SPDIF. It isn't.

On the Realtek I observed the following:

Note the behavior above with Zero / All / Digital was what I experienced maybe 6mo ago on the SB X4 that caused me to move to the SineF10A5.

FWIW:

I am sure this isn't a widespread issue, would you like me try anything else on this install, or close as i no longer need Soundkeeper on the SB Z, well until they break their code again, lol. either way happy to do some testing on the Realtek if you want me to. My suspicion is something changed in the windows insider rings a few months ago...

thanks for making Soundkeeper it has been super useful to me for a few years solving an issue that made me go nuts :-)