GitLab

Modified-and-...
Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

All our private context end in sys_t
Do the same for elementary stream specific context inside sout modules

Re-license almost all the streaming modules to LGPLv2.1+ with
authorization from their respective contributors

After access_output, this includes stream_out and mux.

The duplicate and rtp modules are not concerned by this relicensing
because of unreachable authors. Notably:
 - An L. Ber (dedd7cd2)
 - Andy chenee (5caa2bab)

Thanks to everyone for their help and answers in due time

http://msdn.microsoft.com/en-us/library/b0084kay(v=vs.80).aspx only
mentions the _ prefixed variable.

gcc will always define the _ prefixed variable, like Visual Studio.
The prefixless one is defined in some language standards, e.g. gnu99
but not c99.

The deadlock would occur when the VLM would stop an instance and detach
its RTP output, at the same time as an RTSP client would issue a VoD
command to the VLM.

Unfortunately this introduces a race condition where wrong RTP-Info can
be returned.

This is getting a bit lame

Modified-by: Rémi Denis-Courmont <remi@remlab.net>
Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>

Also prefix with vlc_ for namespace cleanliness.

This fixes a crash with VoD when all tracks were not set up

For VoD, the synchronization is bad, but accurate synchronization would
require at least changes in the core to add support for some kind of
"instant pausing" to the stream output. Synchronous calls to the VLM
shouldn't cause delay problems, no operation waits for the input.

Half of it is still unimplemented, so it's just sweeping under the
VLM rug

Based on keep-alive RTSP requests

RTSP doesn't toggle pause state, it sends unconditional PLAY/PAUSE
commands. Let the VLM handle it.

RTSP uses NPT in seconds, so don't convert for nothing...

Cleaner and better working solution for VoD than the bad hack that we
currently have. Instead of (badly) duplicating large portions of codes,
it reuses the existing RTSP stack and factorizes the RTP payload code,
and provides support for a number of ES not limited to one audio and one
video tracks, as well as for missing features in RTSP headers.

The VoD module is responsible for starting and running the RTSP stack.
When a VoD media instance is started, the VLM passes down media and
session parameters as variables to the RTP stream output object, that
uses them to hook back into the VoD code (and through it, into the RTSP
stack), to retrieve accurate, already set up parameters, and provide
playback data.