Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Streaming Sooloos v2.449 Experiences (Post Update)

I've experienced a few "new" glitches over the weekend that I haven't seen posted.

1: This is a bit like the "Track 2" (dropped-track) glitch. Earlier, I posted that I'd seen dropped tracks after pausing playback, and then resuming. But recently -- perhaps because I've been playing more Tidal tracks recently -- it strikes regularly and without regard to pausing or Track 2. At the end of playing a track, all subsequent tracks in the current album will skip, through the end of the queued playlist, pausing for a few seconds on each trying to load, before moving on to the next. When I add the album to the queue again, sometimes it plays through, sometimes not. The following message pops up on the bottom of my C10: "TIDAL media is loading too slowly: A networking or connectivity problem is interfering with TIDAL playback." But my network is rock solid, with (a) internet download speeds exceeding 100 mbps, as verified just after the time of the above track skip and message and (b) no LAN issues, as verified by successful playback of tracks stored on my network-connected Ensembles, also just after the appearance of the above message. Interestingly, rebooting the C10 (my core) sometimes "fixes" the Tidal streaming problem, but not always, and sometimes not for very long.

2: When browsing individual tracks of a Tidal album in my library, it usually takes 3 to 4 touches on the track to successfully add it to my queue. So: press track title on screen, see pop-up emerge from bottom of C10 indicating a successful touch, but the track isn't actually added to the queue. I've resorted to doing queue math: note queue time, touch the track, renote queue time to see if queue length has increased by the length of the track I tried to add. This does *not* happen with local stored (ripped) albums and their tracks, as verified when I'm seeing this glitch.

All in all, when Tidal streaming works, it's great, but all these bugs make the listening experience frustrating, as I'm constantly checking my queue to see if anything has skipped. And then when it does skip, I have to futz around or reboot to get it ironed out.