Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Streaming QNAP software

tl;dr

If you are trying to detect if core is running, either run up Sooloos config (PC only) or sniff the LAN for UDP multicast messages on several ports - iirc they are all around 90xx and very obvious when they are being broadcast - iirc one was core beacon, can’t remember what the others were for (possibly store and audio endpoint). It’s long time ago so cannot be sure on exact port numbers - memory very sketchy on the old Sooloos protocols.

You should see the multicast transmissions several times a second, and one of your originators should be your core (and iirc store should be same), but by nature of multicast, which applies to Sooloos config which is looking for same messages.

The UDP multicast messages may be significantly filtered or even dropped altogether. If you don't see evidence of the multicast messages within a few tens of seconds, then assume core is not running or your network is dropping all of them - but as iirc you once had this up and running on a different core device, you must have had a network that at the very least passed these occasionally.

Without the presence of a full set of the UDP multicast messages, Sooloos will not work.

Hi Ian

Many thanks for the message.

I had an idea there would be some UDP packets shuffling around on the network from the Sooloos hardware... so, given the approx port range you mentioned, I can initially do a quick check on those and see what's going on.

Regards,
Tom

The Sooloos QPKG I have is 29MB also. I wasn't talking about the QNAP admin pages. I was saying that you can bring up the Sooloos web interface by clicking the Meridian icon that is on QNAP admin page. The Sooloos web interface will allow you to pick tracks to play on any of your Sooloos end points. If you don't see any endpoints in the drop down other than Local Playback Zone, then you have network issues. Normally firewall settings, but could also be network configuration.

Charlie

Hi Charlie

Thanks for the info.

It's interesting that your QPKG is about the same file size as the one I have.

Though, another forumite has offered to email me a "combination" of both firmware and plugin, which in total, imply that the QPKG is a bit larger than 29Mb. Will see how it compares once it arrives


OK, so in my case the "web interface" on the Sooloos plugin just doesn't work. (see above message as the "webpage" doesn't appear to exist.

It used to, on my original 251 but since that died, I've just been trying to put things back as they were on a (new to me) 251.

As for firewall, this is all running off a local network, so, the router config doesn't actually come into play (in my case) as far as inter-device traffic goes.

Network topology and management is one of my strengths, having done this for nigh on 30 years !!

I've actually had a bit of fun today, looking at the TCP packet data going between the QNAP, the Control:10 and my "packet sniffing" hardware. Quite a few "unassigned" (according to RFC6335) packets moving on the network, mainly on ports: 9003, 9011, 9012, 9013, 9021, 9030, 9050, and 9099. I've got to capture the packets next and see what's being carried over...

Regards
Tom

Those are private multicast discovery packets from various Sooloos components. Many years ago, I wrote an iOS app that detected the Sooloos hardware using those. It allowed me to detect what pieces of network hardware didn't play nice with Sooloos.

A few more images in this link to the Gallery

Hi

Just wanted to give you some feedback on where I stand as of 15 minutes ago.

1) I received via Dropbox 2 different Sooloos QPKG files: one of approx 29Mb size which is suitable for QNAP firmware upto 4.2.x. The second QPKG file is approx 79Mb and is suitable for firmware upto 4.3.x. Who knew these different size QPKGs were for different QNAP firmwares? Not me for sure.


2) Having recently installed a QPKG file that was 29Mb onto the v4.3 firmware, I was surprised that a) it didn't work and b) there was no feedback given (during installation of this QPKG) that older QPKGs did not work on newer QNAP firmwares. The earlier version also took up ZERO memory (after installation) when viewed via the Dashboard Resource Monitor of the QNAP, which lead me to suppose it wasn't properly installed and might be a corrupted file.


3) Installing the 79Mb QPKG has brought 100% SUCCESS...the QNAP is accessible via the touch-screen of the Control:10 and my entire library of CDs from the pair of RAID-HDDs taken from my earlier (and dead) TS-251 are now available and playing music... hurrah !!

The actual Sooloos QPKG that is now installed is version 2.527 and it is running on QNAP firmware 4.3.6.0895 - it is also using around 200 Mb of the RAM in the QNAP (now usefully upgraded to 8Gb).


The ONLY issue I had this evening was that on re-booting the system I saw a "flashing" message icon that said that more than one device was set as "Core" - in this case, both the Control:10 and the QNAP were set to be "Core"...so, given that the QNAP was now accessible via the System Settings, I just de-selected the QNAP as a "Core" and left it to the C10.

----------------

EDIT: When clicking on the M icon of eh Sooloos plugin in the QNAP App Manager, I am still getting a blank screen (in my browser) that says:

404 Not Found

"Not Found
The requested URL /webclient/WebClient.html was not found on this server."

