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

Also the streaming/Tidal buffering time limit could be relaxed somewhat so the 2nd or third song of the album is not skipped when it is met.

Sometimes add to queue on Tidal tracks does not consistently behave correctly.

These things are probably fit for tuning of set of time-limits.

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.

I can agree, the experiance can be great but so often frustrating. I wanted to play a complete album, 'Long Player' by The Faces.
I selected play all tracks and was delighted it played track 2 but then it skipped a few tracks and nothing I could do would make it just play the album order I wanted. I gave up.

I hope Tidal/Meridian are noteing this feedback as the experiance falls very short of being able to abandon a physical collection as it is now.

In time I hope these bugs can be sorted out to deliver the experiance the premium price commands.

Thoughts, Chris

Apologies if this popped up earlier in this thread, but I didn't see it after a quick perusal.

I've had the update in for a couple of weeks now and am not having any real issues at the front end, but my Control:PC has become completely unusable. I've rebooted everything multiple times, even uninstalled/reinstalled Control:PC, all to no avail.

What happens is the Control:PC software appears to "reboot" itself, essentially, periodically--basically wiping out anything I'm currently in the processing of doing and resetting itself to the home screen. It's consistent enough so that I haven't been able to import an album since the update, since by the time I've edited a few fields and checked all the metadata, it's "refreshed" itself.

No network or PC changes other than the updates; no other problems playing back via my 818.5 or Control:15, etc.

Anyone else seen something similar or have thoughts/suggestions as to cause?

Thanks!

Hi Jerry

I have a similar issue on a Windows 7 PC and I have not installed the two latest Sooloos updates, Control:Mac is fine.

I have not found the cause, strangely another Windows 7 PC works fine, both PC's are running the identical version of Windows?

Russ

Have you cold-booted your C15 (i.e. switched it off and on at the mains)?

Thanks Russ and Gianni. At least I don't seem to have a unique situation. I will try unplugging/replugging the C15 when I get home; I've only turned it off/on via the menu and switch on the back.

I may also try Control:PC on my laptop, which also is Win7, as an experiment, to see if my situation is like yours, Russ.

Will report back.

Following up, last night I unplugged/replugged both the 818.5 and C15. Then I tried importing another CD (I only import already-ripped files) via the Control:PC and it followed a fairly 'normal' current behavior pattern: at first it seems stable -- I actually completed one import -- but by the 2nd import it was back to 'refreshing' itself too frequently to complete another import.

And, while it sometimes just 'refreshes' when I'm not doing anything at all, it seems to happen a lot when it's doing a look-up operation (e.g., while typing in a tag on either side, instead of popping up the look-up list as I type, it hangs, no look-up, then refresh kicks in).

I didn't have time to try a 2nd machine last night, but will do that tonight.

Jerry, have you checked all Sooloos/Meridian programs in your firewall ? Make sure all are set to accept/allow or whatever your security app uses.

Also, assume core is not on a IP/Power plug or anything unusual ?

Just checking to see if anyone has received any type of response or acknowledgement of the issues we are having with Tidal integration in Sooloos?

The skipping of tracks is becoming extremely annoying.

I thoroughly checked firewall and antivirus settings last night -- not that anything had changed recently -- and could find nothing that would appear to hinder Sooloos or the Control:PC from operating normally. And there were no errors or log entries to suggest problems.

But I did install Control:PC on a laptop (also Win7 and on the same network and plugged into the same router as the main PC) and did NOT appear to have the same 'refreshing' problem as on the main PC. To be fair, I only had time to process a couple of CDs, and I continue to have occasional issues --apparently-- with downloading metadata from the Meridian database. But 2 CDs is still better than I've been able to do with my main installation ever since the upgrade to 2.449.

I appreciate the thoughts and suggestions; I'm just reporting back results in case it helps.

Thanks.

Sorry if I've missed this elsewhere, but has anyone tried connecting remotely (i.e. outside of their network)?

When I attempt to connect, my browser very briefly flashes the expected control:web UI, then shows blank white in the browser's content area.

I then have to reboot the MC200, as it appears to hang, even for local use (Control:Mac and iOS Core Control).

Anyone else seeing anything like this?

Thanks