In the convert.conf - does spotty read data from an URL or process a byte stream from LMS stdin so that LMS gets the data initially.
It's reading bytes from the spotty helper, which would download from a remote source. But as sle118 mentioned: it's track based, not a single stream.
Just by looking at the convert.conf file I'm guessing $URL$ is a spotify URL which is used to get data but I don't recognise what $CACHE$ is about.
$CACHE$ is just the cache folder where spotty would find temporary files, credentials etc.
Remote stream were expected to work either as * live - infinite stream which runs in realtime so there is very little data to buffer - if input connection is marginal and loses time sending data then rebuffering.
That's not the spotty case.
* "listen again"/podcast - URL will supply as much data as possible so that player will have all the data for minutes before it is finished playback - so watchdog timeouts occurs after all data is in player.
That's closer to Spotty's behaviour.
I feel to trigger watchdog -spotty is behaving like multiple "live" connections with gaps or some other variation.
Spotty would stream every track of a playlist or album individually. I don't know how that "live" behaviour would be controlled...
-- Michael _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
