Asset Stops being recongnized on audio device

[alk630]

I have been using a registered version of Asset 4.1 on a Windows 7 x64 machine for around one year, with default settings on an ARCAM Solo Neo.

I Originally messed around on a laptop to set Asset up, but since then changed to a permanent server with around 18,000 albums all in FLAC format.

The first problem is that the hi-fi still sees the old Asset DLNA name when I select <Net Media>. I have since changed this name to a different one, but the old name persists in addition to the new one, even past a factory reset on both the ARCAM and my wireless router. Arcam have denied this is their problem and said a factory reset should have cleared the old DLNA name.

Everything seems to work perfectly for days, then suddenly I am unable to see the working Asset name on my hi-fi, but can still see the old Asset name. The only way I have found to resolve this is to reboot the server with Assett installed on it, whereupon both Asset names are visible on the hi-fi again. I would like to know if there are any reasonable steps I can take to find out why this frustrating problem is occurring. I only have Microsoft Security Essentials and the standard Microsoft Firewall Installed.

Can you give me some pointers on where I should be looking for to pinpoint the cause of this problem please?

[Spoon]

Re: Asset Stops being recongnized on audio device

You would have to try a different control point (the arcam is the player and control point) to determine if asset is still running. There are a few control points for ipads, etc, such as PlugPlayer.

Also if you shut down the computer with Asset on, and the player still shows the old name after 1 hour, it cannot possibly be Asset advertising the old name as it is not running.

[alk630]

Re: Asset Stops being recongnized on audio device

Thanks Spoon. I took up the issue of the persistent old server name up with Arcam who recommended a factory reset, which failed to cure the problem - a strange, but minor quirk.

I'll get back to the issue of Asset appearing to stop running when the issue happens again. As mentioned, it only happens after a few days of running.