From: Romain B. <to...@ra...> - 2011-02-02 14:57:43
|
Hi all ! Maybe we could first add a script that cuts only local files.. I have one already ready that could fit for the next stable release and we could think about changing the protocol resolution stuff later in the dev cycle.. Romain On Wed, Feb 2, 2011 at 4:06 AM, David Baelde <dav...@en...> wrote: > Hi Peter, > > Thanks for sharing your script. It had escaped my mind that this was > useful to deal with relatively precise scheduling. This shows that > there are several uses of cutting files, hence not necessarily a > single solution. > > On Mon, Jan 31, 2011 at 11:35 PM, Peter Retep <pet...@gm...> wrote: >> For scheduling with absolute start and end time, I am not sure if it makes >> sense to call scripts like this from inside liquidsoap, because it could be >> run outside just before starting liquidsoap or triggered by the external >> scheduler. > > Running it outside makes sense. One thing, though, is the management > of temporary files. Your script creates a temporary file where the cut > song is stored. Then it is passed to liquidsoap, which plays it. But > who deletes your temporary file? > > It would be nice if your script could be hooked into liquidsoap using > add_protocol. Then liquidsoap could know that the resulting file is > temporary, and delete it after playing. > >>> (no point detailing it here) >> Where else? > > I meant, no point in that general mail, but of course this list is the > right place. Now that I've started discussing protocols and temporary > files, I can state the technical problem Romain and I faced. > > It's easy to add a protocol using a script similar to yours so that > "cut:<params>:FILE" results in a new temporary file cut as expected. > However, this would only work with local files, whereas people would > naturally want to write things like > "cut:<param>:http://blah.org/file.mp3". The problem is that our > request resolution algorithm doesn't allow one protocol (cut) to act > on the result of another (http), but only allows one protocol (e.g. > database lookup via a scheduler) to give back another request > involving another protocol (e.g. http). > > We didn't manage to settle on a pleasant solution. As you can see it's > not so bad because most people wouldn't care about the cut protocol > working on remote files. > > Cheers, > -- > David > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Savonet-users mailing list > Sav...@li... > https://lists.sourceforge.net/lists/listinfo/savonet-users > -- They try to fool the black population, By telling them that Jah Jah Dead. But I&I know that... Jah no dead! |