Installing lms-to-upnp Plugin to Roon enable NDS

I found the solution in another thread in case useful to anyone else. Was an error in the config file:

The key item that was blocking it from working was the line:

<roon_mode>1</roon_mode>

In the default config file the value is set to 0 and it needs to be set to 1.

DPH,

Yes, the room_mode settings you found is required to enable the plugin for roon. You may also want to look at the sample_rate settings (see above posts) if you want to play higher resolution files.

Thanks.

Iā€™ve been following this thread and its variations for some time, and today I decided to try lms-to-upnp. The advice has been useful but three hours later Iā€™m pulling my hair out.
Iā€™ve made sure that I have the correct privileges but I still running into problems with messages like: ā€œcommand not foundā€ or ā€œno such file or directoryā€.
The OSX terminal is frustrating to use as it keeps loosing the correct directory. Is there a better terminal app out there?

The terminal app is pretty solid on Mac tbh, itā€™s strange that itā€™s losing the current directory.

If you want to recap what you have done so far and at what point you get an issue then will try help if I can

Iā€™m trying to install the software on a Mac mini. Subsequently, I tried to do the same on a MacBook Pro. I have had partial success on the MBP, but it does not discover any of my Unitiqutes.
One issue Iā€™ve found is that both computers have two sets of directories for ā€˜applicationsā€™; this may explain why I managed to install it on the MBP.
I wonā€™t fiddle about anymore this evening. Iā€™ll tackle it fresh tomorrow. Thanks for any observations.

Okā€¦it could be that problems such as ā€œcommand not foundā€ or ā€œno such file or directoryā€ are down your PATH definitions. Most often if you are in the correct directory then placing ā€œ./ā€ before the command will cause it to execute correctly.

Anyhow shout if you get stuck, ATB

1 Like

Thanks - I noted that suggestion before and it worked on the MBP but not on the Mac mini. Something to work on tomorrow.

Success - partial at least. lms-to-UPnP working on my laptop for all Naim endpoints (4xQutes and NDS). But I still canā€™t get it to work on the Mac mini. Iā€™ve yet to compare this with the hardware solution from Audiostore, but Iā€™m well chuffed.

Thanks to all for their help and encouragement on this forum, especially @trickydickie and @Jack.

Iā€™ll work on the Mac mini problem another time - off to celebrate with a pint (as long as the road is not flooded on the way to The Bull in Inkberrow.

1 Like

Excellent, glad you got it up and running

1 Like

Have just got this working on my windows PC with few problems. A little wrinkle - The best way to run it on Windows, I reckon is to install the exe as a service. The easiest way to do that is to use a software program, such as NSSM, which installs and manages services.

Many thanks to everyone on this forum who helped with this!

Thanks - still have problems with Macmini
I get it installed then run the file again only to find ā€˜error when reading socketā€™, this is repeated until I stop the terminal. Now Iā€™m out of my depth!

Are both machines effectively configured the sameā€¦same Operating System level, both connected via wired (or wireless), no VPN setup, no other significant differences?

Also did you follow exactly the same setup procedure, if not, do you recall what was different?

Thanks for the quick feedback.
MBP is running High Sierra and the Mini Catalina.
I first started on the mini and tried both multi and multi-static to no avail. I then moved to the MBP and got things to work.
I went back to the mini and tried again with a different directory, which worked partially. Except for the terminal socket error.

As you probably know the software has been primarily tested on W7 and Linux, I doubt itā€™s ever been tested on Catalina. However, donā€™t see any reason why it shouldnā€™t work on Catalina.

Socket errors are normally associated with network related issues. Iā€™m just guessing here but I would be thinking along the lines of trying it again but trying some combinations along the following linesā€¦

  • make sure only the wired network interface is enabled at boot and try running again
  • try switching the firewall off
  • make sure the config file on the MBP and the mac mini look reasonably similar, nothing really obviously wrong
  • switch off any AV software that might be running
  • remove the ā€œlmstoupnpā€ software completely from the mac mini and start again

Iā€™m assuming you have the same rights and permissions on the mac mini as you have on the MBP and that relevant lms files have the same permissions

Failing all that and if you still have the motivation you probably need to start up the ā€œconsoleā€ app and start reading through the log files and looking for associated messages that help you pin the problem down.

BTWā€¦where is the Roon Core running?

I have mine running on MBP Catalina with no issues.

Never come across the socket error. Buy is looks like something silly. Keep at it. I am sure you will resolve.

I suggest you post screenshots of your error logs here. The more experienced eyes you can get to look at it, the better.

ASenna04

Thanks for the hints guys (@ASenna04 and @Jack).
Just poured myself a cup of tea and going to tackle the beast.
I have the Roon core on three devices: Audiostore music server, MBP and Macmini. The black box is a hardware solution feeding my NDS, theMBP must be approaching itā€™s first decade birthday and is usually just used for ripping, the Mac mini is my work machine.all except the MBP are wired into my network. My music is all on the server, with copies dotted around the place in a couple of NAS and on the computers. I should be content with Roon on the MBP as I can use it now to play to the Unitiqutes, but itā€™s on its last legs, hence Macmini (although that is 8 years old).
Anyway time to see where itā€™s at and probably a reinstall.

Good question - and one that Iā€™m also struggling with.
But how will a Roon trial decide that?
Surely you need to compare an NDX2 in your system vs a hacked NDS?
But has anyone ever made that comparison??

My dealer (who I trust) said that the NDS was quite a way ahead of the NDX2.

Given the similarities with the ND555 itā€™s not surprising and it makes full use of the 555ps has the same DAC, the brass suspended boards etc. Remember this was Naims source of choice for demonstrating the Statement before he ND555 came along.

Of course the NDX2 can start as a standalone player and be upgraded in increments and has the new platform. You need to start the NDS with at least an ND5 XS power supply and ideally a 555ps. I started with an XPS DR and switched to a 555 DR, the difference was very significant XPS DR vs 555 DR.

I once had a demo of all the new streamers, for me the magic happened with the ND555 and I get a similar ā€˜feelingā€™ with the NDS (I had an NDX v1 before).

2 Likes

Hi Huw
How come youā€™re trying to get an LMS-to-UPnP plugin working when you have the Audiostore hardware box working?
Thanks
Jim

Good question.
The answer is Iā€™m reluctant to fiddle around with the black box setup (scared I would loose the NDS setup) ā€¦ but now Iā€™ve tried with LMS I might be tempted to set up other outputs with the black box.

1 Like