Mosaic unresponsive at times

[PAR (Pete)]

@struts001

I don’t have Tidal however, could that just maybe be the problem?

No Tidal here. From memory when it occurs it affects whichever service is being used, Radio, Qobuz or UPnP.

[Phil (Phil Harris)]

@struts001

I can try to help you here Phil.

Fantastic … the more the merrier!

If we can get anything to help us recreate an issue or even point us in the right direction to find an issue then I can get it logged and placed with the dev team … even if it’s something like an external event sate that we can perhaps handle better.

It’s always interesting that the perception is that “we” write everything (for instance UPnP discovery or UPnP browsing) from scratch and modify that code at will and just bake it into every release however it stands at the time so on every release you’ll get a few reports of that kind of functionality having broken on the new release but the reality is that all of that functionality is provided by the iOS or Android libraries that everyone uses and no-one has any direct access to to modify or otherwise play around with and mess up … the submission requirements for the Apple Appstore and the Google Play Store are massively tight and very much automated to make sure that you are using nothing but the approved calls and functions and that you are using them properly…

P

[Phil (Phil Harris)]

@PAR

@PAR

Once I would be able to easily swap the S100 out. However my disabilities now make it a daunting task. I will try if I can

Pete, you are one of the total rocks of this forum and I am aware you have had issues (although not of the details and it’s none of our business) so, much as I really do appreciate you trying to help nail down an issue, please don’t feel in any way obliged or expected to do anything you can’t manage to do comfortably … we’d much rather have you as an active and much loved forum member than receive a screenshot that causes you personal discomfort and aggravation to obtain.

Px

[Lima]

@PAR This screen shot is what happens, just freeze and lose connection.

[glevethan (Gregg)]

@Anupc

That said though, most folks seem to have at least a pair of cascaded Switches between their Mosaic Control iDevice and the dCS component. Like Gregg listed above for example; Mosaic → EEPro → Cisco → dCS. Which means, every time Mosaic Control sends out a dCS hunt request broadcast, thats 3 hops to get to the dCS, adding to the overall response time delay.

That shouldn’t be a problem when every thing is hunky dory, but in reality, including depending on what else is going-on on the network, response times could impact user-experience.

@Anupc @Phil

Hi Guys

Thanks for the concern and followup - much appreciated.

As Phil mentioned further down the thread I too was guilty of having multiple switches in the system (not “audiophile” grade but rather commercial ie Cisco 2960’s). While the Ebay seller advertised they were returned to default settings, and were no longer managed (?), I can understand where they could eventually become a source of problems.

As Anup posted above I have tried to simplify my system as much as possible. I think this has been accomplished as I do not know many who can build out a system and not use at least one router (EEPro to serve IP addresses) and one switch (Cisco to connect different devices - although in my case minimal as there are simply 3 other EEPro’s and the dCS connected to the switch).

The problem I continue to have, and have had since day one of ownership, is Mosaic spinning and unable to discover the Rossini. I have again read the thread Anup listed above - "Regular “Lost Connection to dCS Rossini DAC” - however the timeout delays I encounter are completely different. They are not on the order of 1, 3, or 5 seconds, but rather go on indefinitely until I quit and restart Mosaic - possibly even multiple times. Once again it could be a network problem or iOS problem. My sincere hope is it is not a network card problem on my Rossini - quite honestly I highly doubt it.

As per Phil’s request I will contact him via support and inquire about the test kit. In the meanwhile I have thought about doing my own testing and am curious to hear from Anup or Phil if they think it is worthwhile or a waste of time.

Prior to moving to Eero (and I am not sure I am happy with it) I had been a long time Google Nest mesh user (once again all access points with ethernet backbone instead of wireless). I have some spare Nest routers (not the most recent “Pro” incarnation) and was thinking about connecting one to the Cisco switch, creating a new test network “dCS”, and plugging the Rossini directly into the Nest (the Nest has two ethernet points). This will create a clean network with only one device on it - the Rossini.

Of course I realize every time I want to use Mosaic on my iPhone I will need to disconnect from my main house network and reconnect to the new “dCS” network, however perhaps it is worth a try.

Best
Gregg

[glevethan (Gregg)]

same as what I frequently encounter

