philippe_44 wrote: > I did but unfortunately it seems to enter i to the same category of > devices having a specific/narrow implementation of nextURI - they need > more than 10s to implement it which is wrong, IMHO. Nothing in the > standard says that the nextURI must arrive before all data of currentURI > has been sent or X seconds before end of currentURI
If this refers to upmpdcli, this is I think not the case. SetNextAVTransportURI should just happen before the current track stops. Actually the best time to send it is right after the track starts, but as long as it comes before playing stops, upmpdcli will use it. Of course, if it comes so late that the mpd buffer empties before the next track data can begin streaming, playing can't be continuous. This would depend on the details of mpd buffering, but I would not be too surprised if setnext needed to happen a couple seconds before the end of track for things to be seamless. ------------------------------------------------------------------------ medoc's Profile: http://forums.slimdevices.com/member.php?userid=72014 View this thread: http://forums.slimdevices.com/showthread.php?t=103728 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
