Hacker Guide/VLM Internals - Revision history

DoesItReallyMatter: +{{Back to|Hacker Guide}}

2019-04-17T06:36:23Z

+{{Back to|Hacker Guide}}

← Older revision		Revision as of 06:36, 17 April 2019
Line 1:		Line 1:
			{{Back to\|Hacker Guide}}
	==Introduction==		==Introduction==
	VideoLAN Manager is a small media manager designed to control multiple streams with only one instance of VLC. It allows multiple streaming and video on demand (VoD). VLM can be controlled through the telnet and http interfaces of VLC as described in [[Documentation:Streaming_HowTo/VLM]].		VideoLAN Manager is a small media manager designed to control multiple streams with only one instance of VLC. It allows multiple streaming and video on demand (VoD). VLM can be controlled through the telnet and http interfaces of VLC as described in [[Documentation:Streaming_HowTo/VLM]].

EPirat: /* Thread Creation */

2017-01-23T19:37:36Z

Thread Creation

← Older revision		Revision as of 19:37, 23 January 2017
Line 50:		Line 50:
	==Thread Creation==		==Thread Creation==

	VLM is a complex subsystem within VLC. When VLM is initialized, when a media is created ~~etc...~~, threads are created to handle these tasks. This section will describe the thread model used by VLM.		VLM is a complex subsystem within VLC. When VLM is initialized, when a media is created etc…, threads are created to handle these tasks. This section will describe the thread model used by VLM.

	When new instance of VLM is created by the ~~'''''~~__vlm_New()~~'''''~~ function, a management thread is created which has as its start function ~~'''''~~Manage()~~'''''~~ residing in ~~'''''~~src/input/vlm.c~~'''''~~. This takes care of scheduling, as well as destruction of dead input objects.		When new instance of VLM is created by the <code>__vlm_New()</code> function, a management thread is created which has as its start function <code>Manage()</code> residing in <tt>src/input/vlm.c</tt>. This takes care of scheduling, as well as destruction of dead input objects.

	when a new vod media is added to VLM, an input thread is created with ~~'''''~~Run()~~'''''~~ as its start function. This thread takes care of all streaming for that media.		when a new vod media is added to VLM, an input thread is created with <code>Run()</code> as its start function. This thread takes care of all streaming for that media.

	If a broadcast media is added, it needs to be played. When The libvlc function ~~'''''~~libvlc_vlm_play_media()~~'''''~~ is called, an instance of the broadcast media is created as well as an input thread with ~~'''''~~Run()~~'''''~~ as its start function. This thread takes care of all streaming for the broadcast instance by calling appropriate demux, codec, and sout modules.		If a broadcast media is added, it needs to be played. When The libvlc function <code>libvlc_vlm_play_media()</code> is called, an instance of the broadcast media is created as well as an input thread with <code>Run()</code> as its start function. This thread takes care of all streaming for the broadcast instance by calling appropriate demux, codec, and sout modules.

	{{Hacker_Guide}}		{{Hacker_Guide}}

EPirat: /* Control */

2017-01-23T19:36:34Z

Control

← Older revision		Revision as of 19:36, 23 January 2017
Line 46:		Line 46:
	==Control==		==Control==

	Once VLM is initialized, there needs to be some way to control it, such as adding medias, starting and stopping a media instance, etc... The '''''vlm_Control()''''' function is used for this purpose. This allows all VLM commands to be issued through one common interface, and it takes care of locking issues. By executing '''''vlm_Control()''''' with the proper command code, such as '''''VLM_ADD_MEDIA''''', and a variable argument list, any VLM command can be executed without the need to understand the lower level details. This allows for easily wrapping the VLM code to be used by many interfaces. '''''vlm_Control()''''' can be found in ~~'''''~~src/input/vlm.c~~'''''~~. The list of VLM command codes can be found in the enumerated type '''''vlm_query_e''''' in the file ~~'''''~~include/vlc_vlm.h~~'''''~~.		Once VLM is initialized, there needs to be some way to control it, such as adding medias, starting and stopping a media instance, etc... The <code>'''vlm_Control()'''</code> function is used for this purpose. This allows all VLM commands to be issued through one common interface, and it takes care of locking issues. By executing <code>'''vlm_Control()'''</code> with the proper command code, such as <code>'''VLM_ADD_MEDIA'''</code>, and a variable argument list, any VLM command can be executed without the need to understand the lower level details. This allows for easily wrapping the VLM code to be used by many interfaces. <code>'''vlm_Control()'''</code> can be found in <tt>src/input/vlm.c</tt>. The list of VLM command codes can be found in the enumerated type <code>'''vlm_query_e'''</code> in the file <tt>include/vlc_vlm.h</tt>.


	==Thread Creation==		==Thread Creation==

