Playback in http and rtsp

"Erwan Gouyette" <[email protected]>
Newsgroups gmane.comp.multimedia.helix.devel
Message-ID <[email protected]>
Hi, I've been trying to understand how a "two streams in one source (Audio
and video)" playback is done with Helix DNA Client from any web server. 

 

****************************************************************************
*************

 

These are the different steps:

 

The Client parses the URL to know if it's a local or a network playback.

 

The Client loads the appropriate Network Service to abstract UDP/TCP.

 

Then it loads the File_System plug-in which creates a File_Object.

 

Local playback (case of HTTP)

 

Each packet buffered has a content type indicating the MIME type of the
stream (Audio or Video, and encoding format).

 

If he MIME can't be found, the client takes a look at the extension or uses
the recognizer.

 

Then it loads the File_Format plug-in (corresponding of both encoded audio
and video) which creates a FileFormatObject.

 

This FileFormatObject makes the File_Header, the Stream_Headers, and revises
the Stream_Packets_Headers according to the Stream_Headers.

 

Then the renderers are loaded and when the amount of data is sufficient, the
playback begins.

 

Network playback (case of RTSP)

 

The Client asks the server for RTSP DESCRIBE response which contains the SDP
with the number of streams, how they are encoded . 

 

Then it's the same as a local playback because the client has the MIME type.

 

****************************************************************************
*************

 

Please tell me that's OK. Thanks,

 

Erwan

 

PS: I wonder how many File_Format and FileFormatObject are used. One
File_Format plug-in is loaded but only one FileFormatObject is created,
isn't it? I wonder because MIME types of video and audio encoded at the same
format are different.

_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.