Asset and n-stream

Posted by: meaculpa on 06 July 2012

I seem to keep having problems with n-stream recognising Asset.  You can select it, go to album       For example, and then select A, it then says connecting and goes back to the server list. I have tried restrating Asset but no joy.  I don't think it is an issue with Asset as Plug Player and e-lyric both recognise it ok and can play from it.

 

Does anybody have any idea's or has seen a similar issue?

 

Andrew

Posted on: 06 July 2012 by Chris Shorter
Originally Posted by meaculpa:

I seem to keep having problems with n-stream recognising Asset.  You can select it, go to album       For example, and then select A, it then says connecting and goes back to the server list. I have tried restrating Asset but no joy.  I don't think it is an issue with Asset as Plug Player and e-lyric both recognise it ok and can play from it.

 

Does anybody have any idea's or has seen a similar issue?

 

Andrew

I use Asset in conjunction with NStream very successfully. I have seen this problem maybe twice in six months and I resolved it with a full "Refresh All" rescan of the library. I think in both cases there had been some unusual event in the house like a power cut and all the devices hadn't really come up in the correct order.

 

Chris

Posted on: 07 July 2012 by Dungassin

I've seen this three times so far.  It's always been after a power cut, and I have curedit each time (after trying various things such as rebooting the NDX etc) by going into my Netgear N6000 router setup and just clicking APPLY without actually changing any of the router settings.

 

John

Posted on: 10 July 2012 by CharlieP

Macula,

Has it ever worked?  Does it fail to open stream only on certain files or all files?

Check the file format can is recognized by your streamer.  

Posted on: 11 July 2012 by JackRabbit

Do you use DHCP to dynamically allocate IP addresses? If so, I would strongly recommend making them static.

Posted on: 11 July 2012 by Simon-in-Suffolk

Andrew, to me it sounds like there might be an issue with the discovery protocol used by upnp. This uses something like broadcast frames (ie at the level below IP addresses). However this requires a good transparent network to work. Can you describe your LAN setup between the Nstream -> wireless -> switch / router -> Assett  -> switch / router -> Naim? 

If somewhere in that chain these special frames are being unreliably sent you could lose upnp connection as you describe. This happened to me, and it was my wifi access point that was not handling this broadcast/multicast data correctly. I swapped if for an Apple AirportExpress that specifically supports this data type (as used by both AirPlay and Upnp) and it then worked fine.

Also, do you leave asset switched on, or do you reguarly turn it off and on when you need it?

Simon

Posted on: 17 July 2012 by meaculpa

Hi all,

 

Thanks for the advice, but still a problem.

 

Simon,

 

I am worried, as it is not conventional!  N-stream on iPAD wirelessly connected to Apple Time Machine Router.  NDX is hard connected to a Apple AirPort Extreme which my NAS (WD Book with Twonky) is also hard wired into.  Into this Airport, as a third hard connection, is a ASUS Netbook running Asset.  This is all in the sitting room while the Time Machine is in the study hooked up to a iMAC running Parallels and dBPoweamp for ripping.  I am sure I have the Airport configured as a bridge correctly, so I am hoping it is not causing a problem by acting as a router in its own right?

 

It is intermittent, because if I re-install Asset and rescan it does work for a while before just looping round!

 

You may have an idea, but it may be because of the bridge setup and having it across two rooms.

 

A

 

Posted on: 17 July 2012 by Simon-in-Suffolk

Hi, it's hard to see what is happening, you might want todry a conventional switch connecting your NDX, Asset and wireless access point (Exteme)... One other idea is to check multicast is enabled on the airport extreme.

Simon