EPirat: /* Initializing VLM and Adding Medias */

2017-01-23T19:34:52Z

Initializing VLM and Adding Medias

← Older revision		Revision as of 19:34, 23 January 2017
Line 40:		Line 40:
	==Initializing VLM and Adding Medias==		==Initializing VLM and Adding Medias==

	Since VLM is a part of libvlc, I will describe initialization of VLM with respect to libvlc. If we want to use VLM we are probably going to have at least one media. Therefore we can use the libvlc functions '''''libvlc_vlm_add_broadcast()''''' or '''''libvlc_vlm_add_vod()''''' to instantiate and initialize VLM. Each one of these functions checks to see if a VLM instance exists. If it does not, the function creates a '''''vlm_t''''' instance and creates and adds either a broadcast or vod media to the '''''vlm_t''''' instance. If the media is of type vod, then a separate '''''vod_media_t''''' is created and linked to the media of type '''''vlm_media_sys_t''''' and a vod server of type '''''vod_t''''' is created and linked to the '''''vlm_t''''' instance.		Since VLM is a part of libvlc, I will describe initialization of VLM with respect to libvlc. If we want to use VLM we are probably going to have at least one media. Therefore we can use the libvlc functions <code>'''libvlc_vlm_add_broadcast()'''</code> or <code>'''libvlc_vlm_add_vod()'''</code> to instantiate and initialize VLM. Each one of these functions checks to see if a VLM instance exists. If it does not, the function creates a <code>'''vlm_t'''</code> instance and creates and adds either a broadcast or vod media to the <code>'''vlm_t'''</code> instance. If the media is of type vod, then a separate <code>'''vod_media_t'''</code> is created and linked to the media of type <code>'''vlm_media_sys_t'''</code> and a vod server of type <code>'''vod_t'''</code> is created and linked to the <code>'''vlm_t'''</code> instance.

	Note also, that the VLM instance is attached to the libvlc instance as a singleton, therefore allowing only one VLM instance per libvlc instance. Both '''''libvlc_vlm_add_broadcast()''''' and '''''libvlc_vlm_add_vod()''''' wrap around the '''''VLM()''''' macro which wraps around '''''__vlm_New()''''' which actually does the instantiation, initialization, and binding of the VLM instance to the libvlc instance. These functions are found in the ~~'''''~~src/control/vlm.c~~'''''~~. ~~'''''~~__vlm_New()~~'''''~~ is found in ~~'''''~~src/input/vlm.c~~'''''~~.		Note also, that the VLM instance is attached to the libvlc instance as a singleton, therefore allowing only one VLM instance per libvlc instance. Both <code>'''libvlc_vlm_add_broadcast()'''</code> and <code>'''libvlc_vlm_add_vod()'''</code> wrap around the <code>'''VLM()'''</code> macro which wraps around <code>'''__vlm_New()'''</code> which actually does the instantiation, initialization, and binding of the VLM instance to the libvlc instance. These functions are found in the <tt>src/control/vlm.c</tt>. <code>__vlm_New()</code> is found in <tt>src/input/vlm.c</tt>.

	==Control==		==Control==

EPirat: /* Medias and Instances */

2017-01-23T19:31:27Z

Medias and Instances

