Keyboard Shortcuts
Likes
Search
strange issue with Media Player Object
I've been seeing a strange issue with the SmartGraphics Media Player Object on a couple different projects, and am wondering if anyone else has seen it. Then I saw it happen with an NAX streaming player, and another system with an Autonomic.? These are systems that had been otherwise working fine for months or years.? I noticed there's a new Media Server Object Router v4.1 module in the recent database, but couldn't find (or remember) what the differences are between that and v4.0.? I'm planning to swap those out at one of the sites tomorrow, but again am wondering if anyone else has seen this? |
Thanks Oliver!
toggle quoted message
Show quoted text
There aren't any MSPs on the CRPC signals, but that's good to know. --- On Friday, February 16, 2024 at 2:21 AM, Oliver Hall wrote: |
I have definitely seen this with Sonos. Basically it looks to me like the basic commands like transports (which work without the MPO) are working but more advanced things like Feedback and list selection buttons don't work.
Rebooting the program with the SonosSystem and Device modules typically fixes it...:( This is why for years I've put the Sonos stuff in a separate Slot program so it could be rebooted separate from the main program.? I have the CRPC and CRPC_FB passing thru the 3-series EISC and have not seen any particular issues with this. Note: In my Sonos Program, I've made sure to set each of the Device Module v3.2.0 IP Port Number Parameters to a different port number. (I'm using the range:: 41991, 41992, ....) I've complained since almost day 1 of the Sonos integration that the SonosSystem module lacks a 'restart communications' trigger so that you don't have to reboot the whole program...but crickets as expected... I have not noticed this with Autonomic thus far, but I may be just missing the opportunity. |
Thanks Chris.
toggle quoted message
Show quoted text
The first site that reported the issue already has the Sonos modules running on a dedicated RMC3, with the CRPC signals running through the 3-Series EISC. I thought the EISC might be causing an issue at first, but it's been running this way for over a year, maybe two. I just updated it from the 3.1.1 modules to the 3.2.0. I might also stagger the ports like you've done. Although I really don't expect those changes to make a difference, I don't think they'll hurt anything either. That same project also has an Autonomic they're trying out - because we first thought it was a Sonos issue, AND I've been telling them to use Autonomic instead of Sonos for several years :-) A couple of days ago I witnessed the same issue with the Autonomic, which let me know it was a Crestron problem, and not a Sonos problem. The Autonomic logic is in the main program, with the CRPC signals connected directly, not going through an EISC. I've done many, many systems with both Sonos and Autonomic over the years, and this is my first time seeing this particular issue. Another project has both Sonos and NAX, but they mainly use Sonos because that's what they're familiar with. Once they started reporting the same issue, I had them try the NAX for a couple of days and I just heard they've seen it with that too. I suspect it has something to do with a recent software, firmware, or database update, only because it seems to have started recently, within the last few months. It could also be that the clients have only "mentioned" it recently, but I have a few that love telling me something isn't working right so I'm sure I would've heard about it :-) --- On Friday, February 16, 2024 at 9:33 AM, ckangis wrote: |
On Fri, Feb 16, 2024 at 09:42 AM, Eric Luckart wrote:
ckangis, Have you tried the latest Sonos modules? They have a re-establish communication trigger.Eric - Yes, I've been using the System v3.1.1 and the Device v3.2.0 modules since they've been out. When I've had the chance to T/S issues in the last month, my experience is that the 'Restart' trigger does not resolve comms issues... Not that I'm surprised, for some reason Crestron and/or Sonos refuses (IMO) to resolve the root issue and thus secondary issues continue to be a 50% solution. FTR, 50% of our systems have '0' problems with Sonos Comms and the other 50% have constant issues. And yes, I've reviewed the system designs - there are no obvious differences...:( Have your second slot program restart every night at 3am and that will eliminate 90% of your issues...except the ones that happen during the day...The 'Digital age' is really embarrassing... Tony, Sorry to Hijack your thread, though U think that it is kind of relevant to your situation... |
I have seen this before and we mostly use Autonomic. Many times rebooting the MMS fixes the issue for us- havent really tried processor as its quicker and less disruptive to reboot the MMS. So I'm not sure whose side its on. Although a MMS-3E on my home PRO3 system that hasnt been updated in at least a year I never have problems, and some of our sites never have an issue. All of them have up to date MMS firmware so yea it could be something Crestron DB relayed or even firmware. Its kind of embarassing when we sway people from Sonos to Autonomic then it blows up in our faces.? ?
|
FYI, Currently (for the last month) it seems that Sonos is having issues even within their own systems. Reports of some players in a system not even being able to play audio!
We've also seen multiple sites with 2 players in the last month where one player will work fine and the other is completely non-communicative... Digital music is a Crap-Show and as I said earlier... ?The 'Digital age' is really embarrassing... |
Its weird. the 1070 freaks out yet my crestron go ui is totally fine. thinking its probably SG or touchscreen related. Sucks as its not something i can fix by myself.?
Sonos has no real interaction with the services, autonomic is a bit better, but no one really has anything that great. Or it has limited services that make it a no go. |