Hello all, proud owner of a new Topping L30 + D10s stack. Many thanks to everyone on this forum who test these units and helped me make an informed decision.
I've been having a very concerning problem with my D10s that has seemingly just started related to DSD playback. On any DSD sample rate, both native and DoP, after a few seconds of playback I get this sudden, loud onset of pinkish noise. This does not start immediately with a track, a track could play fine for minutes on end or just seconds before this starts. Its worth noting that when the noise starts, there's usually a small pop noise, the actual audio/music starts to fade out/sound distant like its being played across a room, while the pink noise steadily rises. Noise stops when the DAC changes to PCM, or the DSD stream is simply stopped briefly and restarted. It happens with actual DSD files and PCM that is converted/upsampled to DSD.
It's a seriously loud noise that makes me worry it will potentially damage my D10s, L30 or worse, my ears. Any ideas on what could cause this issue? Should I return my D10s for a replacement?
Setup: Windows 10 > Foobar2k using Topping ASIO drivers > D10s > L30
What I have tried:
- Different versions of the ASIO driver
- Different versions of the SACD decoder plugin
- Forcing both native and DoP
- Increasing buffer sizes
- Removing any and all DSP and processing
I've seen quite a few different pathways people set up to get DSD out of Foobar using Topping DACs and related hardware but I can't find a consensus on what plugins/proxies are the most ideal. The SACD plugin included with official Topping drivers seems to be older and missing quite a few features. Here's a picture of my components list, wouldnt be surprised if I'm just doing something completely wrong here.
Tinfoil hat edit: It seems to be particularly triggered by loud volume spikes in DSD, such as a when a violent snare drum enters the mix or a "drop" etc. Otherwise it's pretty hard to reliably reproduce. On occasion, a track that seems to glitch out at said volume spike will play through with no issues. Next 5 attempts it will fail close to the same point though. A really weird issue.
I've been having a very concerning problem with my D10s that has seemingly just started related to DSD playback. On any DSD sample rate, both native and DoP, after a few seconds of playback I get this sudden, loud onset of pinkish noise. This does not start immediately with a track, a track could play fine for minutes on end or just seconds before this starts. Its worth noting that when the noise starts, there's usually a small pop noise, the actual audio/music starts to fade out/sound distant like its being played across a room, while the pink noise steadily rises. Noise stops when the DAC changes to PCM, or the DSD stream is simply stopped briefly and restarted. It happens with actual DSD files and PCM that is converted/upsampled to DSD.
It's a seriously loud noise that makes me worry it will potentially damage my D10s, L30 or worse, my ears. Any ideas on what could cause this issue? Should I return my D10s for a replacement?
Setup: Windows 10 > Foobar2k using Topping ASIO drivers > D10s > L30
What I have tried:
- Different versions of the ASIO driver
- Different versions of the SACD decoder plugin
- Forcing both native and DoP
- Increasing buffer sizes
- Removing any and all DSP and processing
I've seen quite a few different pathways people set up to get DSD out of Foobar using Topping DACs and related hardware but I can't find a consensus on what plugins/proxies are the most ideal. The SACD plugin included with official Topping drivers seems to be older and missing quite a few features. Here's a picture of my components list, wouldnt be surprised if I'm just doing something completely wrong here.
Tinfoil hat edit: It seems to be particularly triggered by loud volume spikes in DSD, such as a when a violent snare drum enters the mix or a "drop" etc. Otherwise it's pretty hard to reliably reproduce. On occasion, a track that seems to glitch out at said volume spike will play through with no issues. Next 5 attempts it will fail close to the same point though. A really weird issue.
Last edited: