And by the end of the year (if possible), podradio (a webradio, I co-founded) will release the tool I developed, it's a Rails application (web app but many tasks are on system side).
Features : - manage multiples radios/channels - manage multiples users (system admins, radio admins, radio users (readonly), guest/listeners access (restricted readonly) - manage schedules (1 week repeating for now) - manage a library of programs - manage a library of music and playlists - manage which playlist is played at which time by default - APIs (music infos and cover via XML/PList/JSON) Voila. (Also : It might be open source) Giovanni Olivera a.k.a Pof Magicfingers Développeur iPhone, Web, et Mac OS Co-fondateur de podradio.fr http://pofmagicfingers.fr/ http://twitter.com/pofmagicfingers +33626956011 Le 28 juil. 2011 à 08:33, David Baelde <[email protected]> a écrit : > Hi, > > Brandon, your solution looks fine to me. You don't seem to have done > anything scary, so if the result sounds good to you, it's all good. > > On Wed, Jul 27, 2011 at 10:35 PM, Romain Beauxis <[email protected]> wrote: >> On this topic, I have heard very good comments on the way that airtime >> implements its scheduling. Maybe you may want to have a look there for >> more inspirations.. > > Airtime's solution was developped by Jonas Ohrstrom. As far as I > understand your solution relies on feeding liquidsoap one file at a > time and making sure liquidsoap doesn't try to prepare two files in > advance. If one file lasts two long you skip it and the correct one is > played. In Jonas' solution, a whole one-hour slot (they also have > fillers in case the scheduled files are too short) is fed to > liquidsoap, which may prepare several files in advance for extra > safety. I think this is the main difference. As a result they have a > more complex skipping mechanism (which they use only at the beginning > of the next hour is the past slot is running too long): they have to > skip all remaining items in the queue, but before doing so they want > to be sure that the files of the next hour have been prepared by > liquidsoap, so they feed a second queue in advance, and when time > comes switch to it and empty the other one. > > I feel like I'm missing some details and maybe some of the reasoning > behind this more complex system. If you're interested, you may be able > to find more info in savonet-users mails from Jonas, or in Airtime's > scripts. > > Cheers, > -- > David > > PS: By the way, after discussing that system with Jonas, and seeing > the frequent (but perhaps decreasingly frequent) questions about > scheduling, I wanted to write a tutorial on different systems with > increasingly complex specifications. But I never started it :\ > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Savonet-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/savonet-users ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
