n-stream 3.4 -- unable to find upnp server after app sleeps
Posted by: DavidCT on 26 August 2013
Hi,
I am streaming to my NDX from a Synology nas running both Minimserver and the Synology Media Server. After inactivity, n-stream goes into the background. When I reactive n-stream, it can control the playing music and play different titles from the queue. However, if I try any operation that browses the current upnp server, I get a message saying that the server can not be contacted. I can still browser the upnp server from the NDX controls.
If I kill n-stream and restart the application, the app sees both my upnp servers. This problem did not occur until I upgraded n-stream.
Are others having this challenge? Any tips?
Thanks,
David
Continue to have the same problems even after turning both ipad and ndx off and on, resetting the wifi etc. Ipad has latest Os update, but I use devolo not aiport for networking.
However ndx is running 3.16 - I don't feel the need to update firmware but now wonder whether this might be causing the compatibility issues. When I select compatibilty mode, it all works fine, within those limitations. Am I alone with 3.16 or must I update in order for nstream to work?
Please Naim, this is frustrating, I have had a full year of absolutely rock solid performance and reliability with my system - nothing has changed my side, other than this last nstream update - I would rather ditch the upgrades and go back to the previous version if that is possible?
Superuniti 3.21
n-stream 3.4.7079 on ipad 2 with OS 6.1.2
NAS Synology 112+ DSM 4.3-3776 with Logitech media server and 2.5GB of FLAC music
Before the last update of n-stream and Superuniti everything was running very well. No matter from which situation I could start n-stream and the NAS was found after very latest 10sec and I could browse my music collection.
Now the situation has changed.
N-stream has become unreliable in terms of start-up and detecting the NAS. It takes between 1-5mins until I have a usefully system where I can browse the collection and start listening to music. One situation in terms of recovery time is e.g. when I have been listening to music, left the system running, hibernate the ipad and return e.g. 1h after the last song has played.
What is really strange is that sometimes even when there is "no server", I just press play and the first song from the last album starts playing, it nevertheless takes the mentioned 1-5mins until n-stream reports the server as detected and I can select song from another album.
In the meantime I have been trying different methods to make my system recover faster e.g. restart of Superuniti, restart of n-stream, toggle upnp modes, refresh covers etc etc. - it didn.t help.
Currently I'm really frustrated and I'm very much hoping that NAIM will be able to correct the situation in the next few weeks.
If I only could, I would immediately step back to the versions I had before.
Hm, it looks increasingly like multicast discovery got broken somehow with the latest Nstream version with iOS 6.1.x. Perhaps an Apple software library issue. iOS 5.1.1 appears to work fine.
Simon
My setup is:
NDX
Synology DS710+ with Synology Media Server / Minimserver
iPad 4 / iPhone 4
Asus NT-56 Router
Netgear Gigabit switch
+ TV etc.
I experienced the “server not found” problem when I first added the NDX into the network back in January (as well as with the demo unit I had prior to this). I overcame it by making changes to the network setup.
Originally I had everything running in DHCP mode, both on the router and devices. I found that manually assigning the IP in the router (against MAC address) for each device on the network solved the problem. I left the settings on the devices unchanged (i.e. DHCP). (NB: I switched all the devices off before changing the router settings, then switched them back on one by one afterwards to mitigate any risk of the devices getting in a muddle).
When I updated nStream/NDX last week I too saw the problem a few times once again. I updated the firmware in my router, reset the settings and then added back the manual IP assignment once again. The problem has not re-occurred as yet (famous last words!)
The only other change to my network is that last week Synology brought out a new version of its software (DSM4.3) as well as a new version of the media server (which has been updated to include a specific profile for nStream). As I previously experienced this problem with other DLNA servers that I tried (Plex, Serviio, Minimserver), this is probably not directly relevant, but I mention it for completeness.
If you are not already running a similar network set-up it might be worth giving it a try.
Best of luck!
Nick
I have tried all the suggestions in this thread but I still get the "unavailable server" scenario.
Killing and restarting the n-stream app always cures the problem.
This is only a n-stream update issue, and not a streamer update one or a combination of the two, as it started when I had only updated n-stream.
It's rather annoying...
If anything it's worse! 2x "No Network" in wireless operation before finding the NAS, sleep mode re-enabled... zzz...
I'm using an iPad with 6.1.3, Asset on a Win 7 Server, wired to QNAP NAS and NDS, wifi via Netgear WN802Tv2. No problems with uPnP discovery.
Continue to have the same problems even after turning both ipad and ndx off and on, resetting the wifi etc. Ipad has latest Os update, but I use devolo not aiport for networking.
However ndx is running 3.16 - I don't feel the need to update firmware but now wonder whether this might be causing the compatibility issues. When I select compatibilty mode, it all works fine, within those limitations. Am I alone with 3.16 or must I update in order for nstream to work?
This issue first appeared here post N-Stream update and was not solved by updating the NDX firmware which suggests it is an N-Stream bug.
Morning all,
I am having issues also since upgrading the n-serve app. I use an NDX with a ReadyNas Duo V2. Some recently played albums come up and others say 'Cant Play Skipped Track'. Interstingly all is ok with the remote.I have noticed that serching for music has slowed down also.
G
Hi Guys, sorry for only just spotting this thread. Has anybody with the problem tried to delete n-Stream from their device and re-install it from the app store?
Be careful deleting n-Stream if you have created any UPnP playlists as deleting the app will delete them too. You can back them up by connecting the iPad/iPhone to iTunes and using the file sharing feature for n-Stream (copy off the playlist files then put them back once you have re-installed n-stream)
Did as you suggested.... All working perfectly again!
It's all very strange.
G
TJ,
I tried your suggestion but am still experiencing the challenge.
David
TJ, I tried your suggestion but am still experiencing the challenge.
Me too, I now have to kill the app. daily.
Everything looks ok until you find what you want then press play - "No Server".
Exit / kill app / reload app / works fine (for some unspecified time that seems to equate to a day on average it seems), irritating!
@hafler3o
Did you delete or just kill the app? My suggestion was to delete then re-install. Remember note about backing up playlists
@DavidCT & others
could you tell me:
- iOS device type
- iOS version
- App version
- UPnP server
- Router Make model
@hafler3o
Did you delete or just kill the app? My suggestion was to delete then re-install. Remember note about backing up playlists
Deleted app. / reinstalled app. last week. Now I know how to kill the app. I'm not forced to use compatibility mode full time (a relief as it is crummy), just killing the app. when it refuses to recognise the server. I don't bother with playlists, I select albums and play them... I've never been 'into' playlists. I'll post my info later, btw what's an iOS? I know what the other stuff is.
iOS is what Apple calls their iPhone and iPad operating system, Basically I want to know if you have an iPad, iPhone or iPod touch and which version of the Apple operating system it is running.
We are looking into this issue at Naim
Hi TJ,
Excellent news, I trust you are looking at the "gapless" issue also. Using ipad 6.1.3.
Cheers,
Bill
could you tell me
Device: iPad Mini / ver 6.1.3
Naim App: 3.4.7079
Server: WD MyBookLive 2TB with Twonky 5.1.9
Router: Technicolor TG582n
TJ, are you able to confirm Naim are looking into the gapless issue as well. I believe that was reported prior to this issue (a couple of days after releasing the firmware) so hopefully yes?
Interesting I don't suffer the discovery issue, but I am running iOS 5.1.1 on an Apple AirportExpress wifi.
Thanks
Simon
Tj details as requested
Devices IPad 2 ver 6.0.1 (jailbroken) & Ipod touch 5th gen ver 6.1.3
Naim App. 3.4.7079
Server. Netgear Readynas Duo 2 running Minim Server, Logitech media server & ReadyDLNA
Router. BT Homehub 4
I have also tried uninstalling the apps on both devices and reinstalling.
Hi TJ
i have also tried deleting and reloading the app - it worked from the first attempt last night, but today I have the same problem.
i have iPad 3 running the latest iOS 6.1.3
windows home server running Asset
standard BT Business broadband hub, to which NDX (3.16) is hard wired via a netgear gigabit Ethernet switch.
ipad connecting over wifi using Devolo AV200+
Nothing has changed in this configuration over the last 12 months other than the iOS and nstream updates.
Thanks for the info all, I think we are making progress tracking this one down. RE gapless issue that was reported, yes it is being looked into.
TJ - thanks for letting us know
Simon
Simon I believe I have been remiss in thanking you for responding on a number of issues I have posted about, so accept my apologies and thanks for the input too!
TJ thanks also, I now have another 'issue', and that is after going into multiroom mode the client (Qute2) wirelessly connected upstairs, loses the network totally at some random time afterwards! I mean I having to rescan for available routers, put in wireless network key (!) I'd have thought the Qute would store that somewhere inviolably (until overwritten), just how would I come adrift from my home network so easily, and without any warning, I mean all it would say was "Can't play track", hardly a useful message for an unassigned streamer surely?