Jerome - the revolutionary release of Sooloos is not yet upon us... the release notes of today's release have been put on the public website, there are small bug-fixes but nothing I have noticed.
There may be some non-public features that have been enabled for developers and dealers to test the new Tidal streaming features, I have not seen any settings or GUI for this feature yet. I have already subscribed to Tidal through my Sonos system and quite like it. I think I will cancel my Rhapsody subscription when Tidal is released for Sooloos.
I would not know where to start debugging that. I assume there is no firewall between the MD600 and the MS600 which are connected by a dumb switch?
Just tried Control:Web and that too auto-stops at ~15 minutes.
It wasn't clear whether it was Sooloos-Sooloos or Sooloos-PC. As you say, Sooloos-Sooloos should work through the basic switch so the issue is internal to 2.435.
Sooloos Control:Web would likely be the same issue so if you did want to investigate further, running Wireshark monitoring remote TCP ports in the 9000-9020 range might reveal the connection and the disconnect and whether any traffic was passed over it and what frequency. TBH, I would think that Meridian will know the issue just from your symptoms and let them work out the underlying cause.
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).
Last thing last night I rebooted (switched off and on via the front panel switch) the MD600 and set an album playing via a Control:PC end-point.
This morning it had played to the end.
This morning I started playing an album over 30 minutes ago. There have been no interrupts. Yesterday I would have expected at least one, probably two and maybe three.
So the problem is APPARENTLY resolved, presumably by rebooting the MD600 again.
Thinking in retrospect, yesterday the MD600 restarted after the new software was applied but did not actually switch off and on - doh!
So may I suggest that ThePioneer, Rodders and any others with the same symptom restart your MD600s and report back.
I have reviewed the debug information and can see nothing relevant.
Thanks as always for the patient help and support received from this forum.
TL;DR - if it doesn't work, switch it off and on again!
In the spirit of Spinaltap, I would like to confirm that I am not involved in the corrupt theft of a global sport.
And just to add to what Gianni is saying... when it comes to computer based equipment [such as all our Sooloos Cores and Endpoints], it is almost always more effective to "Hard" Reboot the Devices using the Power Off using Power Switch - Count to 10 - Power back On methodology... rather than using the "Soft" Reboot / Reset options available, such as within Sooloos Configure.
There can be subtle differences between Hard and Soft Reboots and most of the time Soft resets are sufficient... but when all else fails, Hard Reboots do cause the kit to perform a more effective Reset.
And by NO means am I saying that this explains everything seen yesterday... just outlining a "best practice" method for rebooting computer-based kit.
Adding to Ronnie's comment it is worth hard rebooting a few times in case some endpoints are not quite finished updating. I don't know if a systems with several end-points will update them simultaneously or sequentially. If the latter then a few reboots may be required to catch them all.
I downloaded the software with no apparent problem but when I checked the debug screen I noticed my MS200 had disappeared. I rebooted it, back it came but then my 818/ID41 was gone!. I rebooted that and everything is well. Apparently, as others have said, rebooting is a necessary part of this process.
Ken
Main: G68J, 5K2s, 5Ks, HSU subs, Pio 151FD, Dish VP722, Roku, Wadia I70, Anti Mode Dual Core, Oppo 103D Vanity Lite Office: SBT, Berkeley Alpha DAC 2/MQA, Magico S3 Mk II, Boulder 2060, Lumin U1 Mini streamer, Roon.