Hi all,
I've had this problem since I got my WiiM Mini about 3 months ago. Each time you click "next", or select a new track, in each case while another track is playing, there is a pause (which is normal) followed my a clicking/popping sound before it plays the selected track. There is no clicking/popping if you simply let the one track play and then move to the next, automatically.
I am using Qobuz (thru the WiiM app), but this also happens with Spotify connect.
Hardware is a Denafrips Ares II DAC with a QED cable optical cable.
The release notes from a few months ago identified this as an issue, but it said it was solved. I don't think it is. (The issue was described as:"Popping noise coming through speaker's when changing tracks when using optical output to DAC optical in").
When I logged a ticket (after the release notes claimed it was "solved") they said they are working on it, suggesting it was indeed, not solved. But, the issue persists.
Any ideas? Does anyone else have the same issue, or the same hardware, with no issue?
Cheers,
Adrian
I've had this problem since I got my WiiM Mini about 3 months ago. Each time you click "next", or select a new track, in each case while another track is playing, there is a pause (which is normal) followed my a clicking/popping sound before it plays the selected track. There is no clicking/popping if you simply let the one track play and then move to the next, automatically.
I am using Qobuz (thru the WiiM app), but this also happens with Spotify connect.
Hardware is a Denafrips Ares II DAC with a QED cable optical cable.
The release notes from a few months ago identified this as an issue, but it said it was solved. I don't think it is. (The issue was described as:"Popping noise coming through speaker's when changing tracks when using optical output to DAC optical in").
When I logged a ticket (after the release notes claimed it was "solved") they said they are working on it, suggesting it was indeed, not solved. But, the issue persists.
Any ideas? Does anyone else have the same issue, or the same hardware, with no issue?
Cheers,
Adrian