Hacker Guide/libvlc - Revision history

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

2019-04-17T03:46:04Z

+{{Back to|Hacker Guide}}

← Older revision		Revision as of 03:46, 17 April 2019
Line 1:		Line 1:
			{{Back to\|Hacker Guide}}
	==Libvlc Startup==		==Libvlc Startup==

DoesItReallyMatter: Formatting consistency, wikilinks

2019-02-16T08:16:21Z

Formatting consistency, wikilinks

← Older revision		Revision as of 08:16, 16 February 2019
Line 2:		Line 2:

	===Introduction===		===Introduction===
	Libvlc represents the underlying API of ~~vlc~~. VLC itself is just a wrapper around libvlc. By utilizing libvlc developers can take advantage of all the complex functionalities of vlc. Libvlc is generated as a shared library and can be wrapped up with numerous interfaces, including both Python and Java bindings. This allows the end user to build applications around the vlc code base and take advantage of all the plugins available to vlc instead of writing everything from scratch.		[[Libvlc]] represents the underlying {{API}} of {{VLC}}. VLC itself is just a wrapper around libvlc. By utilizing libvlc developers can take advantage of all the complex functionalities of vlc. Libvlc is generated as a shared library and can be wrapped up with numerous interfaces, including both Python and Java bindings. This allows the end user to build applications around the vlc code base and take advantage of all the plugins available to vlc instead of writing everything from scratch.

	This document will explain how to get started using libvlc. It will step through the instantiation of a libvlc instance and explain the typical startup procedure of libvlc.		This document will explain how to get started using libvlc. It will step through the instantiation of a libvlc instance and explain the typical startup procedure of libvlc.
