[streaming] Re: vls vs. vlc

[Gildas Bazin]

On Thursday 22 May 2003 22:48, Larry Kelly wrote:
>
>  But, my point is
> that would it not help both sets of developers to have some standard 
common
> interfaces for functions which would need to exist in both?  IE:  Both
> programs can be used to stream DVD's, and both programs can stream other
> MPEG2 and some MPEG1 files, etc.  It just sounds like a good mechanism for
> handling this would be to start with a good common input module, and work
> from there.
> 

Doing that would basically mean rewritting VLS into another VLC.

Both programs are very different internally. VLS has been designed from the 
ground up to stream MPEG files and only MPEG files. This is what makes VLS 
lightweight and "simple". This can for sure be an asset when you want to 
run a reliable server. Don't get me wrong VLC is very stable mainly because 
more people are working on it and testing it. But if you happen to find a 
bug in VLC you will have more problems understanding its complex 
architecture and solving it, while it will be _a lot_ simpler with VLS.

We also tried to share some code when possible. Look at the libdvbpsi and 
libdvdcss projects.

> 
>   An additional question -- has anyone looked at creating output code that
> would periodically inject the MPEG1 header info into an outgoing stream in 
a
> transparent fashion?  A number of MPEG1 files I have come up against do 
not
> contain periodic pieces of the header info, and therefore won't stream
> properly.  It seems like some sort of intelligent output code could solve
> this problem without having to change the original MPEG1 file.
> 

VLC handles this without any problems.

Regards,

--
Gildas
-- 
This is the streaming mailing-list, see http://www.videolan.org/streaming/
To unsubscribe, please read http://www.videolan.org/support/lists.html
If you are in trouble, please contact <postmaster at videolan.org>