I want to generate dynamic playlists from user specifications; these will be infinite lists of tracks, to be played until something else is requested. I have the generator already...
What's the best way of presenting this information? Feeding one track URI at a time to a playlist file and reading that with playlist() doesn't seem to work because, even with reload=1 and reload_mode="rounds", it doesn't seem to get re-read every time it's changed - so tracks get repeated. Would it make more sense to feed in say ten tracks at a time? But then how would the system know when to refresh that list? (The brute-force option would be to generate a thousand or more tracks, i.e. more than will be used in a single play session. But I'd prefer to be elegant about it and generate tracks as they're required.) Even if I do use the thousand-or-more-tracks approach, how can I get the playlist() function to recognise when the playlist is no longer available? Making the playlist URI return 404, or returning an empty playlist, both cause it to retain the last playlist it had - whereas I want it to fail, and trigger the next fallback(). Is playlist() the right function to use for this? ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
