>A socket disconnect is what you get at the end of a podcast. > Really? I thought all podcasts were episodes (files) contained within xml markup, and file length information was always available. I don't use Squeezebox Server for Podcasts, as Squeezebox Server is way too basic for podcasts. I use other apps, but all other apps show download progress for all podcasts, eg. iTunes, wTicker, GetRight. i.e. I have 60 podcasts (and 927 unlistened episodes) in iTunes - all of which I believe showed a download progress.
>Maybe we could assume that if we do not know the length (duration), and >it is not seekable, then it must be live. But there would still be a >subset of podcasts (or podcast-like streams) where this solution would >end up repeating the podcast indefinitely. I think it would be safe to assume more people will be playing internet radio streams than podcasts with no length information. Not reconnecting to a radio station is more annoying than occasionally repeating a podcast that has naturally ended. If this really is a problem (not knowing if it is the end of a file or a disconnect in a stream), could it detect whether the last few samples were quiet? Most podcasts will have some lead-out silence? Having said that, radio stations that disconnect could be in the middle of a small period of silence too, so maybe it's a bad idea to try to be too clever. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
