Re: [Savonet-users] Liquidsoap: Playlist stops and streams silence.

[Romain B. <to...@ra...>]

Le Monday 23 June 2008 16:46:01 1394542, vous avez écrit :
> Hi!

	Hi !

> I've encountered a problem with my playlists:
(...)
> >From my understanding, those playlist should never stop playing.
>
> Once the playlist reaches its end, it should start from the top,
> or from any playlist position, since it's randomized.
> Yet, the playlist simply reaches silence, and streams nothing.

Yes this indeed a known bug, we've been discussing it with another user.

> This is how the playlists are merged with each other:
>
> # merging jingles with music
> auto = random( weights = [1, 2],
>                [jingles, pl] )
>
> The resulting stream, is often just silence.
>
> However, Ive got another fallback running:
>
> # switching to DJ mountpoint with fading
> full = fallback( track_sensitive = false,
>                  transitions = [ cfade, cfade, sfade ],
>                  [input.http("http://localhost:8010/"),
> input.http("http://localhost:8000/stream.ogg"), auto]
>
> Now, when the stream is silent, a DJ can connect to any of those
> mountpoints, and disconnect after a few seconds.
> After that, the playlist is running again. I don't know how.

Strange, and interesting to get to know where the issue is..

> Anyway, in the telnet console, I get the following error, after
> issuing "playlist(dot)lst.next":
>
> ERROR: Invalid_argument("Array.make")
> END
>
> But the playlist is still running.

Yes, this is fixed in the latest SVN trunk/

> Could anyone help me with those problems?

I'm willing to help you but you'll need to help me :)
First, can you test with a recent svn ? I have looked at the source and fixed 
several other things, suchs as Array.make error, so it would be a good 
starting point.

If you can reproduce the issue quickly, it would be good to have more logs, so 
you could use the following setting:
  set("log.level",5)
and store the logs.

Also, in a second try, you could add, after the log.level setting, the 
following:
  set("scheduler.log",true)

This will produce a huge log....


I will try to reproduce here..

Romain