n-Serve regularly loses control of UnitiServe

n-Serve has been really stable on my iPhone (it's a 4S).  It's never failed to "see" my uServe. 

Have you tried uninstalling and reinstalling n-Serve? That's where I'd start.

PS -- which "update" are you referring to?

Thanks for the input Bart, I have re-installed n-Serve a couple of times. It's app v.2.5, the current one which came along earlier in the year.

What does nServe actually do? Can you not control the system, choose music etc, just by using nStream?

I run a Unitiserve on its own and use the digital output so n-Serve controls the Unitiserve.

If you have a Naim streamer/player (ND%XS, NDX, NDS) and a uServe, you do use n-Stream to control everything.  But n-Serve is needed when it's used as a player (which I used to do before buying my NDS).  I still sometimes fire up n-Serve when the NDS does not yet "see" new music or changed meta data, and I want to see if the server has indexed it yet.

In the order of what it could be, I usually would rank such problems as more likely caused by the iDevice and/or the installation of n-Serve, or the home network, and less likely caused by the server itself.

Excellent, that's the response I was hoping for. Thanks.

Everything works fine if I control it with n-Serve on a Macbook so it is either the software or the iPod, I would not imagine many others use this particular Touch to run n-Serve.

IPod Touch 3 user here !

Our UnitiServe sees use in two houses, with nServe controlled alternately by an iPod Touch 3 or an iPad 3. In my wife's house, either device works flawlessly to control the UnitiServe. When the UnitiServe is moved to my house the iPad is usually the one to have difficulties seeing the UnitiServe. The iPod always works... The difference between the two houses is the router... so router setup may be the first place to look. Also, you could download inSSIDer (a free app) onto your Macbook, to visualize wi-fi networks in real time and check for any glaring issues (competition on channels used, field strength, etc).

Perhaps Simon can chime in...

Jan

inSSIDer is $4.99 here but I will invest in it

I am somewherebetween barringtonlevi and bart. My iPhone 4s sometimes loses the Unitiserve, perhaps once every 2 weeks. Running the latest version of n-serve. Certainly not flawless, but also not unreliable enough to worry about.  Interestingly n-serve on my iPad has never lost control, not even once. As the Americans say, Go Figure......

Cheers, Paul 

Normally I use dtc, but yesterday I used n-serve to play tracks from a long playlist I have created. Worked with no problems. This morning I tried to access the playlist again, just to be told that this was not possible in offline mode.

One interesting observation. If I activate autoconnection, it will search for a server but not find any. When I do not use autoconnection my server ip address is found, and with stay connected on this should work, wich it does not do  all the time. I have a similar problem with plugplayer, that used to work, so something mus thave changed in my setup. The n-serve has a fixed dhcp address.

Claus

I am experiencing what seems to be the same issue.  I also use an iPOD Touch.  After restarting the iPOD the nServe Software seems to be in control. However after a short while, it seems to lose track of what is playing. It will not list tracks on albums and requires a reboot.

For me the issues seems to date from the update to v1.6d. I am hanging out for v1.7 in the hope it will resolve the issue. Otherwise I may have to invest in an iPAD. My preference is for Windows so this will be a big step.

Simon,

the n-serve on my ipod4s is also playing up now- perhaps I didn't notice it much before because II usually use iPad. Now it regularly loses the connection, as per your post.

I am not even running the latest version of US firmware.  Think I am still on 1.6b. Decided not to bother updating after a few folks posted problems with the update, and with no obvious improvements in functionality.

Cheers, paul

It's good to hear that I'm not alone, SimonFM describes my problem precisely. Finger's crossed for 1.7