I tried reverting to 2.1.6.245, and the intermittent cut outs and stuttering were reduced but not eliminated.
I tried changing my DNS server to 1.1.1.1 and 1.0.0.1, and updated Tidal to 2.1.18.437 again.
Drop outs and stuttering are back
Reverted to 2.1.6.245. No fix
Now trying accessing Tidal through Roon... major dropouts. Very confused
Well this is very interesting.
I have 2 Tidal desktop app computer installs. Very simple, straightforward PC only setups, no other gear involved other than a Meridian Explorer2 DAC . One is a Win 10 Home 64 fanless mini PC running a Celeron N3450 with 8GB RAM; the other is a Win 8.1 Pro 64 bit with a Corei7 3820 and 16GB RAM. Both PCs have run the Tidal app generally smoothly, especially the Corei7. I got the mini PC so as to have something I could stream Tidal and other music sources on in dead silence. My internet is a laughable 5Mbps DSL connection although it's a surprisingly steady connection for music streaming even at high bit rates.
From the beginning
both systems have suffered a 3 or 4 second buffering pause (using the Tidal desktop app) right at the beginning (at about the 4-6 second point) of each song when streaming an
MQA title with either software only decoding in the Tidal desktop app, or when connected via USB to a Meridian Explorer2 DAC for full MQA rendering (software decoding is turned off in the app) .
This buffering problem seemed to lessen a bit if I let MQA songs play contiguously, ie, no skipping around from song to song before the song finished. To me it seemed that somewhere in Tidal or the network, this sort of easing off on the skipping from song to song allowed the system to buffer more completely.
At no time did I ever experience this regular beginning-of-song buffering pause when streaming at the regular HiFi setting. Clearly something, somewhere in the MQA stream was causing this.
I had mentioned before that a few weeks ago I started realizing that I wasn't getting the beginning-of-song buffering problem on my Win8.1 PC. I later realized that the software version of the Tidal app had gone from 2.1.16.408 to 2.1.17.429. It seemed consistent with the later software--no more buffering at the beginning in any MQA song no matter how loud or quiet it started.
After several weeks of not running my N3450 mini-PC I started it up and tried its Tidal app--it was still at 2.1.16.408... and it still did the beginning-of-song buffering. I thought What, let me upgrade to the very latest--2.1.18.437 (the big download) and see what happens. Well to my pleasant surprise the buffering stopped just like on my Corei7 that had 2.1.17.429. With that in mind I went ahead and upgraded my Corei7 from 2.1.17.429 to the latest 2.1.18.437 and it too, still renders MQA songs smoothly.
It seems Tidal has done
something with the app starting at 2.1.17.429 and continuing with the latest .218 app iteration to fix, at least in my situation, the beginning-of-song buffering issue. Now, I haven't used 2.1.18.437 long-term and I don't know if dropouts or buffering problems will come up at further points in the songs. Time will tell.
This is all food for thought stuff that I know
doesn't directly address the more complex interactions that folks that have more gear (i.e. Roon) involved in their Tidal setups might have. That said, I did read, I think over on AVS forums, at least anecdotally, within the fairly recent time frame, that people with other gear involved like Roon said that they had noticed streaming improvements and it may have something to do with what ever Tidal has done with their software. Obviously, YMMV!
Note: I get the same results using Cloudlflare DNS (1.1.1.1) or my ISP-assigned default DNS. I am currently using 1.1.1.1 set in my router.