← Older revision		Revision as of 19:31, 23 January 2017
Line 22:		Line 22:
	The configuration structure is of type <code>'''vlm_media_t'''</code> (a misnomer due to historical reasons) and contains the name of the media, as well as its type and a host of other details. It is defined in <tt>src/input/vlm_internal.h</tt> also.		The configuration structure is of type <code>'''vlm_media_t'''</code> (a misnomer due to historical reasons) and contains the name of the media, as well as its type and a host of other details. It is defined in <tt>src/input/vlm_internal.h</tt> also.

	A media instance is represented by the structure <code>vlm_media_instance_sys_t</code> defined in <tt>src/input/vlm_internal.h</tt> also. This structure contains a playlist index as well as the current input thread and output stream instance. Mulitple media instances can exist for each media.		A media instance is represented by the structure <code>'''vlm_media_instance_sys_t'''</code> defined in <tt>src/input/vlm_internal.h</tt> also. This structure contains a playlist index as well as the current input thread and output stream instance. Mulitple media instances can exist for each media.

	Each VOD server is represented by the struct <code>vod_t</code>. This structure contains a pointer to the module that will be loaded to help the vod server, as well as a pointer to an RTSP server. It also contains several function pointers to help create and delete vod medias of type <code>vod_media_t</code>. Each <code>vod_media_t</code> is actually referenced by a <code>vlm_media_sys_t</code> if that media is of vod type. <code>vod_t</code> is defined in <tt>include/vlc_vod.h</tt> and <code>vod_media_t</code> is defined in <tt>modules/misc/rtsp.c</tt>.		Each VOD server is represented by the struct <code>'''vod_t'''</code>. This structure contains a pointer to the module that will be loaded to help the vod server, as well as a pointer to an RTSP server. It also contains several function pointers to help create and delete vod medias of type <code>vod_media_t</code>. Each <code>vod_media_t</code> is actually referenced by a <code>vlm_media_sys_t</code> if that media is of vod type. <code>vod_t</code> is defined in <tt>include/vlc_vod.h</tt> and <code>vod_media_t</code> is defined in <tt>modules/misc/rtsp.c</tt>.

	The layout of the main vlm structures hierarchically looks like this:		The layout of the main vlm structures hierarchically looks like this:

EPirat: /* Medias and Instances */

2017-01-23T19:30:45Z

Medias and Instances

← Older revision		Revision as of 19:30, 23 January 2017
Line 13:		Line 13:

	There are two types of medias:		There are two types of medias:
	*'''vod~~'''~~: A vod media is commonly used for Video on Demand. It will be launched only if a vod client asks for it.		; vod
	*'''broadcast~~'''~~: A broadcast media is very close to a TV program or channel. It is launched, stopped or paused by the administrator and may be repeated several times. The client has no control over this media.		: A vod media is commonly used for Video on Demand. It will be launched only if a vod client asks for it.
			; broadcast
			: A broadcast media is very close to a TV program or channel. It is launched, stopped or paused by the administrator and may be repeated several times. The client has no control over this media.

	A media is represented by the structure '''''vlm_media_sys_t''''' defined in ~~'''''~~src/input/vlm_internal.h~~'''''~~. Each ~~'''''~~vlm_media_sys_t~~'''''~~ contains a configuration structure, a list of instances of the media, as well as a structure representing a vod server which is initialized only if the media is of type vod.		A media is represented by the structure <code>'''vlm_media_sys_t'''</code> defined in <tt>src/input/vlm_internal.h</tt>. Each <code>vlm_media_sys_t</code> contains a configuration structure, a list of instances of the media, as well as a structure representing a vod server which is initialized only if the media is of type vod.

	The configuration structure is of type '''''vlm_media_t''''' (a misnomer due to historical reasons) and contains the name of the media, as well as its type and a host of other details. It is defined in ~~'''''~~src/input/vlm_internal.h~~'''''~~ also.		The configuration structure is of type <code>'''vlm_media_t'''</code> (a misnomer due to historical reasons) and contains the name of the media, as well as its type and a host of other details. It is defined in <tt>src/input/vlm_internal.h</tt> also.

	A media instance is represented by the structure ~~'''''~~vlm_media_instance_sys_t~~'''''~~ defined in ~~'''''~~src/input/vlm_internal.h~~'''''~~ also. This structure contains a playlist index as well as the current input thread and output stream instance. Mulitple media instances can exist for each media.		A media instance is represented by the structure <code>vlm_media_instance_sys_t</code> defined in <tt>src/input/vlm_internal.h</tt> also. This structure contains a playlist index as well as the current input thread and output stream instance. Mulitple media instances can exist for each media.

	Each VOD server is represented by the struct ~~'''''~~vod_t~~'''''~~. This structure contains a pointer to the module that will be loaded to help the vod server, as well as a pointer to an RTSP server. It also contains several function pointers to help create and delete vod medias of type ~~'''''~~vod_media_t~~'''''~~. Each ~~'''''~~vod_media_t~~'''''~~ is actually referenced by a ~~'''''~~vlm_media_sys_t~~'''''~~ if that media is of vod type. ~~'''''~~vod_t~~'''''~~ is defined in ~~'''''~~include/vlc_vod.h~~'''''~~ and ~~'''''~~vod_media_t~~'''''~~ is defined in ~~'''''~~modules/misc/rtsp.c~~'''''~~		Each VOD server is represented by the struct <code>vod_t</code>. This structure contains a pointer to the module that will be loaded to help the vod server, as well as a pointer to an RTSP server. It also contains several function pointers to help create and delete vod medias of type <code>vod_media_t</code>. Each <code>vod_media_t</code> is actually referenced by a <code>vlm_media_sys_t</code> if that media is of vod type. <code>vod_t</code> is defined in <tt>include/vlc_vod.h</tt> and <code>vod_media_t</code> is defined in <tt>modules/misc/rtsp.c</tt>.

	The layout of the main vlm structures hierarchically looks like this:		The layout of the main vlm structures hierarchically looks like this:

