After my brief experiments with streaming, I am back to listening to music in 15 minute chunks - just does not work with extended Southern Rock guitar jams
I shall test my MS600s...
In the spirit of Spinaltap, I would like to confirm that I am not involved in the corrupt theft of a global sport.
I am trying to establish whether the problem is specific to Control:PC end-points (with all the variety of possible other factors which could be contributing elements) or whether it also strays into the Meridian-controlled ecosystem.
In the spirit of Spinaltap, I would like to confirm that I am not involved in the corrupt theft of a global sport.
I have now found that the problem is systemic in my network, affecting all Sooloos devices (MS600 and PC-based end-points connected by ethernet or wirelessly).
The MS600 is closely coupled to the MD600 in that they only share an ethernet switch, presumably eliminating any PC software issues or network issues, and indicating a problem somewhere in the core software.
As a result of the latest software release my system no longer functions. A facility to roll back the update and reinstall the previous version would be an acceptable interim solution.
I hope that mine is a rare or isolated instance but that does not appear to be the case.
Last edited by Gianni; 2015-03-0316:16. Reason: Removed some comments in light of resolution. I've retained the rest to maintain continuity of the thread.
In the spirit of Spinaltap, I would like to confirm that I am not involved in the corrupt theft of a global sport.
Over the past weeks the drop out problem has really got bad , in particular BBC channels.
I am hoping that the Sooloos new update will address this problem . If not I guess best to delete the radio channels and reinstall from Rhapsody.
I have not experienced drop out either from stored CDs on C15, or Rhapsody downloads. Our internet speed is not great but at 11-12 mbs it should manage.
I am sure it is not coincidental, but 900 seconds is a very common default TCP timeout i.e. if no communication is received over the TCP connection in 900 seconds, then the TCP connection will be closed which could give the effects that you are seeing.
So the question is, why is no TCP communication occuring on the connection after 2.435 where it probably was before?
Personally, I would look to see if any firewalls are at play in the communication between the two devices and if so, temporary disable it. This assumes that one device is a PC/Mac and that you have control over the firewall. In your scenario, the router will not have any effect.
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).