Another 'latest NStream / Software 3.16' thread

seems to be common, i switch to another input eg ipod then back to pC which always correct IT   A

From what I've read here 3.16 is using a completely different communications approach. The old versions used a Naim proprietary protocol to communicate to the streamer, which in turn used uPnP/DLNA to communicate with the Server. Now, nStream has become a proper uPnP control point and uses uPnP wherever the protocol supports what it is trying to achieve. There are of course pro's and con's.... Using a proprietary protocol, Naim could do things like like replicate menu navigation in real time, and support special features that only its players understand. The limitation is that it cannot directly control the Server without relaying commands through the streamer.

uPnP / DLNA are an industry attempt at standardisation, but inevitably it becomes a lowest common denominator.

At least it's comforting to know I'm not alone

Mind you, I don't think it should be happening really

Help! I've finally got rid of my Internet over mains connection (cheers heard from Phil and Simon-in-Suffolk!), moved my router down to where my SU is, moved my Synology NAS ditto, updated the SU and iPad firmware/software to the latest. But instead of everything being hunky-dory, I've got a new problem. On iPad and iPhone, when I choose uPnP, I get a message saying 'no server'; yet if I choose the same input directly on the SU I have full access to what's on the NAS. Also if I use Synology's rather nifty DS Audio app I seem to be able to access everything ok, though I do worry it maybe doing some downsampling or something. So it only seems to be through nStream on my iPad and iPhone that I have a problem! But this is the App I want to use.

One further thought to throw into the mix. I'm currently using a Virgin Superhub, much hated by many on these forums. I'm considering switching it to modem only and buying an Airport Extreme. But do you think it could have any bearing on this issue, given that it's just acting as a switch here for two hard-wired connections?

Thanks

Paul

Silly me, should have read more thoroughly before posting. It's the same uPnP compatability button everyone else has been having to press. Sorry to have bothered you all!

That's interesting because it also suggests to me that Naim streamers will be more likely to respond properly to 3rd-party control points than they have in the past. Some of these I definitely prefer to NStream but they didn't work very well when I tried them and my ND5XS would "hang". 

Paul, congratsson removing some horrible pollutants in your house.. However with your server not found message.. Does it happen all the time or occasionally? If the latter clearing the cache on your iPhone iPad might help, but there could be a bug with the latest version of  Nstream inter working with the latest firmware.

If however the no server found is always or frequent.. and might have hapalbeit from time to time with the old stream, that could be because your home network is not correctly supporting multicast. Some cheap internet router switches and wireless access points are guilty here.

For streaming I recommend a dedicated consumer unmanaged switch (Netgear, Linksys etc) to connect directly Naim network player, upnp server and wireless access point. With the latter I recommend the Apple Airport Express as it supports upnp/AirPlay multicast discovery and update info.

Its what I use and I have no network problems at all.  I read  on the net that the Virgin 'Superhub' is notoriously bad and best delegate to Internet access router duties only. I have had performance with occasional server not found message  and playlist corruption issues with the latest Nstream, but I cleared the iPad cache, and ensure I don't have multiple controllers active, and so far issues have gone.

Simon

Hi Simon

Thanks for the response, you're most helpful as always. I'm afraid clearing the cache hasn't helped, so I've had to switch compatability mode on on both iPad and iPhone. This clearly isn't just my problem, givenhow many people have reported it here.

Im trying to understand what you've written re Airport etc. Given that my SU and NAS connections are now hard-wired, though obviously nStream is still wireless, do you think going to an Airport device will still make a difference? The dreaded Superhub does seem to be doing its job, but I'm willing to spend if it'll improve things.

Thanks

Paul

Is it just me, or is it a general problem that quoting other posts doesn't work on an iPad.... Anyway, Chris, in response to your post:

I don't think Naim quote their streamers as being uPnP certified, and I can't see them mentioned on the uPnP forum, so they can adopt the parts of uPnP that they need to talk to 3rd party servers without having to support the full set of uPnP standards. Same applies to DLNA.

Standards are always funny things... In theory they ensure compatibility between vendors, but after 27 years working in IT it's never as simple as that.

The bottom line is that 3rd party control points 'might' work, but I doubt Naim would be particularly helpful if they did not. As has become clear in other posts, Naim work hard (ignoring bugs for now, which I'm sure they will address)  to make sure their products interoperate well and deliver the best possible results. Whilst other solutions may well deliver equally good results for those technically included to experiment, Naim do not guarantee it.

Sometimes it's fun to play though 

Hi sorry work kept me away. The airport express provides the multicast path between the controller / Nstream and the SU and the upnp controller. This will  allow the controller/Nstream  to find the devices and get realtime updates from them. If uour SU works with the IR controller but not with Nstream it point to this. If the IR controller on the SU shows issues with the "server not found" message  etc then it point to possibly your upnp server or super hub and I would try a dedicated switch connecting SU, UPNP server, Superhub, and.. I would recommend airport express for trouble free wireless multicast for iPhone and iPad. (required for AirPlay and UPNP)

However I think there might also be a bug with Nstream which is not helping, but so far removing all other controllers talking to Naim, clearing cache, and ensuring iPad and iPhone don't 'clash' (i use one or other) I have seen no issues for a week now and I am using Asset V4 UPNP/DLNA server.

Simon

Referring back to my original problem, the cure seems to be to always take the SU display back to the server list (there is only the Vortexbox in the list) when I've finished a listening session.

Just tried the new playlist version of n stream and it is back working, after some initial success, it hadn't been working with the server not responding message. For the last week or so I have been using compatibility mode.

I can't think what's changed over the last week.....

And I've tried my Iphone and that is now working with playlists, and that never worked. Strange.....

Have naim discovered some way of silently upgrading their products 

This makes me think there is nothing fundamentaly wrong with my newtwork, and perhaps there is some minor conflicts happening software.

No such luck here, still need compat. mode

Evening all,

I used to access my music on the ipad/iphone by selecting the following UPNP>Ready NAS>Browse Folders>Music. If I do this without selection UPNP Compatibility mode I received the message “ Server Not Responding”. If I select UPNP Compatibility mode it works however I still have several NULL entries that I never had prior to the upgrade. The bizarre thing is, if I use the panel on the front of the HDX I get none of these issues and all albums/track names appear as they should.

I am sure it is something simple but I am completely lost...................

It's called progress.

Exactly the problem I have with my SU in UPnp compatible mod,see in my other thread: https://forums.naimaudio.com/di...nt/18884205030885688

It is not the SU, it is either the N-stream or the Streaming process from Naim

So Naim, you got some problem here!