n-stream 3.4 -- unable to find upnp server after app sleeps

Yes! SuperUniti and UnitiQute owner, all machines see my WD NAS and can play but occasionally the app. will not 'see' the server for ages (never happened before). Less occasionally the app. reports 'No Servers' and I have to toggle 'UPnP Compatibility Mode', ending up on the noddy mode...

Out of interest how do you kill n-stream? I had to uninstall/reinstall re-run app. to get things going again. No amount of cache refreshing / clearing or device swapping / power cycling will work.

 superuniti here, and the same issue... When it occurs, I turn to vinyl 

Leave the N-Stream app.  Then double click the I-Phone button.  This will display a list of open applications.  Then click on the n-stream app and keep your finger pressed down. Click the minus sign on the app to kill it

David

Thanks, I must get up to speed with "how to" instructions, problem is I'm enjoying the SU too much!

Same problem here with n-Stream 3.3 and NDS. In a few occasions it even stopped playing half way through the track  . I thought there was something wrong with my QNAP NAS.

I don't have this problem with a UnitiServe feeding a Uniti and a Qute.

If you leave uPnP compatibility mode switched on does it work OK?

Same issue here with N-Stream/NDX and ReadyNas Duo :-(

No not ok, it works but cannot perform many functions..

No problems here using Asset and NDX.. But I am using IOS 5.1.1 which might be something to do with it.

Simon

Same problem here, using twonky on a readynas. With the previous version of n stream I had to use compatibility mode since It never found the servers so this is still a bit of an improvement for me.

Also have the same problem using minim server on a readynas duo2 to a ND5XS. Also have the Logitech Media server and the readynas media server running, both of these work fine. One thing I have noticed is when playing music using minim server and the server disapears, it comes back on its own after a couple of minutes. 

I forgot to say, I also use Apple Airport Extreme wifi for my iPad control point, and I ensure I enable multicast support (enabled by default) and I have no issues.

When I use a Cisco 870 wifi I have similar issues to those described above, but I have done so with earlier versions of Nstream as well.

I do wonder if this is linked to upnp discovery not working properly in some hardware/software combinations.

Simon

Thanks for all the suggestions and its good to hear that I am not the only one experiencing this issue.  Simon, I agree it is likely a discovery problem related to software/ hardware configuration.  

The thing is that I had absolutely no problems before the n-stream upgrade and I am using a wired network configuration setup by my local dealer.

@TJ - is this potentially a n-stream issue that you can look into?

Same issue here with NDX-Synology! Frustrating...

Fred

I noticed something interesting.  If I configure n-stream in setup to never sleep, it does not lose contact with my upnp servers.  So discovery is working on app startup and while the app is awake.  

So the problem is only on discovering my upnp server when the app wakes up.

David

Is anyone experiencing this using an AppleAirport Express wifi and/ or ios 5.1.1. As I am using both of those and no problems at all here.

Simon

Hello Simon,

I use also an airport extrem and an iPad 1 with no problems. Even gapless seems to work with my NDX. Only time4seek don't work with studiomaster. I think my qnap is'nt powerfull enough for this.

Lieben Gruß

Reinibert

As I've no idea what they are I'd say I'm not using them, but I am getting a regular 'no network' message when starting Qute2 UPnP wirelessly in the bedroom (from the RCOM) It takes upwards of a minute to re-find the network and restore the library, then plays like a dream until it's left for half a day say. I might see if I can stop the NAS going into sleep mode and see if that changes anything. Currently n-Stream/SuperUniti seems to have no glitches. 

Simon,

I have a very similar combination (NAS and NDX connected wired to Airport Extreme, Ipad 1 connecting wirelessly, but to a different wireless AP than the Extreme).

In normal use I don't seem to have a problem...  However, when I first upgraded to the latest firmware, I did a complete rebuild of the UPNP server [Long story - not really related].  I cleared all the caches on NStream and did a complete reload of art etc.  While that was happening, Nstream seemed to lose connection, and failing to find the NDX/reconnect. (It looked like it might still have the connection to the NAS....) This was at the same time as wifi transmission rates dropped to single figures.  [It was the first thing I looked at - I have been here before with bulk uploads to the NAS - it also holds my picture archive.]

At the time I thought "Oh dear, that doesn't augur well" but it hasn't recurred in normal use, including some fairly large corrections to the library, and quite a bit of listening.  I'm hoping it was a glitch, but perhaps seek2time has made the whole system more sensitive to comms delays...

Hi hafler3o, the issue looks like it might be Apple related in terms of some interaction with the new version of Nstream with certain Apple software and other hardware:  AirportExpress is an Apple wifi adapter (amongst other things) that supports streaming services like Apple AirPlay and uPNP. The iOS 5.1.1 is the Apple operating system in the iPad. This is the  latest version that the iPad 1 can use which is what I have. 

Simon

PS- Reinibert, you say gapless is working reliably? What upnp server software are you using?

Slioch, yes when it next rains.. I might have a sneak at the Naim seek2time implementation to see which way they do it... I'd be suprised if it in itself causes these discovery or connectivity issues though.

I had the Same issues with nd5xs. German Support told me, Turn Off the streamer and unconect the powerline. This will be Reset and initial the LAN Board . 

I did it. Done , Perfect