Hi devs,

I think I'm finally over with that big change in Lang that was needed
to use the new liquidsoap as before, potentially loading several big
scripts. I also wrote a bit of doc on the one new thing that users
need to know: encoding formats. Before asking courageous people to
come back to playing with our SVN, I thought I'd rather prepare here a
list of what is still not working well, and perhaps what we want to
fix before user experiment with the new version.

(1) Type and type errors are harder to read than before.
  I'll have to do better for 1.0 and even before that, but it can wait a bit.

(2) Lots of operators don't support video.
  This can wait, it's strictly better than before already.

(3) input.http/harbor are purely audio.
  This is a bit of a similar case as before, but we might want to work
on this one faster.

(4) No more external encoders for outputs.
  Not too hard to do, but not done yet.

(5) We still need to explicitly use audio_to_stereo and such to get
rid of variable channel numbers.
  I don't think anybody will want to use the current, raw single(),
playlist(), etc. We should rename them to single.variable() maybe, and
create wrappers like single(), single.video()?

(6) Operators might not have the right type.
  There are alternative policies in choosing the type of various
operators. We can aim for the most general, but a more restrictive
might sometimes make sense. This has to wait: it is only by using more
liquidsoap that we'll figure out which scheme is the most comfortable.
The goal is to get liquidsoap to infer the right content types with
the most natural scripts.

(7) Video resampling not supported.
  As a result you can only play videos of one samplerate (24 by
default, but you can set it using frame.video.samplerate).

(8) Liquidsoap goes crazy sometimes.
  Especially, I think it goes into almost-infinite loops when trying
to decode requests that don't fit the content type. For example, it
happens all the time with a video of a bad samplerate.

Do you see anything else?

I feel that (5) should be addressed before an announce, and if
possible also (7) and (8).

Cheers,
-- 
David

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Savonet-devl mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-devl

Répondre à