I can live without this functionaility - as I usually control things via the touch screen - though I'm wondering what might be causing this...?

----------------

I will give the fully functional system a while to fully get used to itself now and I might just play some music...


It's a shame that Meridian stopped development of this after the Sooloos founders left the company - as it's a cracking system...but they could maybe learn a lesson or two about version numbering and installation routines and feedback during said process.

But I am also so glad that I found this forum, as it has helped me to get my music system working again.

So, a big thank you to Longitude for "going the extra mile" to share the files he had. And thanks to others who've replied to this thread as all of this info has assisted me and it might now also help others who have issues like I've had.

regards and keep safe
Tom

If your QNAP is half decent, I would make that core rather than Control:10. More specifically, Core and Store on same device is better than distributing them. It gives core local access to store which can have some benefits.

For starters, check that Sooloos is running on correct port - iirc it expects port 80.

Remember that Meridian system setup and configurations were designed to be for dealers to do as part of a whole service. If you want to DIY, then you are outside this knowledge. Also, QNAP was a bit of an afterthought, but again it officially needed dealer support to start the process. The Sooloos hardware solutions just worked out of the box, unlike QNAP.

Another reason for having QNAP as the core is that, at least in my case, Tidal still works whereas not with cores on Meridian hardware for the moment.

Hi Ian,

Thanks for the info.

When I killed my TS-251 I had three options: Buy a totally new, latest spec, multi-bay QNAP (and hope it would accept my pair of original HDDs) - or find a s/h 251 (in any condition) and transplant it's motherboard into my chassis (which takes about 5 minutes and undoing 7screws) - or find a s/h TwinStore and go fully Sooloos.

The first and third options didn't work due to cost and/or availability so I luckily found a slightly battered but working 251.,,,so I don't have the benefit of the latest gen Quad-core Intel CPU but it does have a Dual-core Intel® Celeron™ 2.41GHz (up to 2.58GHz) - and having now ramped up the QNAP memory from 4Gb to 8Gb (@1600), I think there's plenty of resources available for Sooloos to run (and Plex too).

However, having got this up and running properly last night for the first time (with restored plugin), the initial issue was that both the C10 and the QNAP plugin were set to be "Core" - so for simplicitys sake, I just used the touch screen to set the C10 as Core and see how it goes...but I do realise that it might be better on the QNAP...so hopefully I can switch that around once everything is "bedded in".

I can get to the Control:Web interface on the C10, via my PC, without issue and that is correctly shown in the PCs browser URL bar as "192.168.1.201/webclient/WebClient.html".

The QNAP is using port 81 for the "web interface" in the QNAP settings.

Just to be clear, the error occurs when clicking on the Sooloos icon in the QNAP AppCenter when viewed from a browser...and when clicked on, it opens a new browser window but in the URL bar is just showing the URL as "/webclient/WebClient.html". So it looks to me that the Sooloos plugin doesn't know the IP address of the Core - and there's no way of setting that on the QNAP....unless this is supposed to happen automagically?

But it could well be that as my Core is the C10, and not the QNAP, then this could be why it's failing and displaying an error.

I have watched (and owned) Meridian products for many years - they went from being a pretty good amplifier manufacturer (101/103/103D/105), to then embracing CD (MCD/MCD Pro - using rebadged, re-engineered Philips chassis) and to then realise that they should be going a bit more upmarket...in the same way that Linn and Naim also started selling more expensive and better made hardware, so Meridian brought out the 207CD/pre-amp, and then the rest of the 200 Series. After that came the 500 Series which cost even more. Then came the 600 Series.

This was all at a time when economies were booming and there was a market for this sort of product, as the people who bought into Meridian in the early days, wanted something better and would upgrade and were prepared to pay for it.

So the whole idea of Meridian trying to become a high end brand and at high end prices is not lost on me...and seeing the external build quality of the Sooloos does make it look and feel very much "top end" and so it would be expected that dealers would have greater involvement with customers purchases - in the same way that Ferrari and Mclaren have with their customers.

I totally "buy" this as being commensurate with a high end product...though Meridian have shot themselves in the foot completely, by discontinuing all direct support for Sooloos...which I think is clearly down to their management having a "fit" about the founders of Sooloos walking away.

The one thing you should never do is to make customers who've paid a premium for their products, feel that they have been "cut off". And with Bob Stuart leaving too, and Allen Boothroyd passing recently, there is not much left for Meridian to do...unless they can find a "digital guru/designer/engineer", who can lead them on to better things....plus they need a new "industrial designer" to give their new products (should they make any) a bit of flair.

regards
Tom

I am afraid Richard Hollinshead the Guru you accurately describe was probably the first to leave.

Just to complete the important leavers list.

Hector