Does the control point need to be turned on allways??

[simoncn]

(03-12-2012 08:43)Rairwave Wrote:  Happy with with the functionality so far with Minimserver. Like it a lot but there is one major problem that stops me from actually using it.

I have a Linn DS upnp renderer, and ipad with kinksy, chorusds and plugplayer as upnp control point and a synology nas with synology media server and minimserver installed together.

When I start with a clear linn ds (so no music assigned) and use kinsky and the synology media server, music plays fine as usual. No problems.

When I start with a clear linn ds (so no music assigned) and use kinksy and the minimserver, music loads and starts but after around 20 to 40 seconds the music stops. On the Linn DS I see a turning hourglass.

I have no idea why this happens but I am getting the impression that the control point needs to be allways running. Because when I keep 'playing' with the control point (adding music for example) the music keeps playing as well. But when the control point (ipad or ipod) goes to sleep, the music stops (turning hourglass).
Can somebody shed a light on this?
Does it have something to do with the 'dynamic' playlist functionality of minimserver? Or do I have a different problem?

When you start playing a track, the DS streams the music directly from MinimServer on the Synology, without the control point being involved. If the DS stops playing and displays an hourglass, this means that the DS has lost contact with the Synology and is no longer receiving the network stream.

Do you have some kind of power-saving setting enabled on the Synology to spin down the disks or enter sleep mode? It sounds like the Synology may be doing this while MinimServer is sending data to the DS. When you play with the control point, you're probably doing something to the Synology that keeps it awake. Also, the built-in media server probably has some internal way to tell the Synology that it's running and prevent the Synology from entering sleep mode. Please try disabling spindown/sleep mode on the Synology to see if that solves the problem.