EPirat: /* vlm_t */

2017-01-23T19:26:34Z

vlm_t

← Older revision		Revision as of 19:26, 23 January 2017
Line 6:		Line 6:
	==vlm_t==		==vlm_t==

	In a running instance of VLC or libvlc only 1 instance of VLM can be running. This instance of VLM is represented by <code>struct vlm_t</code> as defined in <tt>src/input/vlm_internal.h</tt>. <code>vlm_t</code> contains a list of Medias, Schedules and vod servers, as well as a lock for the data structure, and a unique id. In essence, the <code>vlm_t</code> data structure is the global container for all VLM related data.		In a running instance of VLC or libvlc only 1 instance of VLM can be running. This instance of VLM is represented by <code>'''struct vlm_t'''</code> as defined in <tt>src/input/vlm_internal.h</tt>. <code>vlm_t</code> contains a list of Medias, Schedules and vod servers, as well as a lock for the data structure, and a unique id. In essence, the <code>vlm_t</code> data structure is the global container for all VLM related data.

	==Medias and Instances==		==Medias and Instances==

EPirat: /* vlm_t */

2017-01-23T19:26:09Z

vlm_t

← Older revision		Revision as of 19:26, 23 January 2017
Line 6:		Line 6:
	==vlm_t==		==vlm_t==

	In a running instance of VLC or libvlc only 1 instance of VLM can be running. This instance of VLM is represented by ~~'''''~~struct vlm_t~~'''''~~ as defined in ~~'''''~~src/input/vlm_internal.h~~'''''~~. ~~'''''~~vlm_t~~'''''~~ contains a list of Medias, Schedules and vod servers, as well as a lock for the data structure, and a unique id. In essence, the ~~'''''~~vlm_t~~'''''~~ data structure is the global container for all VLM related data.		In a running instance of VLC or libvlc only 1 instance of VLM can be running. This instance of VLM is represented by <code>struct vlm_t</code> as defined in <tt>src/input/vlm_internal.h</tt>. <code>vlm_t</code> contains a list of Medias, Schedules and vod servers, as well as a lock for the data structure, and a unique id. In essence, the <code>vlm_t</code> data structure is the global container for all VLM related data.

	==Medias and Instances==		==Medias and Instances==

Corbax: /* Thread Creation */

2013-11-14T17:29:11Z

Thread Creation

← Older revision		Revision as of 17:29, 14 November 2013
Line 57:		Line 57:
	If a broadcast media is added, it needs to be played. When The libvlc function '''''libvlc_vlm_play_media()''''' is called, an instance of the broadcast media is created as well as an input thread with '''''Run()''''' as its start function. This thread takes care of all streaming for the broadcast instance by calling appropriate demux, codec, and sout modules.		If a broadcast media is added, it needs to be played. When The libvlc function '''''libvlc_vlm_play_media()''''' is called, an instance of the broadcast media is created as well as an input thread with '''''Run()''''' as its start function. This thread takes care of all streaming for the broadcast instance by calling appropriate demux, codec, and sout modules.

	~~[[Category:Coding]]~~
	{{Hacker_Guide}}		{{Hacker_Guide}}

Corbax at 16:22, 30 October 2013

2013-10-30T16:22:57Z

← Older revision		Revision as of 16:22, 30 October 2013
Line 58:		Line 58:

	[[Category:Coding]]		[[Category:Coding]]
	{{~~Documentation~~}}		{{Hacker_Guide}}