DENAFRIPS DAC ---- Owner Impressions, Feedback, General Discussion, Questions and more....

Perhaps @alvin1118 can comment.

I don't have the unit so I can't actively check. My advice would be to go through the firmware update anyways, that way you will be sure to have the most current version. 

However, I'll repeat what I stated above...Tidal dropouts are more likely being caused by something other than the DAC.

I spent about three hours of listening to my own music last night and had no dropouts.  This was playing from a USB drive I have inserted in the Node 2 running thru the Termy.  Most likely the issue is with Tidal itself as @jaytor suggested.  If I find any other issues I'll report back but I think I'm all good for now.  Thanks @david_ten for your suggestions.  I will try the FW upgrade once I get my laptop up.  

Good Sunday & Happy Easter! 

The frequent dropouts are likely network related. There are possibilities of deficient internet speed, high traffics volume, streaming services etc. 

A good way to verify this is like what others suggested, try to play local music content, or use a known good source like CDT to cross check. This helps to isolate and pinpoint the issue. 

Stay safe and healthy!

Alvin
www.vinshineaudio.com 

Alvin is well aware that there are issues with connections to Tidal and Quboz via the Blusound Node 2i. I bought a Pontus dac with the new DSP board from Alvin and Vinshine Audio in October 2019 and have been messaging him monthly about firmware updates that he's promised from Denafrips. Sorry to air my dirty laundry.

From the beginning I was getting constant skipping and dropouts via a SPDIF cable between the dac and Node. Quoting a message from Alvin in November 2019:

"The issue of skip in split second was due to fifo buffer clock sync with source's clock mismatch by split second, hence the dac skip.This doesnt happen to all source, some sources clock has larger different with denafrips dac, so it will skip when the time sync is out.
I am pushing a firmware fix to address this​"​

​Alvin seems to be like a great guy to deal with but saying its a network issue seems disingenuous. I use a direct ethernet cable connection to the Node and have 200mb/s download speed. It's not Alvin's fault, but him being Denafrips only dealer, there should be a firmware update after 6+ months. I wonder what my system could sound like without all the skipping and dropouts. Skipping happens with every listening session and dropouts have to be resolved by turning the dac off then back on. 

What helped with the skipping and dropouts was me going out the first week and getting an iFi SPDIF iPurifier reclocker. I shouldn't have needed to do that. But the issue still persist on a smaller scale and we still need a firmware update as promised. Hopefully others with the same issue can voice it here.

The following explanation is based on my understanding of how the Denafrips DACs work from reading their documentation and other postings. I could be wrong in my understanding of the issue.

The Denafrips DACs use an internal reclocker when the DAC is connected using SPDIF or AES, which uses a small FIFO to buffer the PCM samples before they are clocked out using the internal clock to the R2R DAC. 

SPDIF (and AES/EBU) assume that the source controls the clock, but as we all know this can introduce jitter resulting in poor performance. By buffering the data and reclocking it, the DAC can all but eliminate the issues with jitter, but this only works well if the source clock is close enough in frequency to the DACs reference clock such that the FIFO can handle the timing differences for the duration of the stream.

If the source clock is operating at a significantly different frequency from DAC clock, or the time between resetting the buffer is too long, the FIFO will either overflow or run out of samples and you'll get a drop out or stutter. 

The iPurifier is doing essentially the same thing, but it probably has a deeper buffer than the Denafrips DAC, and/or is smarter about how it uses its buffer. It also likely has a better clock than the Node 2i (or at least is matched better to the DACs internal clock) so the DAC is not having the same issue buffering the data in its internal reclocker.

There may be ways to improve the problem in the DAC's firmware by being smarter about how the FIFO is used (starting the reclocking sooner or later depending on whether the source clock is faster or slower than the DACs reference clock), or perhaps there is a way to increase the FIFO size (if it's implemented in RAM) if the clocks are significantly off. 

Assuming this is the issue, this problem will not occur when connecting the DAC over USB since the DAC is in control of the timing in this case instead of the source. 

But I also think in @snafujg's case, it's more likely an internet/Tidal issue since he didn't have problems streaming local content and the internet has seen significantly increased streaming demand over the past several weeks due to so many people sheltering at home.