I have been using my new DX5 II for 2 weeks now. It is even better than expected. However I am also having some issues.
Issue 1 which is repeatable.
I use the device to replace a dbx equalizer. This means I use it primarily to equalize out a bass resonance in my Quad Esl electrostatics. Works like a charm. But of course I also exploit the extra option to use and equalize my HD 600 headphones in one go.
The strange issue occurs when I connect or disconnect the headphones while playing music over the loudspeakers (LO SE output). The second I pull the headphone plug the speaker sound drops away for a second or so. The other way around I when connect the headphones the speaker sound drops away for a second just when the headphone plug touches the metal of the 6,35 mm to 3.5 mm converter I use.
I suspect there must be something inside the DX5 II that is very sensitive to stray electric charges.
Issue 2 is not easily repeatable.
I have the Topping connected to a Maranz Streamer / Cd player via spdif. The Maranz is used a a digital selector, my record player plays over the Maranz via a minidsp pocketadc, my computer is connected via a 15 m ssnake optical spdif and when I need another input it is also connected via an ADC. The Maranz itself is a streamer / internet radio spotify endpoint etc. (This chain went from mostly analog into a digital system, only the power amp still is analog).
After this long preambule, the issue. When playing through the Topping every now and again suddenly the volume increases or drops by quite a margin for just one or two seconds. Not unlike the dropout in the headphone scenario, but it doesn't only drop out, the volume increases as well on occasions. There is no difference in connecting the Topping through coax or optical. I stress that this never happened with the amp connected to analog outputs of the Maranz itself. It's unique with the signal path through the Topping.
I suspect that both phenomena have a common origin, that might even have a connection with the usb issues
Could anyone shed a light on this behavior of the DX5 II., or even offer a solution.
It is too good a device to write off already.