Line 8:		Line 8:
	===Libvlc Instantiation===		===Libvlc Instantiation===

	Libvlc is a singleton. For each application wrapped around libvlc, only one libvlc instance should be running. In order to create an instance of libvlc, you must call ~~'''''~~libvlc_new()~~'''''~~. This function initializes the thread system and allocates a libvlc instance. ~~'''''~~libvlc_new()~~'''''~~ resides in ~~'''''~~{{VLCSourceFile\|src/config/core.c}}~~'''''~~.		Libvlc is a singleton. For each application wrapped around libvlc, only one libvlc instance should be running. In order to create an instance of libvlc, you must call <code>libvlc_new()</code>. This function initializes the thread system and allocates a libvlc instance. <code>libvlc_new()</code> resides in {{VLCSourceFile\|src/config/core.c}}.

	~~'''''~~libvlc_new()~~'''''~~ calls ~~'''''~~libvlc_InternalInit()~~'''''~~ which handles command line parsing, loads the module bank, and spawns a number of threads to handle various vlc subsystems. The threads are spawned from inside the function ~~'''''~~playlist_ThreadCreate()~~'''''~~. Below is a list of thread start functions that are run for playlist processing. The threads corresponding to these functions are spawned in the order listed.		<code>libvlc_new()</code> calls <code>libvlc_InternalInit()</code> which handles command line parsing, loads the module bank, and spawns a number of threads to handle various vlc subsystems. The threads are spawned from inside the function <code>playlist_ThreadCreate()</code>. Below is a list of thread start functions that are run for playlist processing. The threads corresponding to these functions are spawned in the order listed.

	* ~~'''''~~RunPreparse()~~'''''~~ - Perform initial parsing of the playlist		* <code>RunPreparse()</code> - Perform initial parsing of the playlist
	* ~~'''''~~RunFetcher()~~'''''~~ - load artwork associated with playlist item		* <code>RunFetcher()</code> - load artwork associated with playlist item
	* ~~'''''~~RunControlThread()~~'''''~~ - perform playlist scheduling and playing		* <code>RunControlThread()</code> - perform playlist scheduling and playing

	See [[{{#rel2abs:../Playlist}}\|Playlist]] for more details.		See [[{{#rel2abs:../Playlist}}\|Playlist]] for more details.

DoesItReallyMatter: Change wikilink redlink

2019-02-15T20:36:33Z

Change wikilink redlink

← Older revision		Revision as of 20:36, 15 February 2019
Line 16:		Line 16:
	* '''''RunControlThread()''''' - perform playlist scheduling and playing		* '''''RunControlThread()''''' - perform playlist scheduling and playing

	See [[~~Documentation~~:~~Hacker's Guide~~/~~Playlists~~\|~~Playlists~~]] for more details.		See [[{{#rel2abs:../Playlist}}\|Playlist]] for more details.

	{{Hacker_Guide}}		{{Hacker_Guide}}

	[[Category:libVLC\|*]]		[[Category:libVLC\|*]]

DoesItReallyMatter: It looks like src/control/core.c is now src/config/core.c

2019-02-15T08:38:10Z

It looks like src/control/core.c is now src/config/core.c

← Older revision		Revision as of 08:38, 15 February 2019
Line 8:		Line 8:
	===Libvlc Instantiation===		===Libvlc Instantiation===

	Libvlc is a singleton. For each application wrapped around libvlc, only one libvlc instance should be running. In order to create an instance of libvlc, you must call '''''libvlc_new()'''''. This function initializes the thread system and allocates a libvlc instance. '''''libvlc_new()''''' resides in '''''src/~~control~~/core.c'''''.		Libvlc is a singleton. For each application wrapped around libvlc, only one libvlc instance should be running. In order to create an instance of libvlc, you must call '''''libvlc_new()'''''. This function initializes the thread system and allocates a libvlc instance. '''''libvlc_new()''''' resides in '''''{{VLCSourceFile\|src/config/core.c}}'''''.

	'''''libvlc_new()''''' calls '''''libvlc_InternalInit()''''' which handles command line parsing, loads the module bank, and spawns a number of threads to handle various vlc subsystems. The threads are spawned from inside the function '''''playlist_ThreadCreate()'''''. Below is a list of thread start functions that are run for playlist processing. The threads corresponding to these functions are spawned in the order listed.		'''''libvlc_new()''''' calls '''''libvlc_InternalInit()''''' which handles command line parsing, loads the module bank, and spawns a number of threads to handle various vlc subsystems. The threads are spawned from inside the function '''''playlist_ThreadCreate()'''''. Below is a list of thread start functions that are run for playlist processing. The threads corresponding to these functions are spawned in the order listed.

DoesItReallyMatter: +:Category:libVLC

2019-02-15T07:47:39Z

+Category:libVLC

← Older revision		Revision as of 07:47, 15 February 2019
Line 19:		Line 19:

	{{Hacker_Guide}}		{{Hacker_Guide}}

			[[Category:libVLC\|*]]

Corbax: /* Libvlc Instantiation */

2013-11-14T17:25:35Z

Libvlc Instantiation

← Older revision		Revision as of 17:25, 14 November 2013
Line 18:		Line 18:
	See [[Documentation:Hacker's Guide/Playlists\|Playlists]] for more details.		See [[Documentation:Hacker's Guide/Playlists\|Playlists]] for more details.

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

Corbax at 16:21, 30 October 2013

2013-10-30T16:21:08Z

← Older revision		Revision as of 16:21, 30 October 2013
Line 19:		Line 19:

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

Corbax at 14:42, 1 October 2013

2013-10-01T14:42:36Z

← Older revision		Revision as of 14:42, 1 October 2013
Line 17:		Line 17:

	See [[Documentation:Hacker's Guide/Playlists\|Playlists]] for more details.		See [[Documentation:Hacker's Guide/Playlists\|Playlists]] for more details.

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

J-b: moved Documentation:Hacker's Guide/libvlc to Hacker Guide/libvlc

2011-11-09T11:50:59Z

moved Documentation:Hacker's Guide/libvlc to Hacker Guide/libvlc

← Older revision	Revision as of 11:50, 9 November 2011
(No difference)

Stondage123 at 18:18, 8 June 2007

2007-06-08T18:18:16Z

New page

==Libvlc Startup==

===Introduction===
Libvlc represents the underlying API of vlc. VLC itself is just a wrapper around libvlc. By utilizing libvlc developers can take advantage of all the complex functionalities of vlc. Libvlc is generated as a shared library and can be wrapped up with numerous interfaces, including both Python and Java bindings. This allows the end user to build applications around the vlc code base and take advantage of all the plugins available to vlc instead of writing everything from scratch.

This document will explain how to get started using libvlc. It will step through the instantiation of a libvlc instance and explain the typical startup procedure of libvlc.

===Libvlc Instantiation===

Libvlc is a singleton. For each application wrapped around libvlc, only one libvlc instance should be running. In order to create an instance of libvlc, you must call '''''libvlc_new()'''''. This function initializes the thread system and allocates a libvlc instance. '''''libvlc_new()''''' resides in '''''src/control/core.c'''''.

'''''libvlc_new()''''' calls '''''libvlc_InternalInit()''''' which handles command line parsing, loads the module bank, and spawns a number of threads to handle various vlc subsystems. The threads are spawned from inside the function '''''playlist_ThreadCreate()'''''. Below is a list of thread start functions that are run for playlist processing. The threads corresponding to these functions are spawned in the order listed.

* '''''RunPreparse()''''' - Perform initial parsing of the playlist
* '''''RunFetcher()''''' - load artwork associated with playlist item
* '''''RunControlThread()''''' - perform playlist scheduling and playing

See [[Documentation:Hacker's Guide/Playlists|Playlists]] for more details.