Hello, > > Main playlist uses mksafe [...] > > If main fails, moves to rescue but only play silence. Dont know > why > > If you wrap the main playlist with mksafe, you get an infallible > source. Indeed, mksafe() plays silence instead of failing. This is > probably not wanted: it's better to let the main playlist fail, and > have your fallback() handle the failure in a smart way.
It makes sense! > This is what you do in these two cases: > > Main playlist is fallible > > Rescue playlist is mksafe = creates the mount point, moves to the > rescue playlist when main is deleted empty or corrupted. ALL OK > > > Main playlist is fallible > > Rescue playlist uses playlist.safe = creates the mount point, > moves to the rescue playlist when main is deleted empty or > corrupted. ALL OK > In both cases you need an infallible rescue source. If you get it > using playlist.safe() that's nice, but liquidsoap refuses to start > if the rescue playlist is empty or invalid. If you get it by using > mksafe() around a normal playlist, that works too, but it means > that you'll get silence when the rescue fails. In this last solution I'm not sure what the interest is compared to simply having a single > playlist wrapped in a mksafe(). I implemented this feature, because the playlists are FTPed by other people. I have a script in the crontab that every morning check if there is a playlist for the day, if so, recreates the main playlist, and restart liquidsoap. If the playlist admins make a mistake, like FTP and invalid playlist, I want something that plays music when the liquidsoap gets restarted. Thats why I implemented a static rescue playlist with audio files that I personally checked. Altough nobody can delete my rescue playlist, I used mksafe just in case something bad happen with one or more audio files (that are local). Well... I am so paranoid ;) Thanks for your time and help Jorge ------------------------------------- Saca tu propia cuenta de email gratis en Colombia entrando a http://mail.conexcol.com
