If I paused playback the data remained latched at the value of the last word of the audio data before playback was paused, resulting in a digital DC offset. You can see it on the foobar Peak Meter. If I happen to pause playback just when a waveform peaked at its maximum possible level, the resultant DC offset will be equivalent to a full-scale signal" and possible destroy my power-amp and speakers.
With the Stop button I don't have this behavior. I first think it's a driver fault but I don't have this behavior with any other players pause button.
If I paused playback the data remained latched at the value of the last word of the audio data before playback was paused, resulting in a digital DC offset. You can see it on the foobar Peak Meter. If I happen to pause playback just when a waveform peaked at its maximum possible level, the resultant DC offset will be equivalent to a full-scale signal" and possible destroy my power-amp and speakers.
With the Stop button I don't have this behavior. I first think it's a driver fault but I don't have this behavior with any other players pause button.
Sorry, I have forgotten. You can only see it if you set "fade" in "Advanced Preferences" to 0 ms.
Windows XP SP3
Foobar 1.1.1
If I paused playback the data remained latched at the value of the last word of the audio data before playback was paused, resulting in a digital DC offset. You can see it on the foobar Peak Meter. If I happen to pause playback just when a waveform peaked at its maximum possible level, the resultant DC offset will be equivalent to a full-scale signal" and possible destroy my power-amp and speakers.
With the Stop button I don't have this behavior. I first think it's a driver fault but I don't have this behavior with any other players pause button.
Sorry, I have forgotten. You can only see it if you set "fade" in "Advanced Preferences" to 0 ms.
Windows XP SP3
Foobar 1.1.1
I'm be wrong with the "Stop Button". The same behavior as the "Pause Button". The only difference to the "Pause Button is, you don't see the issue on the Peak Meter.
Hey, I love your player. Best sounding, best playlist.
Please have a look on the error. It's not cosmetic, it's possible the death for my hardware.
Please!
Possible it's important to let you know I use the ASUS Xonar Essence ST Soundcard.
The relevant review:
http://www.stereophile.com/computeraudio/a...rds/index6.html (http://www.stereophile.com/computeraudio/asus_xonar_essence_ststx_soundcards/index6.html)
In the review he use foobar and my soundcard.
If your sound card or drivers don't silence a DC offset when pausing a DirectSound buffer, something is wrong. If they don't silence a DC offset when stopping, that's stupidly wrong. Neither would be the player's fault, as pausing a buffer should automatically silence it. And even if it didn't, where did you read that maintaining a full magnitude DC offset would harm your equipment?
Because my native language is German I hope there is no misunderstanding.
Since 5 month I discuss with ASUS and ASUS said I should use a compatible Audio Player like Windows Media Player. I try AIMP2 and the Player from Feurio and both haven't had this problem but to be fair Winamp, xmplay and MediaMonkey had.
I'm not a programmer but two Audio Players haven't had this problem. Yes there is something wrong but I don't know what. The truth is foobar don't automatically silence the digital DC offset to be connectet with the Xonar drivers.
Yes, and I don't must read that maintaining a full magnitude DC offset would harm my equipment. I only must have a look on the woofers strong amplitude after I paused or stop playback for about 100 seconds. The reason is the great capacitor in the analog output circuit of my Benchmark HDR DAC.
Neither foobar2000 nor any other player should need to silence the output of any playback method. Pausing the output through the output API's specific pause method should be sufficient. If it is not, there is either something wrong with the sound drivers, or Windows itself. The player should not need to feed silence to the output before pausing it.
Note that the visualizer does not blank itself when the output is paused. It continues to display the same signal as when it was paused, until it is unpaused. The only way to clear it while it is paused is to minimize the main window for long enough for the visualization to shut down.