TIDAL: a network or connection error is interfering with TIDAL playback

If I could clarify re Patrick’s comment above …

I spent a little time comparing a Tidal MQA album with its FLAC equivalent (Aretha Franklin - I Never Loved a Man). This showed that during the first 5-10 seconds of a track the following track on the album was being cached, in the Roon cache. Further, each MQA track cached almost three times the size of the non-MQA track (26Mb vs. 9.2Mb, 42Mb vs. 15Mb, 30Mb vs. 11Mb etc.). Correspondingly, processor load during the cache operation for MQA tracks was 3-4 times that required for non-MQA. On earlier Antipodes server models (pre-2015) this CPU requirement for ~5 seconds was sufficient to cause dropouts and loss of sync. Once the track had been cached CPU usage dropped to 1/10th of that needed for the cache operation and there was ample processing power for handling playback of MQA tracks,