Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems INFO: New Firmware for 218, 251, 271, ID41

If it is a 218 or 251, connect directly to the device, no network involved.

I had the same problem, only when I had everything hardwired to a cheap switch it worked.

I could not get it through one of my Cisco 2960 switches. Last resort could be to connect it all directly to the router.

I had to look for an old laptop, these modern things have no ethernet port anymore. Good luck. It is worth it, my network performance of the 218 has improved. Less drops and smoother recognition on the network without rebooting.

Thanks for the suggestion Mimesis. Reading the comment about using 'a cheap switch', I looked at the switch I was temporarily using to connect the laptop and Meridian devices.
It was a Netgear GS105E. It was a cheap switch, but looking at the Netgear webpage, a support app can be download to update it's firmware.

I did this and noticed that a second GS105E also appeared. It is a switch installed in the back of the TV cabinet in the living room.

After updating the firmware on both switches, I looked at the other available options in the app and found a Multicast page for IGMP Snooping Configuration.
It was enabled, so I disabled 'IGMP Snooping Status' and 'Block Unknown MultiCast Address'. I repeated this for the second switch.

This solved the problem and I was able to update both Meridian devices.

Connected my laptop directly to the ID41 but still showing “Preparing Device for Update” forever.

Turned off 818, unplugged, turned it back on. No difference.

Anyone have any ideas?

Run it with admin privileges. This might help.

If someone could provide me with a copy of the Meridian Device manager I would be very grateful.

I have e-mailed the importer for Meridian in my country but no reply. According to their website there is only one Meridian dealership left: an interior design studio 😳 I think I need not bother asking them.

Thanks in advance

So after acquiring a new Nucleus (as recommended by our local M dealer) and applying the Meridian update to the ID41 cards in our 818 and 861 (with Bruce's help - again thanks), I thought all would be well. Unfortunately no. Last night while starting to play a new album via Roon/Tidal, I liked what I was hearing so tried to add it to our library (while the first track was playing). The system immediately choked, losing the 818 endpoint that had been playing. Once the endpoint was again recognized by Roon, I tried again. Same result. Tried playing through the 861 - same behavior. Rebooted the Nucleus. First try again, no joy. But on second try, the album played in its entirety. So no more trying to add to our library while listening. (I used to do this regularly.) Does anyone know if Meridian is working on a solid firmware fix (or new interface card)? This behavior is not acceptable.

John

I have had similar issues using Roon lately. Choose a audio source and play a track (always a Meridian 218) the endpoint will disappear and Roon will display choose an audio zone. I need to investigate further to see if this is also the case with non Meridian endpoints.

This is the same thing that is happening to me, as well as sometimes losing the endpoint by just opening Roon on my iPad.
I have yet to update the i41 in my 818v3 as I do not have a copy of the new Device Manager.


.

I can send you a copy.

FYI - Roon has been terrible with M zones for quite a while. There have been significant code issues causing memory chokes and general bad server performance. The M zones seem to be quite impacted by this (you can see it in the logs). However, recent updates and fixes to Roon pushed into their EA (Early Release) program have been improving things. It's still not 100% yet as the memory issues still seem to brew up after a day or two between reboots.

So, my point is that if you are on the main production release of Roon, you may not have seen any improvements yet.

My experience is that with the ID41, the network glitches and zone disposal annoyances, have reduced with the new firmware. Roonserver still has some work to do.

Hope that helps

My system must be the exception to the rule, as I’m not experiencing the regular Roon drop-outs that others are reporting.

Typically, on Saturday mornings, by 9.00 am, I set up Roon once to curate/stream my chosen music genre for the day. My system isn’t closed-down until 6.00 pm.

I simply don’t experience any problems.