[PAR (Pete)]

This loss of connection message can be generated i my case after the blue button ceases to react and is tapped several times in an attempt to get it to work. If you get to see it and Mosaic is frozen then this is almost certainly an issue with your network.

[PAR (Pete)]

Thanks Phil, this is very much appreciated.

[Phil (Phil Harris)]

The loss of connection message simply means that the app has lost its IP connection to the streamer … unfortunately that’s going to be “outside” of the app in that territory that we have no control over…

P

[struts001]

3 hours of very frequent pause/play/change and not a hint of a problem. I wonder what I am doing “wrong”?

[PAR (Pete)]

Hi Phil, I managed to get a screenshot of the blurred screen that happens instead of a correct action from selecting the blue Play button. In this case the previous track had been paused once it had finished and left for a few minutes. I then wanted to recommence play and this is the result:

[Anupc (Anup)]

@glevethan

however the timeout delays I encounter are completely different. They are not on the order of 1, 3, or 5 seconds, but rather go on indefinitely until I quit and restart Mosaic - possibly even multiple times.

Oh! Thats definitely not normal. I’m actually surprised you haven’t escalated to resolve this sooner

As I mentioned in my post above, having cascaded Switches is not inherently a problem. In my case for instance, because of the nature of my home network, the Lina stack in my home-office is literally 5 hops away from Mosaic on my iPhone; Mosaic → Cisco → Mikrotik → Juniper → Juniper → Lina, and I rarely encounter a “lost connection” that last more than 3 seconds.

Considering I don’t encounter the same issue as you do, and I use Apple iOS, and multiple dCS units, the only logical conclusion would be that it’s your network or your particular Rossini which has something funky going on.

@PAR

I managed to get a screenshot of the blurred screen that happens instead of a correct action from selecting the blue Play button.

Interesting. I’ve never seen Mosaic do that. Pete, is it only on your Android?

[barryr1]

I haven’t added any “switches” to clean anything up. My network is fairly large with somewhere over 50 devices. Fortunately many of them are not being used at a time. Between the router and DCS I believe that I have 2 switches. One at the router which basically distributes the network and one at the dcs system which allows local distribution to the (over 100’ away) dcs and other electronic items in the immediate area. The local switch feeds a FMC to cat5 to DCS

[barryr1]

perfect Pete

[johnandvirginia (John Anderson)]

Hi Pete. That’s it! Exactly what I get plus usually the whole image is blurred as well as the blue pause button.

[struts001]

Well, in 9 hours of pretty continuous usage today and trying really hard to provoke this error I have experienced nothing untoward at all. Hopefully that alone is somehow of use in ringing this in. I have Mosaic 1.4.2 (150) on an iPhone 15 Pro running iOS 17.1.2.

PS I an using a Bartók. It seems many of the folks here who are experiencing the error are using Rossini. I assume most of the code here is common but presumably below some abstraction layer there is some platform-specific code??

[PAR (Pete)]

@Anupc

Pete, is it only on your Android?

The generation of the blurred screen is Android only. The response problem with the blue Play/Pause button was also regarded as an Android only problem until it occurred with iOS a few days ago as per my posting earlier in this thread. However this incidence was rare unlike with Android when it is not regular but not all that uncommon.

[imprezap2]

After months of working flawlessly I had a hick up tonight, I was playing music and searching for another artist when music started to have drop outs and after a few seconds stopped playing, I saw in the rossini display the no input message. The screen on my Ipad froze, completely black. After that I heared the rossini switch to have an input again and the mosaic app came back to life and I was able to continue my playlist.

Simple setup, one network cable directly from my providers router to my network switch (s100) and from there with a short cable to Rossini.

[barryr1]

@Anupc i have it on iphone and ipad but occasional. I will say i mostly listen to transport but using qobuz and nas it has happened 3 times or so and only once in past week or so

[Anupc (Anup)]

@imprezap2

I saw in the rossini display the no input message. The screen on my Ipad froze, completely black. After that I heared the rossini switch to have an input again and the mosaic app came back to life and I was able to continue my playlist.

That sounds like a streaming board reset. If you can remember the sequence of actions you took and try to replicate the incident, I’m sure Phil [email protected] would love to get the details.