VideoLAN Wiki - User contributions [en]

MacOSCompile

2009-12-17T13:38:49Z

The DJ: make this more prominent

== Compile VLC on Mac OS X ==

Compiling {{VLC}} on Mac OS X is different from normal linux compiling and OS X compiling. We do not use Xcode, but a simple <code>./configure</code> and then <code>make</code> isn't enough either. The instructions below are always for the currently unstable, non-released code.

If you compile from [[Git]] then please remember that this code can often be in an unstable state. If you wish to develop or test please join the vlc-devel mailinglist.

Don't put any of the non-released test binaries or git-compiles on software sites or on user-forums. We have had bad experiences with this before and we do not appreciate it.

''Be sure to read the paragraph on Mac OS X Leopard before starting the compilation.''

== Quick Steps ==
$ git clone git://git.videolan.org/vlc.git
$ cd vlc/extras/contrib
$ ./bootstrap
$ make

$ cd ../..
$ ./bootstrap
$ export CC=/Developer/usr/bin/llvm-gcc-4.2
$ export CXX=/Developer/usr/bin/llvm-g++-4.2
$ export OBJC=/Developer/usr/bin/llvm-gcc-4.2
$ ./configure --enable-debug

$ make
Read next section for more details.

== Steps ==

Please follow these steps for compiling:

=== Set the development environment ===

Install the Mac OS X Developer Tools from the Developer Tools CD, or get them online.

You need at least Mac OS X 10.5 and Xcode 3.1.2 for compilation. Mac OS X 10.6 and its Xcode releases are also supported. Make sure that the LLVM GCC 4.2 compiler is installed.

Compiling with earlier releases of Mac OS X and/or Xcode will not work.

Additionally, you may need to install Subversion (SVN) and more importantly Git on your Mac.

=== Get the source ===
Download the {{VLC}} [[GetTheSource|source code]] (using [[Git]]) as described on the [[GetTheSource| "Get the source"]] page or get a recent source tarball. Note that the 3rd party libraries will probably break a few months after the release's publication.

=== Build external libs ===

We now need to build the [[Contrib_Status| 3rd party libs]]. For that, you will need to:
* cd to the source directory with your Terminal application.
* If you have fink, then you will need to disable it. {{VLC}} has it's own form of Fink (in the extras/contrib subdir) and it can conflict with Fink. We use this system to generate a reliable, consistent and known amount of packages that {{VLC}} requires.

''To disable Fink comment the line: #source /sw/bin/init.csh in your .cshrc file or . /sw/bin/init.csh in your .bashrc file in your home-directory.''

* First fetch the contribs. Those are external libraries needed by VLC.
$ cd extras/contrib
$ ./bootstrap
$ make

The last command will download '''prebuilt''' binary contrib you can happily use to build VLC wth -- only if you're using git master branch or the bugfix branch for 0.9 / 1.0.
You will only have to do this once. (You can do it again if required libraries are added or updated by the team.)

If you're trying to debug these libraries or want to create a new package, you need to execute <code>make src</code>

''Note that the 10.5 SDK is used by default. If you encounter problems, make sure that the script correctly used Apple's llvm-gcc-4.2 compiler and your Xcode installation is up-to-date.''

=== Prepare the VLC build ===
Now we return to VLC itself. Go back to the top level VLC source directory.
$ cd ../..
$ ./bootstrap

This will create configure and Makefiles for {{VLC}} (snapshots and releases already include this).

=== Setup the correct compiler ===
Current revisions of VLC need to be compiled using Apple's llvm-gcc-4.2 compiler in its latest version. In case of failures, make sure that the latest version of Xcode is installed.
To use this compiler, you need to export the respective variables. In a Bourne Shell, type this (if Xcode is installed to its default location; bash is the default shell on OS X):

$ export CC=/Developer/usr/bin/llvm-gcc-4.2
$ export CXX=/Developer/usr/bin/llvm-g++-4.2
$ export OBJC=/Developer/usr/bin/llvm-gcc-4.2

If you are using a C-Shell, you need to use the ''setenv'' command of course.

=== Configure the VLC build ===
The next step is to configure, in the top level VLC source directory.

In current revisions, you can simply run
$ ./configure --enable-debug
to get VLC in its default configuration. If do not want to use VLC's default configuration for Mac, be sure to add <code>--disable-macosx-defaults</code> to your custom set. Using <code>--disable-nls</code> will save you a lot of time, if you don't care about localised interfaces.

When compiling earlier revisions or the 0.8.6 branch, you need to give a wide variety of configure flags to achieve a useful build. We used to use this set:
<code> ./configure --enable-debug --disable-x11 --disable-xvideo --disable-glx --enable-sdl --enable-mad --enable-libdvbpsi --enable-a52 --disable-dvdplay --enable-dvdnav --enable-dvdread --enable-ffmpeg --enable-faad --enable-flac --enable-vorbis --enable-speex --enable-theora --enable-ogg --enable-shout --enable-cddb --disable-cddax --enable-vcdx --disable-skins --disable-skins2 --disable-wxwidgets --enable-freetype --enable-fribidi --enable-caca --enable-live555 --enable-dca --enable-goom --enable-modplug --enable-gnutls --enable-daap --enable-ncurses --enable-libtwolame --enable-x264 --enable-png --enable-realrtsp --enable-lua --disable-libtool</code>
Have a look at configure.ac for our current default configuration.

You can add <code>--with-mozilla-sdk-path=./extras/contrib/gecko-sdk --enable-mozilla</code> to the configure-line to enable the compilation of VLC's Safari/Firefox plugin.

=== Build VLC ===
After configure is finished, we can finally build {{VLC}}. A simple <code>make</code> will do the trick. If you want to use the resulting application package on a different Mac or a different account on the same Mac, run
$ make
$ make VLC-release.app
afterwards. Use the resulting ''VLC-release.app'' for these purposes.

If you want a disk-image, type
$ make package-macosx
(respectively <code>make package-macosx-plugin</code> for the Safari/Mozilla plugin).

=== What's wrong, if I don't succeed? ===
Starting with Leopard, Xcode may be installed to a custom location on the administrator's choice. While this is non-problematic for ordinary Xcode projects, VLC needs a little help. You have to place extra symbolic links in /Developer pointing to your custom location for these folders:

<code>usr, Headers, Private, SDKs, Tools, Makefiles</code>

You can easily create these links by executing the following command for each folder (whereas theFolder is one of these six):

<code>ln -s /full/path/to/Developer/theFolder /Developer/theFolder</code>

'''Additionally, make always sure that you are using the latest version of Xcode. Otherwise, VLC's compilation or behaviour at runtime won't be the way you want it to be.'''

== What about 64-bit? ==
Both the 1.0-bugfix branch and the master branch can be compiled in 64-bit mode on OS X, but it is considered experimental. This is only tested for x86_64, but PPC64 should also work. Precompiled contribs are usually available for x86_64. To see how to compile VLC this way, check the documentation of your GCC vendor, as there are known differences within the supported versions of Mac OS X, but you may try:

'''After running bootstrap in extras/contrib''': Replace the first line of config.mak to <code>ARCH=x86_64</code> from <code>ARCH=i386</code>. Running <code>make</code> after only this change should cause the precompiled x86_64 contrib to be downloaded and extracted. (If you're compiling your own contrib, you should edit <code>CFLAGS_TUNING</code> and <code>EXTRA_LDFLAGS</code> to use x86_64, and you may also want to change <code>CC</code> and <code>CXX</code> to use llvm versions.)

'''Running configure''': Do something like <code>./configure CFLAGS="-arch x86_64" CXXFLAGS="-arch x86_64" LDFLAGS="-arch x86_64" OBJCFLAGS="-arch x86_64" --build=x86_64-apple-darwin9.7.0</code> instead. Not all these flags may be necessary.

== Snow Leopard ==
A series of problem affect the build under Mac OS X 10.6 (Snow Leopard / darwin 10), these include:

=== 32-bit builds ===
The compiler now tries to build for the x86_64 arch by default, if you want to make a 32-bit build of VLC, you have to change the configure, similarly to what shown above: <code>./configure CFLAGS="-arch i386" CXXFLAGS="-arch i386" LDFLAGS="-arch i386" OBJCFLAGS="-arch i386"</code>

=== Missing libiconv.la ===
The <code>/usr/lib/libiconv.la</code> file has been removed, but the other .la files in contrib still reference it; the quickest way to fix this is <code>rm extras/contrib/lib/*.la</code> (this should lead no negative consequences because OSX's dylib already provide dependency tracking).

== History ==
Written by Jean-Alexis Montignies, [[User:Fkuehne|Felix Paul Kühne]] and [[User:The DJ|Derk-Jan Hartman]], for the VideoLAN Team.
Adapted to the Wiki by [[User:j-b|Jean-Baptiste Kempf]].

[[Category:Building]]
[[Category:Coding]]

User:The DJ

2009-06-12T19:00:05Z

The DJ: Created page with 'Derk-Jan Hartman, Developer. aka. hartman aka thedj For general usage or development problems, refer to vlc or vlc-devel (both @videolan.org as well) please. Thanks :)'

Derk-Jan Hartman, Developer.

aka. hartman aka thedj

For general usage or development problems, refer to vlc or vlc-devel (both @videolan.org as well) please. Thanks :)

MacOSCompile

2009-06-12T18:58:11Z

The DJ: /* History */ link

== Compile VLC on Mac OS X ==

Compiling {{VLC}} on Mac OS X is different from normal linux compiling and OS X compiling. We do not use Xcode, but a simple <code>./configure</code> and then <code>make</code> isn't enough either. The instructions below are always for the currently unstable, non-released code.

If you compile from [[Git]] then please remember that this code can often be in an unstable state. If you wish to develop or test please join the vlc-devel mailinglist.

Don't put any of the non-released test binaries or git-compiles on software sites or on user-forums. We have had bad experiences with this before and we do not appreciate it.

''Be sure to read the paragraph on Mac OS X Leopard before starting the compilation.''

== Steps ==

Please follow these steps for compiling:

=== Set the development environment ===

Install the Mac OS X Developer Tools from the Developer Tools CD, or get them online.

You need at least Mac OS X 10.5 and Xcode 3.1.2 for compilation. Mac OS X 10.6 and its Xcode releases are also supported. Make sure that the LLVM GCC 4.2 compiler is installed.

Compiling with earlier releases of Mac OS X and/or Xcode will not work.

Additionally, you may need to install Subversion (SVN) and more importantly Git on your Mac.

=== Get the source ===
Download the {{VLC}} [[GetTheSource|source code]] (using [[Git]]) as described on the [[GetTheSource| "Get the source"]] page or get a recent source tarball. Note that the 3rd party libraries will probably break a few months after the release's publication.

=== Build external libs ===

We now need to build the [[Contrib_Status| 3rd party libs]]. For that, you will need to:
* cd to the source directory with your Terminal application.
* If you have fink, then you will need to disable it. {{VLC}} has it's own form of Fink (in the extras/contrib subdir) and it can conflict with Fink. We use this system to generate a reliable, consistent and known amount of packages that {{VLC}} requires.

''To disable Fink comment the line: #source /sw/bin/init.csh in your .cshrc file or . /sw/bin/init.csh in your .bashrc file in your home-directory.''

* cd to the extras/contrib subdir of VLC and execute <code>./bootstrap</code>
* Now execute <code>make</code>.

This will download prebuilt binary contrib you can happily use to build VLC wth -- only if you're using git master branch or the bugfix branch for 0.9 / 1.0.

If you're trying to debug these libraries or want to create a new package, you need to execute:

<code>make src</code>

This will download and compile all the required external libraries and programs. You will only have to do this once. (You can do it again if required libraries are added or updated by the team.)

''Note that the 10.5 SDK is used by default. If you encounter problems, make sure that the script correctly used Apple's llvm-gcc-4.2 compiler and your Xcode installation is up-to-date.''

=== Prepare the VLC build ===
Now we return to VLC itself. Go back to the top level VLC source directory. If you use Subversion (which you really should), then run <code>./bootstrap</code>.

This will create configure and Makefiles for {{VLC}} (snapshots and releases already include this).

=== Setup the correct compiler ===
Current revisions of VLC need to be compiled using Apple's llvm-gcc-4.2 compiler in its latest version. In case of failures, make sure that the latest version of Xcode is installed.
To use this compiler, you need to export the respective variables. In a Bourne Shell, type this (if Xcode is installed to its default location; bash is the default shell on OS X):

<code>export CC=/Developer/usr/bin/llvm-gcc-4.2</code>

<code>export CXX=/Developer/usr/bin/llvm-g++-4.2</code>

<code>export OBJC=/Developer/usr/bin/llvm-gcc-4.2</code>

If you are using a C-Shell, you need to use the ''setenv'' command of course.

=== Configure the VLC build ===
The next step is to configure, in the top level VLC source directory.

In current revisions, you can simply run <code>./configure --enable-debug</code> to get VLC in its default configuration. If do not want to use VLC's default configuration for Mac, be sure to add <code>--disable-macosx-defaults</code> to your custom set. Using <code>--disable-nls</code> will save you a lot of time, if you don't care about localised interfaces.

When compiling earlier revisions or the 0.8.6 branch, you need to give a wide variety of configure flags to achieve a useful build. We used to use this set:
<code> ./configure --enable-debug --disable-x11 --disable-xvideo --disable-glx --enable-sdl --enable-mad --enable-libdvbpsi --enable-a52 --disable-dvdplay --enable-dvdnav --enable-dvdread --enable-ffmpeg --enable-faad --enable-flac --enable-vorbis --enable-speex --enable-theora --enable-ogg --enable-shout --enable-cddb --disable-cddax --enable-vcdx --disable-skins --disable-skins2 --disable-wxwidgets --enable-freetype --enable-fribidi --enable-caca --enable-live555 --enable-dca --enable-goom --enable-modplug --enable-gnutls --enable-daap --enable-ncurses --enable-libtwolame --enable-x264 --enable-png --enable-realrtsp --enable-lua --disable-libtool</code>
Have a look at configure.ac for our current default configuration.

You can add <code>--with-mozilla-sdk-path=./extras/contrib/gecko-sdk --enable-mozilla</code> to the configure-line to enable the compilation of VLC's Safari/Firefox plugin.

=== Build VLC ===
After configure is finished, we can finally build {{VLC}}. A simple <code>make</code> will do the trick. If you want to use the resulting application package on a different Mac or a different account on the same Mac, run <code>make VLC-release.app</code> afterwards. Use the resulting ''VLC-release.app'' for these purposes. If you want a disk-image, type <code>make package-macosx</code> (respectively <code>make package-macosx-plugin</code> for the Safari/Mozilla plugin).

=== What's wrong, if I don't succeed? ===
Starting with Leopard, Xcode may be installed to a custom location on the administrator's choice. While this is non-problematic for ordinary Xcode projects, VLC needs a little help. You have to place extra symbolic links in /Developer pointing to your custom location for these folders:

<code>usr, Headers, Private, SDKs, Tools, Makefiles</code>

You can easily create these links by executing the following command for each folder (whereas theFolder is one of these six):

<code>ln -s /full/path/to/Developer/theFolder /Developer/theFolder</code>

'''Additionally, make always sure that you are using the latest version of Xcode. Otherwise, VLC's compilation or behaviour at runtime won't be the way you want it to be. Ah, and don't try to do a 64bit build of VLC on your Mac. That's not supported for now and you will end up with tons of errors and warnings (and neither audio nor video output).'''

== History ==
Written by Jean-Alexis Montignies, [[User:Fkuehne|Felix Paul Kühne]] and [[User:The DJ|Derk-Jan Hartman]], for the VideoLAN Team.
Adapted to the Wiki by [[User:j-b|Jean-Baptiste Kempf]].

[[Category:Building]]
[[Category:Coding]]

MacOSCompile

2009-06-12T18:57:38Z

The DJ: /* Configure the VLC build */ update the patch of gecko-sdk for 0.9 and 1.0

== Compile VLC on Mac OS X ==

Compiling {{VLC}} on Mac OS X is different from normal linux compiling and OS X compiling. We do not use Xcode, but a simple <code>./configure</code> and then <code>make</code> isn't enough either. The instructions below are always for the currently unstable, non-released code.

If you compile from [[Git]] then please remember that this code can often be in an unstable state. If you wish to develop or test please join the vlc-devel mailinglist.

Don't put any of the non-released test binaries or git-compiles on software sites or on user-forums. We have had bad experiences with this before and we do not appreciate it.

''Be sure to read the paragraph on Mac OS X Leopard before starting the compilation.''

== Steps ==

Please follow these steps for compiling:

=== Set the development environment ===

Install the Mac OS X Developer Tools from the Developer Tools CD, or get them online.

You need at least Mac OS X 10.5 and Xcode 3.1.2 for compilation. Mac OS X 10.6 and its Xcode releases are also supported. Make sure that the LLVM GCC 4.2 compiler is installed.

Compiling with earlier releases of Mac OS X and/or Xcode will not work.

Additionally, you may need to install Subversion (SVN) and more importantly Git on your Mac.

=== Get the source ===
Download the {{VLC}} [[GetTheSource|source code]] (using [[Git]]) as described on the [[GetTheSource| "Get the source"]] page or get a recent source tarball. Note that the 3rd party libraries will probably break a few months after the release's publication.

=== Build external libs ===

We now need to build the [[Contrib_Status| 3rd party libs]]. For that, you will need to:
* cd to the source directory with your Terminal application.
* If you have fink, then you will need to disable it. {{VLC}} has it's own form of Fink (in the extras/contrib subdir) and it can conflict with Fink. We use this system to generate a reliable, consistent and known amount of packages that {{VLC}} requires.

''To disable Fink comment the line: #source /sw/bin/init.csh in your .cshrc file or . /sw/bin/init.csh in your .bashrc file in your home-directory.''

* cd to the extras/contrib subdir of VLC and execute <code>./bootstrap</code>
* Now execute <code>make</code>.

This will download prebuilt binary contrib you can happily use to build VLC wth -- only if you're using git master branch or the bugfix branch for 0.9 / 1.0.

If you're trying to debug these libraries or want to create a new package, you need to execute:

<code>make src</code>

This will download and compile all the required external libraries and programs. You will only have to do this once. (You can do it again if required libraries are added or updated by the team.)

''Note that the 10.5 SDK is used by default. If you encounter problems, make sure that the script correctly used Apple's llvm-gcc-4.2 compiler and your Xcode installation is up-to-date.''

=== Prepare the VLC build ===
Now we return to VLC itself. Go back to the top level VLC source directory. If you use Subversion (which you really should), then run <code>./bootstrap</code>.

This will create configure and Makefiles for {{VLC}} (snapshots and releases already include this).

=== Setup the correct compiler ===
Current revisions of VLC need to be compiled using Apple's llvm-gcc-4.2 compiler in its latest version. In case of failures, make sure that the latest version of Xcode is installed.
To use this compiler, you need to export the respective variables. In a Bourne Shell, type this (if Xcode is installed to its default location; bash is the default shell on OS X):

<code>export CC=/Developer/usr/bin/llvm-gcc-4.2</code>

<code>export CXX=/Developer/usr/bin/llvm-g++-4.2</code>

<code>export OBJC=/Developer/usr/bin/llvm-gcc-4.2</code>

If you are using a C-Shell, you need to use the ''setenv'' command of course.

=== Configure the VLC build ===
The next step is to configure, in the top level VLC source directory.

In current revisions, you can simply run <code>./configure --enable-debug</code> to get VLC in its default configuration. If do not want to use VLC's default configuration for Mac, be sure to add <code>--disable-macosx-defaults</code> to your custom set. Using <code>--disable-nls</code> will save you a lot of time, if you don't care about localised interfaces.

When compiling earlier revisions or the 0.8.6 branch, you need to give a wide variety of configure flags to achieve a useful build. We used to use this set:
<code> ./configure --enable-debug --disable-x11 --disable-xvideo --disable-glx --enable-sdl --enable-mad --enable-libdvbpsi --enable-a52 --disable-dvdplay --enable-dvdnav --enable-dvdread --enable-ffmpeg --enable-faad --enable-flac --enable-vorbis --enable-speex --enable-theora --enable-ogg --enable-shout --enable-cddb --disable-cddax --enable-vcdx --disable-skins --disable-skins2 --disable-wxwidgets --enable-freetype --enable-fribidi --enable-caca --enable-live555 --enable-dca --enable-goom --enable-modplug --enable-gnutls --enable-daap --enable-ncurses --enable-libtwolame --enable-x264 --enable-png --enable-realrtsp --enable-lua --disable-libtool</code>
Have a look at configure.ac for our current default configuration.

You can add <code>--with-mozilla-sdk-path=./extras/contrib/gecko-sdk --enable-mozilla</code> to the configure-line to enable the compilation of VLC's Safari/Firefox plugin.

=== Build VLC ===
After configure is finished, we can finally build {{VLC}}. A simple <code>make</code> will do the trick. If you want to use the resulting application package on a different Mac or a different account on the same Mac, run <code>make VLC-release.app</code> afterwards. Use the resulting ''VLC-release.app'' for these purposes. If you want a disk-image, type <code>make package-macosx</code> (respectively <code>make package-macosx-plugin</code> for the Safari/Mozilla plugin).

=== What's wrong, if I don't succeed? ===
Starting with Leopard, Xcode may be installed to a custom location on the administrator's choice. While this is non-problematic for ordinary Xcode projects, VLC needs a little help. You have to place extra symbolic links in /Developer pointing to your custom location for these folders:

<code>usr, Headers, Private, SDKs, Tools, Makefiles</code>

You can easily create these links by executing the following command for each folder (whereas theFolder is one of these six):

<code>ln -s /full/path/to/Developer/theFolder /Developer/theFolder</code>

'''Additionally, make always sure that you are using the latest version of Xcode. Otherwise, VLC's compilation or behaviour at runtime won't be the way you want it to be. Ah, and don't try to do a 64bit build of VLC on your Mac. That's not supported for now and you will end up with tons of errors and warnings (and neither audio nor video output).'''

== History ==
Written by Jean-Alexis Montignies, [[User:Fkuehne|Felix Paul Kühne]] and Derk-Jan Hartman, for the VideoLAN Team.
Adapted to the Wiki by [[User:j-b|Jean-Baptiste Kempf]].

[[Category:Building]]
[[Category:Coding]]

VideoLAN Sites

2008-09-05T14:23:05Z

The DJ: /* Deneb */ correct address

= WebSites =
== VideoLAN public sites ==
* [http://www.videolan.org Main Site]
* [http://wiki.videolan.org Wiki]
* [http://forum.videolan.org Forum]
* [http://planet.videolan.org Developers' News]
* [ftp://ftp.videolan.org/pub/videolan/ Main FTP]
* [http://paste.videolan.org/ PasteBin]
* [http://lists.videolan.org/ Files Attachments from the mailing-lists]

== Developers ==
* [http://developers.videolan.org Main Developers Site]
* [http://nightlies.videolan.org Nightly builds]
* [http://buildbot.videolan.org Buildbot for Automatic Builds]
* [http://trac.videolan.org Trac, bugs, features, roadmap]
* [http://git.videolan.org Gitweb]
* [http://mirrors.videolan.org Mirrors check]
* [http://downloads.videolan.org/pub/ Download Site]
* [http://stats.videolan.org Servers stats]
* [ftp://streams.videolan.org Reference and buggy stream collection]

== Update ==
* [http://update.videolan.org VLC update site] - Non human readable site !

== Other ==
* [http://getvlcstatus.videolan.org VLC Status Page] (This is humour, of course)

= Servers =
== Ganesh ==
* ganesh.videolan.org
* developers.videolan.org
* download.videolan.org, downloads.videolan.org
* ftp.videolan.org
* rsync.videolan.org
* forum.videolan.org
* lists.videolan.org
* mirrors.videolan.org
* planet.videolan.org
* paste.videolan.org
* stats.videolan.org
* svn.videolan.org
* trac.videolan.org
* update.videolan.org
* www.videolan.org

The primary web and FTP server
Hosted in one of FREE S.A.S' datacenter.

== Altair ==
* altair.videolan.org
* buildbot.videolan.org
* nightlies.videolan.org
* people.videolan.org
* git-soc.videolan.org

It is the dev server, that hosts the automatic builds.
Hosted at VIA.

== Epsilon (Shipped back, RIP) ==
*epsilon.videolan.org

Used to be...
Mac Intel Developer Preview machine
Also a nightly build machine for Mac OS X Intel.
Hosted at VIA.

== Jones ==
*jones.videolan.org
* streams.videolan.org
* hudson.videolan.org

Mac Pro (Intel)
build bot machine for Mac OS X Intel.
Hosted at VIA.
Named after Christmas Jones

== Veda ==
*veda.student.utwente.nl
PowerMac - 1.8Ghz Dual, 750MB RAM
Primary Mac OS X PowerPC development machine. Hosts the nightly build client for the OSX PowerPC platform.
Hosted by TheDJ.

== Deneb ==
*cc1001114-b. ensch1. ov. home .nl
Imac 17" - 2Ghz DC, 1GB RAM
Primary Mac OS X Intel development machine. Hosts the nightly build client for the OSX Intel platform.
Hosted by TheDJ.

== Skanda ==
* skanda.videolan.org
* wiki.videolan.org
* git.videolan.org
* svn.videolan.org
* mailman.videolan.org
* download2.videolan.org (for backup, currently unused)
Hosted by OVH with donations of Actech. For more information contact [[User:Remiii|Remiii]].

Some server pictures can be found on: http://people.videolan.org/~dionoea/servers/

{{stub}}

[[Category:About VideoLAN]]

VLC CodeNames

2007-03-08T21:59:47Z

The DJ: why the goldeneye characters are used

=== The different VLC release codenames were: ===

VLC codenames are based on characters in Goldeneye ([[wikipedia:fr:GoldenEye|français]] | [[wikipedia:GoldenEye|english]]). This movie is one of the movies that was used during the original development phase to test VLC.

{|class="wikitable"
! Version !! Codename
|-
| < 0.1.99x || Onatopp
|-
| 0.2.(x<5) || Onatopp
|-
| 0.2.(x>=5) || Ourumov
|-
| 0.3.x || Ourumov
|-
| 0.4.x || Ourumov
|-
| 0.5.x || Natalya
|-
| 0.6.x || Trevelyan
|-
| 0.7.x || Bond
|-
| 0.8.x || Janus
|-
| 0.9.x || Grishenko
|}

Work has already started on [https://trac.videolan.org/vlc/ticket/35 world domination], which is scheduled for version 1.0.0.

[[Category:About VideoLAN]]

SoC 2007

2007-03-08T17:49:17Z

The DJ: /* Subtitle support */ language and expand

Reflexions for Google Summer of Code applications.

== Introduction & Informations ==

This wiki page deals with [[VideoLAN]] attempt to be a mentoring organisation for [http://code.google.com/soc/ Google Summer of Code]
to improve {{VLC}}.

=== VLC media player ===
{{VLC}} is a Multimedia player, encoder and streamer application, that is platform independant.
It is one of the most successful open-source projects without any professional structure underneath.

{{VLC}} is downloaded at an approximate rate of 4 millions every month from the main website (does not include unofficial mirrors and packaged distribution (linux)), which means about 30 million people have downloaded VLC 0.8.5 from the main website!

You can have more information on [http://en.wikipedia.org/wiki/VLC_media_player VLC on Wikipedia] or on this [[Main_Page|wiki]].

=== Summer of Code ===
We would like to be a mentoring organisation ([http://code.google.com/support/bin/answer.py?answer=60303&topic=10727 mentors on SoC Website]).

If selected and developed, SoC ideas will be included in {{VLC}} 0.9.1, under the GPL licence. 0.9.0 which should be the next version of VLC should be out before the summer.

=== Ideas ===
'''Read this'''

We (the VideoLAN team, and [[User:J-b|jb]], the writer of this page) have split this page in two idea lists:
* The ''first ideas'' are the ones we would like to focus on, and seem to be key projects for VLC and a lot more ''fun'' than the others; we have affected potential mentors to these projects.
* and other ones that are less detailed but could be good ideas too.

We don't want to impose anything. This is free and Open Source software.

If you don't want to apply for SoC but want other ideas, check the [[Mini Projects]] page!

== Main ideas ==

=== GUI interfaces for the browsers plug-ins ===
This project focuses on adding interfaces to our browser plug-ins, in order to have, in the web pages embedded mode, buttons to control {{VLC}} as in WMP or Youtube player. These buttons need to be cross-platform and cross-browsers.

The second part of this project aims to provide a replacement for all preconfigured media players embedded in web pages, if possible.

For example, when a webpage asks for WMP embedded plugin, youtube player, quicktime player or any other, VLC would detect the stream and display it. This would mean less CPU needed than Flash based players...

This project may need to work in concert with some improvements on the cache handling module access.

The look of the interface should not be a problem (it can be added later on).

''Proposed mentor: Quovodis.''

=== Fullscreen Controller ===
This project is easy to describe, it would provide a fullscreen controller for Linux/Unix and Windows, as {{VLC}} already has on MacOS X version since 0.8.6.

It should be draggable, clickable and support the classical control buttons to control VLC playback in fullscreen mode.

With this project, which is not too long, there should be some related work on Vout (Making sure the video output does not close and reopen between files for example...)

''Proposed mentor: Not defined yet''

=== Subtitle support ===

This project would rework the subtitle infrastructure and freetype module in order to read more subtitles:

* support bold, italic, underline, RGB colors, size changes and font changes for a whole line or part of one line, (partial now)
* support for the subtitles HTML tags, and add all the most used subtitles types that are not yet in, (almost complete now)
* support for advanced SSA/ASS rendering using libass or asa or any other mean, (not existing today)
* detecting overlap of two subtitle pictures and moving them so that this is less annoying,
* capability of displaying subtitles with no video enabled for audio books,
* ease the automatic extraction to a filebased format of subtitles. These subtitles can come from videos used in different formats (DVB, line 23...)

Optional related work:
* capability of moving the subtitles in the picture (freetype renderer),
* support for Karaoke subtitles ( :D )

''Proposed mentor: Dnumgis''

=== Vista acceleration and DirectX improvements ===
Current versions of {{VLC}} have a lot of problems on Windows Vista (check the forums for specifics).

We need support for the new EVR (enhanced video renderer) in Windows Vista, and make it the default Video Output module for that OS.

See [http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/MED134_WH06.ppt Windows Vista Video Pipeline Architecture And Implementation] and [http://msdn2.microsoft.com/en-us/library/ms788119.aspx DirectShow Improvements in Vista]

Some rework and enhancements of the DirectX and Direct3D Video Output modules may also be necessary.

''Proposed mentor: Quovodis''

=== MacOS X and Leopard ===
There are a few MacOS X specific projects, especially for Leopard (Mac OS X 10.5)

* Creation a {{VLC}} framework that can be used by both VLC.app and VLCplugin.bundle to integrate better with other Mac applications
* Adapt and use Leopard enhancements in {{VLC}}: QTKit Capture API, Resolution independence, iChat Theatre, ...

''Proposed mentor : TheDJ''

=== RTSP ===

''Proposed mentor: jpsaman

== Other Ideas SoC 2007 ==

=== Matroska (mkv) muxing ===
robUx4 can do the mentoring. He already wrote the demux and knows mkv really well.
But this muxer may be better suited for a FFMPEG project, and we should adapt ourselves after that.

=== VLM Schedule rework ===

=== WinCE port ===

=== Mini Projects - More ideas ===

We have a more general page for ideas for Project in {{VLC}}, that could give you ideas: [[Mini_Projects]].

== Questions? Contact us ? ==
If you need to contact us, you can use this [[Talk:SoC_2007| Talk page]], use the vlc-devel mailing list, or contact one of the mentors or [[User:J-b| Jean-Baptiste Kempf]]

SoC 2007

2007-03-08T17:45:33Z

The DJ: /* Fullscreen Controller */ language

Reflexions for Google Summer of Code applications.

== Introduction & Informations ==

This wiki page deals with [[VideoLAN]] attempt to be a mentoring organisation for [http://code.google.com/soc/ Google Summer of Code]
to improve {{VLC}}.

=== VLC media player ===
{{VLC}} is a Multimedia player, encoder and streamer application, that is platform independant.
It is one of the most successful open-source projects without any professional structure underneath.

{{VLC}} is downloaded at an approximate rate of 4 millions every month from the main website (does not include unofficial mirrors and packaged distribution (linux)), which means about 30 million people have downloaded VLC 0.8.5 from the main website!

You can have more information on [http://en.wikipedia.org/wiki/VLC_media_player VLC on Wikipedia] or on this [[Main_Page|wiki]].

=== Summer of Code ===
We would like to be a mentoring organisation ([http://code.google.com/support/bin/answer.py?answer=60303&topic=10727 mentors on SoC Website]).

If selected and developed, SoC ideas will be included in {{VLC}} 0.9.1, under the GPL licence. 0.9.0 which should be the next version of VLC should be out before the summer.

=== Ideas ===
'''Read this'''

We (the VideoLAN team, and [[User:J-b|jb]], the writer of this page) have split this page in two idea lists:
* The ''first ideas'' are the ones we would like to focus on, and seem to be key projects for VLC and a lot more ''fun'' than the others; we have affected potential mentors to these projects.
* and other ones that are less detailed but could be good ideas too.

We don't want to impose anything. This is free and Open Source software.

If you don't want to apply for SoC but want other ideas, check the [[Mini Projects]] page!

== Main ideas ==

=== GUI interfaces for the browsers plug-ins ===
This project focuses on adding interfaces to our browser plug-ins, in order to have, in the web pages embedded mode, buttons to control {{VLC}} as in WMP or Youtube player. These buttons need to be cross-platform and cross-browsers.

The second part of this project aims to provide a replacement for all preconfigured media players embedded in web pages, if possible.

For example, when a webpage asks for WMP embedded plugin, youtube player, quicktime player or any other, VLC would detect the stream and display it. This would mean less CPU needed than Flash based players...

This project may need to work in concert with some improvements on the cache handling module access.

The look of the interface should not be a problem (it can be added later on).

''Proposed mentor: Quovodis.''

=== Fullscreen Controller ===
This project is easy to describe, it would provide a fullscreen controller for Linux/Unix and Windows, as {{VLC}} already has on MacOS X version since 0.8.6.

It should be draggable, clickable and support the classical control buttons to control VLC playback in fullscreen mode.

With this project, which is not too long, there should be some related work on Vout (Making sure the video output does not close and reopen between files for example...)

''Proposed mentor: Not defined yet''

=== Subtitle support ===

This project would rework the subtitle infrastructure and freetype module in order to read more subtitles:

* support bold, italic, underline, RGB colors, size changes and font changes for a whole line or part of one line, (partial now)
* support for the subtitles HTML tags, and add all the most used subtitles types that are not yet in, (almost complete now)
* support for SSA/ASS using libass or asa or any other mean, (not existing today)
* capability of displaying two different subtitles, with no overlap,
* capability of displaying subtitles with no video enabled for audio books,
* ease the automatic extraction of subtitles from videos used in different formats (DVB, line 23...)

Optionnal related work:
* capability of moving the subtitles in the picture (freetype renderer),
* support for Karaoke subtitles ( :D )

''Proposed mentor: Dnumgis''

=== Vista acceleration and DirectX improvements ===
Current versions of {{VLC}} have a lot of problems on Windows Vista (check the forums for specifics).

We need support for the new EVR (enhanced video renderer) in Windows Vista, and make it the default Video Output module for that OS.

See [http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/MED134_WH06.ppt Windows Vista Video Pipeline Architecture And Implementation] and [http://msdn2.microsoft.com/en-us/library/ms788119.aspx DirectShow Improvements in Vista]

Some rework and enhancements of the DirectX and Direct3D Video Output modules may also be necessary.

''Proposed mentor: Quovodis''

=== MacOS X and Leopard ===
There are a few MacOS X specific projects, especially for Leopard (Mac OS X 10.5)

* Creation a {{VLC}} framework that can be used by both VLC.app and VLCplugin.bundle to integrate better with other Mac applications
* Adapt and use Leopard enhancements in {{VLC}}: QTKit Capture API, Resolution independence, iChat Theatre, ...

''Proposed mentor : TheDJ''

=== RTSP ===

''Proposed mentor: jpsaman

== Other Ideas SoC 2007 ==

=== Matroska (mkv) muxing ===
robUx4 can do the mentoring. He already wrote the demux and knows mkv really well.
But this muxer may be better suited for a FFMPEG project, and we should adapt ourselves after that.

=== VLM Schedule rework ===

=== WinCE port ===

=== Mini Projects - More ideas ===

We have a more general page for ideas for Project in {{VLC}}, that could give you ideas: [[Mini_Projects]].

== Questions? Contact us ? ==
If you need to contact us, you can use this [[Talk:SoC_2007| Talk page]], use the vlc-devel mailing list, or contact one of the mentors or [[User:J-b| Jean-Baptiste Kempf]]

SoC 2007

2007-03-08T17:40:48Z

The DJ: /* Summer of Code */ language

Reflexions for Google Summer of Code applications.

== Introduction & Informations ==

This wiki page deals with [[VideoLAN]] attempt to be a mentoring organisation for [http://code.google.com/soc/ Google Summer of Code]
to improve {{VLC}}.

=== VLC media player ===
{{VLC}} is a Multimedia player, encoder and streamer application, that is platform independant.
It is one of the most successful open-source projects without any professional structure underneath.

{{VLC}} is downloaded at an approximate rate of 4 millions every month from the main website (does not include unofficial mirrors and packaged distribution (linux)), which means about 30 million people have downloaded VLC 0.8.5 from the main website!

You can have more information on [http://en.wikipedia.org/wiki/VLC_media_player VLC on Wikipedia] or on this [[Main_Page|wiki]].

=== Summer of Code ===
We would like to be a mentoring organisation ([http://code.google.com/support/bin/answer.py?answer=60303&topic=10727 mentors on SoC Website]).

If selected and developed, SoC ideas will be included in {{VLC}} 0.9.1, under the GPL licence. 0.9.0 which should be the next version of VLC should be out before the summer.

=== Ideas ===
'''Read this'''

We (the VideoLAN team, and [[User:J-b|jb]], the writer of this page) have split this page in two idea lists:
* The ''first ideas'' are the ones we would like to focus on, and seem to be key projects for VLC and a lot more ''fun'' than the others; we have affected potential mentors to these projects.
* and other ones that are less detailed but could be good ideas too.

We don't want to impose anything. This is free and Open Source software.

If you don't want to apply for SoC but want other ideas, check the [[Mini Projects]] page!

== Main ideas ==

=== GUI interfaces for the browsers plug-ins ===
This project focuses on adding interfaces to our browser plug-ins, in order to have, in the web pages embedded mode, buttons to control {{VLC}} as in WMP or Youtube player. These buttons need to be cross-platform and cross-browsers.

The second part of this project aims to provide a replacement for all preconfigured media players embedded in web pages, if possible.

For example, when a webpage asks for WMP embedded plugin, youtube player, quicktime player or any other, VLC would detect the stream and display it. This would mean less CPU needed than Flash based players...

This project may need to work in concert with some improvements on the cache handling module access.

The look of the interface should not be a problem (it can be added later on).

''Proposed mentor: Quovodis.''

=== Fullscreen Controller ===
This project is easy to describe, it would provide a fullscreen controller for Linux/Unix and Windows, as {{VLC}} already has on MacOS X version since 0.8.6.

It should be draggable, clickable and support the classical control buttons to interfere with VLC in fullscreen mode.

With this project, which is not too long, there should be some related work on Vout (non-flickering changes for example...)

''Proposed mentor: Not defined yet''

=== Subtitle support ===

This project would rework the subtitle infrastructure and freetype module in order to read more subtitles:

* support bold, italic, underline, RGB colors, size changes and font changes for a whole line or part of one line, (partial now)
* support for the subtitles HTML tags, and add all the most used subtitles types that are not yet in, (almost complete now)
* support for SSA/ASS using libass or asa or any other mean, (not existing today)
* capability of displaying two different subtitles, with no overlap,
* capability of displaying subtitles with no video enabled for audio books,
* ease the automatic extraction of subtitles from videos used in different formats (DVB, line 23...)

Optionnal related work:
* capability of moving the subtitles in the picture (freetype renderer),
* support for Karaoke subtitles ( :D )

''Proposed mentor: Dnumgis''

=== Vista acceleration and DirectX improvements ===
Current versions of {{VLC}} have a lot of problems on Windows Vista (check the forums for specifics).

We need support for the new EVR (enhanced video renderer) in Windows Vista, and make it the default Video Output module for that OS.

See [http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/MED134_WH06.ppt Windows Vista Video Pipeline Architecture And Implementation] and [http://msdn2.microsoft.com/en-us/library/ms788119.aspx DirectShow Improvements in Vista]

Some rework and enhancements of the DirectX and Direct3D Video Output modules may also be necessary.

''Proposed mentor: Quovodis''

=== MacOS X and Leopard ===
There are a few MacOS X specific projects, especially for Leopard (Mac OS X 10.5)

* Creation a {{VLC}} framework that can be used by both VLC.app and VLCplugin.bundle to integrate better with other Mac applications
* Adapt and use Leopard enhancements in {{VLC}}: QTKit Capture API, Resolution independence, iChat Theatre, ...

''Proposed mentor : TheDJ''

=== RTSP ===

''Proposed mentor: jpsaman

== Other Ideas SoC 2007 ==

=== Matroska (mkv) muxing ===
robUx4 can do the mentoring. He already wrote the demux and knows mkv really well.
But this muxer may be better suited for a FFMPEG project, and we should adapt ourselves after that.

=== VLM Schedule rework ===

=== WinCE port ===

=== Mini Projects - More ideas ===

We have a more general page for ideas for Project in {{VLC}}, that could give you ideas: [[Mini_Projects]].

== Questions? Contact us ? ==
If you need to contact us, you can use this [[Talk:SoC_2007| Talk page]], use the vlc-devel mailing list, or contact one of the mentors or [[User:J-b| Jean-Baptiste Kempf]]

SoC 2007

2007-03-08T17:39:54Z

The DJ: /* VLC media player */ language

Reflexions for Google Summer of Code applications.

== Introduction & Informations ==

This wiki page deals with [[VideoLAN]] attempt to be a mentoring organisation for [http://code.google.com/soc/ Google Summer of Code]
to improve {{VLC}}.

=== VLC media player ===
{{VLC}} is a Multimedia player, encoder and streamer application, that is platform independant.
It is one of the most successful open-source projects without any professional structure underneath.

{{VLC}} is downloaded at an approximate rate of 4 millions every month from the main website (does not include unofficial mirrors and packaged distribution (linux)), which means about 30 million people have downloaded VLC 0.8.5 from the main website!

You can have more information on [http://en.wikipedia.org/wiki/VLC_media_player VLC on Wikipedia] or on this [[Main_Page|wiki]].

=== Summer of Code ===
We would like to be a mentoring organisation ([http://code.google.com/support/bin/answer.py?answer=60303&topic=10727 mentors on SoC Website]).

If selected and developed, SoC ideas will be included in {{VLC}} 0.9.1, under the GPL licence. 0.9.0, next version of VLC should be out before the summer.

=== Ideas ===
'''Read this'''

We (the VideoLAN team, and [[User:J-b|jb]], the writer of this page) have split this page in two idea lists:
* The ''first ideas'' are the ones we would like to focus on, and seem to be key projects for VLC and a lot more ''fun'' than the others; we have affected potential mentors to these projects.
* and other ones that are less detailed but could be good ideas too.

We don't want to impose anything. This is free and Open Source software.

If you don't want to apply for SoC but want other ideas, check the [[Mini Projects]] page!

== Main ideas ==

=== GUI interfaces for the browsers plug-ins ===
This project focuses on adding interfaces to our browser plug-ins, in order to have, in the web pages embedded mode, buttons to control {{VLC}} as in WMP or Youtube player. These buttons need to be cross-platform and cross-browsers.

The second part of this project aims to provide a replacement for all preconfigured media players embedded in web pages, if possible.

For example, when a webpage asks for WMP embedded plugin, youtube player, quicktime player or any other, VLC would detect the stream and display it. This would mean less CPU needed than Flash based players...

This project may need to work in concert with some improvements on the cache handling module access.

The look of the interface should not be a problem (it can be added later on).

''Proposed mentor: Quovodis.''

=== Fullscreen Controller ===
This project is easy to describe, it would provide a fullscreen controller for Linux/Unix and Windows, as {{VLC}} already has on MacOS X version since 0.8.6.

It should be draggable, clickable and support the classical control buttons to interfere with VLC in fullscreen mode.

With this project, which is not too long, there should be some related work on Vout (non-flickering changes for example...)

''Proposed mentor: Not defined yet''

=== Subtitle support ===

This project would rework the subtitle infrastructure and freetype module in order to read more subtitles:

* support bold, italic, underline, RGB colors, size changes and font changes for a whole line or part of one line, (partial now)
* support for the subtitles HTML tags, and add all the most used subtitles types that are not yet in, (almost complete now)
* support for SSA/ASS using libass or asa or any other mean, (not existing today)
* capability of displaying two different subtitles, with no overlap,
* capability of displaying subtitles with no video enabled for audio books,
* ease the automatic extraction of subtitles from videos used in different formats (DVB, line 23...)

Optionnal related work:
* capability of moving the subtitles in the picture (freetype renderer),
* support for Karaoke subtitles ( :D )

''Proposed mentor: Dnumgis''

=== Vista acceleration and DirectX improvements ===
Current versions of {{VLC}} have a lot of problems on Windows Vista (check the forums for specifics).

We need support for the new EVR (enhanced video renderer) in Windows Vista, and make it the default Video Output module for that OS.

See [http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/MED134_WH06.ppt Windows Vista Video Pipeline Architecture And Implementation] and [http://msdn2.microsoft.com/en-us/library/ms788119.aspx DirectShow Improvements in Vista]

Some rework and enhancements of the DirectX and Direct3D Video Output modules may also be necessary.

''Proposed mentor: Quovodis''

=== MacOS X and Leopard ===
There are a few MacOS X specific projects, especially for Leopard (Mac OS X 10.5)

* Creation a {{VLC}} framework that can be used by both VLC.app and VLCplugin.bundle to integrate better with other Mac applications
* Adapt and use Leopard enhancements in {{VLC}}: QTKit Capture API, Resolution independence, iChat Theatre, ...

''Proposed mentor : TheDJ''

=== RTSP ===

''Proposed mentor: jpsaman

== Other Ideas SoC 2007 ==

=== Matroska (mkv) muxing ===
robUx4 can do the mentoring. He already wrote the demux and knows mkv really well.
But this muxer may be better suited for a FFMPEG project, and we should adapt ourselves after that.

=== VLM Schedule rework ===

=== WinCE port ===

=== Mini Projects - More ideas ===

We have a more general page for ideas for Project in {{VLC}}, that could give you ideas: [[Mini_Projects]].

== Questions? Contact us ? ==
If you need to contact us, you can use this [[Talk:SoC_2007| Talk page]], use the vlc-devel mailing list, or contact one of the mentors or [[User:J-b| Jean-Baptiste Kempf]]

Main Page

2007-03-07T23:09:33Z

The DJ: i'm not sure why this Dev corner box was shifted up so high, but it looks really bad on Safari

__NOTOC__
__NOEDITSECTION__

{|style="width:100%;margin-top:0px;background-color:#fcfcfc;border:1px solid #ccc"
|style="width:56%;color:#000"|
{|style="width:280px;border:solid 0px;background:none"
|-
|style="width:280px;text-align:center;white-space:nowrap;color:#000" |
<div style="font-size:162%;border:none;margin: 0;padding:.1em;color:#000">Welcome to [[Main_Page|Videolan's Wiki]],</div>
<div style="top:+0.2em;font-size: 95%">The reference documentation and tips on VideoLAN's projects.</div>
<div id="articlecount" style="width:100%;text-align:center;font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>
|}
|style="width:11%;font-size:95%;color:#000" valign="top"|
*[[VideoLAN|VideoLAN]]
*[[VLC|VLC media player]]
*[[Documentation:Documentation|Documentation]]
|style="width:14%;font-size:95%" valign="top"|
*[http://www.videolan.org Main Site]
*[http://forum.videolan.org Forum]
*[http://planet.videolan.org News from developers]
|style="width:18%;font-size:95%" valign="top"|
*[http://developers.videolan.org Developer's website]
*[http://nightlies.videolan.org Latest builds]
*[http://trac.videolan.org Trac, Bugs, SVN and roadmap]
|}


{|
|- valign="top"
|width="35%" rowspan="2"|<div style="color:#000;background-color:#f5fffa;border:1px solid #a3bfb1;padding:10px;margin:6px; float: left;">
<h2 style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">
What is VideoLAN ?</h2>

'''VideoLAN''' is an Open Source team and a ''community'' that develop and support video projects.

'''VideoLAN''' produces free software projects under the [http://www.gnu.org/copyleft/gpl.html GNU General Public License].

== VideoLAN infos ==
See how you can [[contact VideoLAN|contact]] the team.

* [[Intellectual Properties| Intellectual Properties, trademarks]]
* [[FAQ]]
* Find out [[We Use VideoLAN|who uses VideoLAN]]
* [[VideoLAN in the News]]
* [[VideoLAN Design| Design and goodies]]
* [[VideoLAN_Sites| VideoLAN's websites]]

== VideoLAN projects ==
Here is a short list of the main [[VideoLAN projects|projects]] hosted by the VideoLAN project:
* [[VLC|VLC media player]], the core and main program, is a complete video solution that is a player, a live transcoder and a streamer.
* [[VLS]] is a streaming server, used for professional streaming solutions. {{VLC}} can now do the same. ''VLS is deprecated and unmaintained''.
* [[MiniSAPServer]] is a SAP server.
* [[x264]], a free [[H264]] / AVC encoder.

=== Libraries ===
* [http://en.wikipedia.org/wiki/Libdvdcss libdvdcss], a C library to access DVDs without having to bother about the decryption.
* [[libdvbpsi]], a C library to decode and generate MPEG TS and DVB PSI tables.
* [http://en.wikipedia.org/wiki/Libdca libdca], a DTS Coherent Acoustics decoder.

Discover also [[VideoLAN projects|lesser known projects]].
</div>

|width="35%" rowspan="1" valign="top"|<div style="color:#000;background-color:#f5fffa;border:1px solid #cedff2;padding:10px;margin: 6px">

<h2 style="margin:0;background:#cedff2;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;">VLC media player {{VLC:latest_version}}</h2>

'''[http://www.videolan.org/vlc/ Download VLC!]'''

[[VLC| What is VLC media player ??]]

* Checkout all the ''possibilities'' of [[What can vlc do?|what VLC can do]]

* Want to know [[how to|HOW TO]] do things with VLC?
* Get help with some [[Common Problems]]
* View some of VLC's [[Awards]]

== VLC on your platform... ==
{|style="border-spacing:0px;margin:0px 0px"
|style="width:50%;vertical-align:top;color:#000"|
* [[MacOSX|Mac OS X]]
* [[Windows]]
* [[BeOS]]
|
* [[Linux|GNU/Linux]]
* [[FreeBSD]]
* [[WinCE]]
|}

== Tips and Tricks ==
* You can download extra [[Skins]] for VLC
* Add different [[Interface | interfaces]] to control VLC in different ways, such as from [[Mouse Gestures|mouse gestures]] or even [[Web_Interface|through the internet]].
* [[Uncommon uses|Mad things you can do with VLC]]
* [[Notes about other clients]] (Interoperability)
</div>

|width="30%" valign="top"|
<div style="border: 1px solid #ddcef2; color: #000; background-color: #faf5ff ; padding: 10px; margin: 6px;">

<h2 style="margin:0;background:#ddcef2;font-size:120%;font-weight:bold;border:1px solid #afa3bf;text-align:left;color:#000;padding:0.2em 0.4em;">Support / Get Help</h2>
=== [[Documentation:Documentation|Official Documentation]] ===

=== Knowledge Base ===

Our [[Knowledge Base]] has information on
* [[Codec]]s
* [[Fileformat|Files]]
* [[Dictionary]]
* [[Knowledge Base|more »]]

=== [[FAQ]] ===

</div>
<div style="margin:6px;border: 1px solid #FFA8D3;background-color:#FFECF5; color: #000; padding:10px; margin-top:12px">

<h2 style="margin:0; background-color:#FFA8D3;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em .4em;"> Help the project</h2>
In this section, you can find how you can help and participate to the VideoLAN project, you being a programmer or not.

* [[Help VideoLAN]]
* [http://forum.videolan.org/viewforum.php?f=18 Help topic on the forum]
* [[Quality | Quality Team]]

</div>
|-
|colspan="2" valign="top"|

<div style="border: 1px solid #f2e0ce; color: #000; background-color: #fffaf5; padding:10px; margin: 6px; margin-top: 0px;">

<h2 style="margin:0; background-color:#f2e0ce;font-size:120%;font-weight:bold;border:1px solid #bfb1a3;text-align:left;color:#000;padding:0.2em .4em;"> Developers Corner </h2>

VideoLAN is also a development community that you can join.

You can help videolan by developing, doing artwork, doing translations ...

The [[Developers Corner]] contains various information relative to development: Howtos, work in progress, ...
</div>
|}

== Edit the Wiki! ==

Please note that to modify the content of the Wiki, or to submit articles or FAQ questions, you need to be identified.

Please create an account, this is very fast.

'''Checkout the special [[VideoLANWiki:Syntax | VideoLAN wiki syntax]] for this wiki.'''

Feel free to add to this site, however, keep content appropriate and useful. This is not the place to report bugs or to request help.
[http://www.videolan.org/support/bug-reporting.html See our info on bug reporting].

You can try the wiki syntax in the [[Sandbox]], the test page.

VLC Developers Corner

2007-03-05T21:17:47Z

The DJ: complaints

__NOTOC__
__NOEDITSECTION__

{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc"
|style="width:56%;color:#000"|
{|style="width:280px;border:solid 0px;background:none"
|-
|style="width:280px;text-align:center;white-space:nowrap;color:#000" |
<div style="font-size:162%;border:none;margin: 0;padding:.1em;color:#000">Welcome to [[Developers_Corner|VideoLAN Developers Corner]],</div>
<div style="top:+0.2em;font-size: 95%"> This is a directory of everything to do with the development of VideoLAN's projects.<br />
Check [[VLC|VLC's page]] to get info on VLC.
</div>
<div id="articlecount" style="width:100%;text-align:center;font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>
|}
|style="width:11%;font-size:95%;color:#000" valign="top"|
*[[VideoLAN|VideoLAN]]
*[[VLC|VLC media player]]
*[[Documentation:Documentation|Documentation]]
*[[VideoLAN_Sites#Developers|Developers' Websites]]
|style="width:14%;font-size:95%" valign="top"|
* [http://developers.videolan.org Main Developers Site]
* [http://nightlies.videolan.org Nightly builds]
* [http://buildbot.videolan.org Buildbot for Automatic Builds]
|style="width:18%;font-size:95%" valign="top"|
* [http://trac.videolan.org Trac, bugs, features, roadmap]
* [http://mirrors.videolan.org Mirrors check]
* [ftp://ftp.videolan.org/pub/videolan/ Main FTP]
|}


{|
|- valign="top" width="100%"

|width="30%" valign="top"|
<div style="border: 1px solid #ddcef2; color: #000; background-color: #faf5ff ; padding: 10px; margin: 6px;">

<h2 style="margin:0;background:#ddcef2;font-size:120%;font-weight:bold;border:1px solid #afa3bf;text-align:left;color:#000;padding:0.2em 0.4em;">
VideoLAN other projects</h2>
Here is a short list of the main [[VideoLAN projects|projects]] hosted by the VideoLAN project:
* [[VLS]] is a streaming server, used for professional streaming solutions. [[VLC|VLC]] can now do the same. ''VLS is deprecated and unmaintained''.
* [[MiniSAPServer]] is a SAP server.
* [[x264]], a free [[H264]] / AVC encoder.

=== Libraries ===
* [http://en.wikipedia.org/wiki/Libdvdcss libdvdcss], a C library to access DVDs without having to bother about the decryption.
* [[libdvbpsi]], a C library to decode and generate MPEG TS and DVB PSI tables.
* [http://en.wikipedia.org/wiki/Libdca libdca], a DTS Coherent Acoustics decoder.

Discover also [[VideoLAN projects|lesser known projects]].
</div>

<div style="color:#000;background-color:#f5fffa;border:1px solid #a3bfb1;padding:10px;margin:6px; float: left;">
<h2 style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">
Build an application on VLC</h2>
There are several ways to build an application that uses VLC. Some are listed here.
* Build a GPL application using libvlc, in C/C++/[[C_Sharp|C#]]
* Use the python bindings [[MediaControlIDL]]
* Use the java bindings
* Use the ActiveX Controls
* Use the JavaScript API
* Talk to VLC through the [[DBus]] communication
</div>

|width="35%" rowspan="1" valign="top"|<div style="color:#000;background-color:#f5fffa;border:1px solid #cedff2;padding:10px;margin: 6px">

<h2 style="margin:0;background:#cedff2;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;">
Build VLC media player</h2>
Check the [http://trac.videolan.org/vlc/browser/trunk/NEWS?format=raw NEWS].

Check the [[Compile|generic compile HOWTO]].

To build VLC, you first need to get the [[GetTheSource|Source Code]].

* [[UnixCompile|How to compile on Unix/Linux]]
* [[Win32Compile|How to compile on Windows]]
* [[Win32CompileCygwin|How to compile on Windows using Cygwin]]
* [[Win32CompileMSYS|How to compile on Windows using MSYS]]
* [[OSXCompile|How to compile on Mac OS X]]
* [[BeOSCompile|How to compile on BeOS]]
* [[ARM-XCompile|How to cross-compile for ARM]]

* [[DirectFB_Compile|Compile DirectFB plugin]]
* [[Contrib_Status|Contrib Status]] - 3rd party libraries status.
* Diego 'Flameeyes' Pettenò 's [http://www.gentoo.org/proj/en/desktop/video/vlc.xml notes] about packaging VLC into [http://www.gentoo.org/ Gentoo].
</div>

<div style="margin:6px;border: 1px solid #FFA8D3;background-color:#FFECF5; color: #000; padding:10px; margin-top:12px">

<h2 style="margin:0; background-color:#FFA8D3;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em .4em;"> Code VLC</h2>
=== Start coding on VLC ===
* [[Getting Started At Coding|Get started at coding on VLC]].
* You might be interested in our [[Mini_Projects|Mini Projects]], which are some easy tasks that do not require a lot of VLC Code Knowledge.
* It is recommended that you join the vlc-devel [http://developers.videolan.org/lists.html mailing list], where all commits are archived.

=== VLC Code ===
* [[Unicode and Strings]]
* [[Code Conventions]]
* [[Documentation:Hacker%27s_Guide|Hacker's Guide]]
* [http://developers.videolan.org/vlc/vlc/doc/doxygen/html Code documentation]
* [[VLC variables help]]

=== Tools to code VLC ===
* [[Contrib_Status|Contrib Status]] - Contrib Libraries Status
* [http://trac.videolan.org/vlc Trac] list of bugs, todo's and history of commits.
* [https://bugs.launchpad.net/products/vlc Launchpad for VLC] ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs?field.searchtext=vlc&orderby=-date_last_updated&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package= recent bug changes]) ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs all bugs])
* [http://developers.videolan.org/i18n/ Translation information and stats]
* [http://cia.navi.cx/stats/project/vlc CIA commit statistics]
* [http://paste.videolan.org Pasteboard]
* [http://buildbot.videolan.org Buildbot]
* [http://planet.videolan.org Developer weblog]
* [[Nightly_Build| Nightly Builds]]
</div>

| width="35%" rowspan="1" valign="top" |
<div style="margin:10px;border: 1px solid #f2e0ce; color: #000; background-color: #fffaf5; padding:10px; margin: 6px;">

<h2 style="margin:0; background-color:#f2e0ce;font-size:120%;font-weight:bold;border:1px solid #bfb1a3;text-align:left;color:#000;padding:0.2em .4em;"> Development discussions under work</h2>

== Current discussions ==
* [[DBus-spec]] - Specification for a Common, Desktop neutral, Media Player D-Bus interface.
* [[VoutRework|Vout Rework]] - improving the video output subsystem.
* [[telnet rc rewrite]] - Merging the "telnet" and "rc" controls.
* [[SimplePreferences|Simple Preferences]] - We wish to add a "simple" preferences mode, additionally to the full mode we already have.
* [[QtIntfTODO|Qt Interface TODO]] - A brand new qt4 interface ... in order to get rid of wxWidgets.
* [[Usability Complaints]]

=== Design ===
* [[DefaultSkinRequirements|Default Skin Requirements]] - Specifications of an eligible skin for default skin.

== Past discussions ==
* [[StatsSystem |Stats Sytem]]
* [[Browser Plugin Spec]]
* [[0.9.0PlaylistTODO|0.9.0 Playlist TODO]] - Major changes in the upcoming version
* [[InteractionSystem]] - Interaction System
* [[ExternalAPI|External API]] - improving the external API to vlc
* [[MediaControlAPI|Media Control API]] - an high level player-independent media API, wrapping around our [[ExternalAPI|External API]]
* [[0.8.5StringReview]]
* [[2005StringsReview]]

=== Design ===
* [[WebsiteRedesign|Website Redesign]] and [[WebsiteDesign|Design Proposals]]

</div>

<div style="color:#000;background-color:#f5fffa;border:1px solid #a3bfb1;padding:10px;margin:6px; float: left;">
<h2 style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">
VideoLAN's Administration</h2>
* [[Bugday|VideoLAN bugdays]]
* [[Calendar|VideoLAN calendar]]
* [[VideoLAN Servers]]
* [[Add a skin|How to add a skin on the skins download page]]
* [http://mirrors.videolan.org Download mirrors integrity tests]
=== Wiki Admins ===

* [{{SERVER}}/Special:Listusers?group=sysop Admins list]
* [[SpamBlacklist]]
* [[VideoLAN_Wiki:TODO | TODO]]
</div>

|-
|}

Usability Complains

2007-03-05T21:17:08Z

The DJ: Usability Complains moved to Usability Complaints: fix spelling

#REDIRECT [[Usability Complaints]]

Usability Complaints

2007-03-05T21:17:08Z

The DJ: Usability Complains moved to Usability Complaints: fix spelling

This page contains some usability complains for VLC.

Lets start.

* Hard-to-guess shortcuts to operate with the movie. E.g. shift+arrows to rewind. -- it could be greatly improved with arrows-only navigation. => This should be easy to do in the new interface.

* Non-responsive shortcuts in WX interface. Sometimes they simply don't work (after moving out of the fullscreen). => Qt4 does work the same way ? -- no, seems like it somewhat better in QT4, still to test more.

* Unresponsive stop/play. Video stops after some amount of time. -- kinda better in QT4 interface.

* Preferences are way too big. You can navigate thru them all the day long and you won't find what you're really looking for. => [[Simple_Preferences]]

VideoLAN Sites

2007-03-05T21:04:31Z

The DJ: /* Altair */ streams.v.o

= Sites =
== VideoLAN public sites ==
* [http://www.videolan.org Main Site]
* [http://wiki.videolan.org Wiki]
* [http://forum.videolan.org Forum]
* [http://planet.videolan.org Developers' News]
* [ftp://ftp.videolan.org/pub/videolan/ Main FTP]
* [http://paste.videolan.org/ PasteBin]
* [http://lists.videolan.org/ Files Attachments from the mailing-lists]

== Developers ==
* [http://developers.videolan.org Main Developers Site]
* [http://nightlies.videolan.org Nightly builds]
* [http://buildbot.videolan.org Buildbot for Automatic Builds]
* [http://trac.videolan.org Trac, bugs, features, roadmap]
* [http://mirrors.videolan.org Mirrors check]
* [http://downloads.videolan.org/pub/ Download Site]
* [http://stats.videolan.org Servers stats]

== Update ==
* [http://update.videolan.org VLC update site] - Non human readable site !

== Other ==
* [http://getvlcstatus.videolan.org VLC Status Page] (This is humour, of course)

= Servers =
== Ganesh ==
* ganesh.videolan.org
* developers.videolan.org
* downloads.videolan.org
* ftp.videolan.org
* forum.videolan.org
* lists.videolan.org
* mirrors.videolan.org
* planet.videolan.org
* paste.videolan.org
* stats.videolan.org
* svn.videolan.org
* trac.videolan.org
* update.videolan.org
* www.videolan.org

The primary web and FTP server

== Altair ==
* altair.videolan.org
* buildbot.videolan.org
* nightlies.videolan.org
* people.videolan.org
* streams.videolan.org

It is the dev server, that hosts the automatic builds.

== Krishna ==
It is on of VIA's servers.
* wiki.videolan.org

== Epsilon ==
*epsilon.videolan.org

Mac Intel Developer Preview machine
Also a nightly build machine for OSX Intel.

== Veda ==
*veda.student.utwente.nl
PowerMac - 1.8Ghz Dual, 750MB RAM
Primary Mac OS X PowerPC development machine. Hosts the nightly build client for the OSX PowerPC platform.

== Deneb ==
*deneb.student.utwente.nl
Imac 17" - 2Ghz DC, 1GB RAM
Primary Mac OS X Intel development machine. Hosts the nightly build client for the OSX Intel platform.

Some server pictures can be found on: http://people.videolan.org/~dionoea/servers/

{{stub}}

[[Category:About VideoLAN]]

VideoLAN Sites

2007-03-05T20:59:45Z

The DJ: add some more serverinfo.

= Sites =
== VideoLAN public sites ==
* [http://www.videolan.org Main Site]
* [http://wiki.videolan.org Wiki]
* [http://forum.videolan.org Forum]
* [http://planet.videolan.org Developers' News]
* [ftp://ftp.videolan.org/pub/videolan/ Main FTP]
* [http://paste.videolan.org/ PasteBin]
* [http://lists.videolan.org/ Files Attachments from the mailing-lists]

== Developers ==
* [http://developers.videolan.org Main Developers Site]
* [http://nightlies.videolan.org Nightly builds]
* [http://buildbot.videolan.org Buildbot for Automatic Builds]
* [http://trac.videolan.org Trac, bugs, features, roadmap]
* [http://mirrors.videolan.org Mirrors check]
* [http://downloads.videolan.org/pub/ Download Site]
* [http://stats.videolan.org Servers stats]

== Update ==
* [http://update.videolan.org VLC update site] - Non human readable site !

== Other ==
* [http://getvlcstatus.videolan.org VLC Status Page] (This is humour, of course)

= Servers =
== Ganesh ==
* ganesh.videolan.org
* developers.videolan.org
* downloads.videolan.org
* ftp.videolan.org
* forum.videolan.org
* lists.videolan.org
* mirrors.videolan.org
* planet.videolan.org
* paste.videolan.org
* stats.videolan.org
* svn.videolan.org
* trac.videolan.org
* update.videolan.org
* www.videolan.org

The primary web and FTP server

== Altair ==
* altair.videolan.org
* buildbot.videolan.org
* nightlies.videolan.org
* people.videolan.org

It is the dev server, that hosts the automatic builds.

== Krishna ==
It is on of VIA's servers.
* wiki.videolan.org

== Epsilon ==
*epsilon.videolan.org

Mac Intel Developer Preview machine
Also a nightly build machine for OSX Intel.

== Veda ==
*veda.student.utwente.nl
PowerMac - 1.8Ghz Dual, 750MB RAM
Primary Mac OS X PowerPC development machine. Hosts the nightly build client for the OSX PowerPC platform.

== Deneb ==
*deneb.student.utwente.nl
Imac 17" - 2Ghz DC, 1GB RAM
Primary Mac OS X Intel development machine. Hosts the nightly build client for the OSX Intel platform.

Some server pictures can be found on: http://people.videolan.org/~dionoea/servers/

{{stub}}

[[Category:About VideoLAN]]

VLC Developers Corner

2007-03-05T20:40:11Z

The DJ: spelling

__NOTOC__
__NOEDITSECTION__

{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc"
|style="width:56%;color:#000"|
{|style="width:280px;border:solid 0px;background:none"
|-
|style="width:280px;text-align:center;white-space:nowrap;color:#000" |
<div style="font-size:162%;border:none;margin: 0;padding:.1em;color:#000">Welcome to [[Developers_Corner|VideoLAN Developers Corner]],</div>
<div style="top:+0.2em;font-size: 95%"> This is a directory of everything to do with the development of VideoLAN's projects.<br />
Check [[VLC|VLC's page]] to get info on VLC.
</div>
<div id="articlecount" style="width:100%;text-align:center;font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>
|}
|style="width:11%;font-size:95%;color:#000" valign="top"|
*[[VideoLAN|VideoLAN]]
*[[VLC|VLC media player]]
*[[Documentation:Documentation|Documentation]]
*[[VideoLAN_Sites#Developers|Developers' Websites]]
|style="width:14%;font-size:95%" valign="top"|
* [http://developers.videolan.org Main Developers Site]
* [http://nightlies.videolan.org Nightly builds]
* [http://buildbot.videolan.org Buildbot for Automatic Builds]
|style="width:18%;font-size:95%" valign="top"|
* [http://trac.videolan.org Trac, bugs, features, roadmap]
* [http://mirrors.videolan.org Mirrors check]
* [ftp://ftp.videolan.org/pub/videolan/ Main FTP]
|}


{|
|- valign="top" width="100%"

|width="30%" valign="top"|
<div style="border: 1px solid #ddcef2; color: #000; background-color: #faf5ff ; padding: 10px; margin: 6px;">

<h2 style="margin:0;background:#ddcef2;font-size:120%;font-weight:bold;border:1px solid #afa3bf;text-align:left;color:#000;padding:0.2em 0.4em;">
VideoLAN other projects</h2>
Here is a short list of the main [[VideoLAN projects|projects]] hosted by the VideoLAN project:
* [[VLS]] is a streaming server, used for professional streaming solutions. [[VLC|VLC]] can now do the same. ''VLS is deprecated and unmaintained''.
* [[MiniSAPServer]] is a SAP server.
* [[x264]], a free [[H264]] / AVC encoder.

=== Libraries ===
* [http://en.wikipedia.org/wiki/Libdvdcss libdvdcss], a C library to access DVDs without having to bother about the decryption.
* [[libdvbpsi]], a C library to decode and generate MPEG TS and DVB PSI tables.
* [http://en.wikipedia.org/wiki/Libdca libdca], a DTS Coherent Acoustics decoder.

Discover also [[VideoLAN projects|lesser known projects]].
</div>

<div style="color:#000;background-color:#f5fffa;border:1px solid #a3bfb1;padding:10px;margin:6px; float: left;">
<h2 style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">
Build an application on VLC</h2>
There are several ways to build an application that uses VLC. Some are listed here.
* Build a GPL application using libvlc, in C/C++/[[C_Sharp|C#]]
* Use the python bindings [[MediaControlIDL]]
* Use the java bindings
* Use the ActiveX Controls
* Use the JavaScript API
* Talk to VLC through the [[DBus]] communication
</div>

|width="35%" rowspan="1" valign="top"|<div style="color:#000;background-color:#f5fffa;border:1px solid #cedff2;padding:10px;margin: 6px">

<h2 style="margin:0;background:#cedff2;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;">
Build VLC media player</h2>
Check the [http://trac.videolan.org/vlc/browser/trunk/NEWS?format=raw NEWS].

Check the [[Compile|generic compile HOWTO]].

To build VLC, you first need to get the [[GetTheSource|Source Code]].

* [[UnixCompile|How to compile on Unix/Linux]]
* [[Win32Compile|How to compile on Windows]]
* [[Win32CompileCygwin|How to compile on Windows using Cygwin]]
* [[Win32CompileMSYS|How to compile on Windows using MSYS]]
* [[OSXCompile|How to compile on Mac OS X]]
* [[BeOSCompile|How to compile on BeOS]]
* [[ARM-XCompile|How to cross-compile for ARM]]

* [[DirectFB_Compile|Compile DirectFB plugin]]
* [[Contrib_Status|Contrib Status]] - 3rd party libraries status.
* Diego 'Flameeyes' Pettenò 's [http://www.gentoo.org/proj/en/desktop/video/vlc.xml notes] about packaging VLC into [http://www.gentoo.org/ Gentoo].
</div>

<div style="margin:6px;border: 1px solid #FFA8D3;background-color:#FFECF5; color: #000; padding:10px; margin-top:12px">

<h2 style="margin:0; background-color:#FFA8D3;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em .4em;"> Code VLC</h2>
=== Start coding on VLC ===
* [[Getting Started At Coding|Get started at coding on VLC]].
* You might be interested in our [[Mini_Projects|Mini Projects]], which are some easy tasks that do not require a lot of VLC Code Knowledge.
* It is recommended that you join the vlc-devel [http://developers.videolan.org/lists.html mailing list], where all commits are archived.

=== VLC Code ===
* [[Unicode and Strings]]
* [[Code Conventions]]
* [[Documentation:Hacker%27s_Guide|Hacker's Guide]]
* [http://developers.videolan.org/vlc/vlc/doc/doxygen/html Code documentation]
* [[VLC variables help]]

=== Tools to code VLC ===
* [[Contrib_Status|Contrib Status]] - Contrib Libraries Status
* [http://trac.videolan.org/vlc Trac] list of bugs, todo's and history of commits.
* [https://bugs.launchpad.net/products/vlc Launchpad for VLC] ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs?field.searchtext=vlc&orderby=-date_last_updated&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package= recent bug changes]) ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs all bugs])
* [http://developers.videolan.org/i18n/ Translation information and stats]
* [http://cia.navi.cx/stats/project/vlc CIA commit statistics]
* [http://paste.videolan.org Pasteboard]
* [http://buildbot.videolan.org Buildbot]
* [http://planet.videolan.org Developer weblog]
* [[Nightly_Build| Nightly Builds]]
</div>

| width="35%" rowspan="1" valign="top" |
<div style="margin:10px;border: 1px solid #f2e0ce; color: #000; background-color: #fffaf5; padding:10px; margin: 6px;">

<h2 style="margin:0; background-color:#f2e0ce;font-size:120%;font-weight:bold;border:1px solid #bfb1a3;text-align:left;color:#000;padding:0.2em .4em;"> Development discussions under work</h2>

== Current discussions ==
* [[DBus-spec]] - Specification for a Common, Desktop neutral, Media Player D-Bus interface.
* [[VoutRework|Vout Rework]] - improving the video output subsystem.
* [[telnet rc rewrite]] - Merging the "telnet" and "rc" controls.
* [[SimplePreferences|Simple Preferences]] - We wish to add a "simple" preferences mode, additionally to the full mode we already have.
* [[QtIntfTODO|Qt Interface TODO]] - A brand new qt4 interface ... in order to get rid of wxWidgets.
* [[Usability Complains]]

=== Design ===
* [[DefaultSkinRequirements|Default Skin Requirements]] - Specifications of an eligible skin for default skin.

== Past discussions ==
* [[StatsSystem |Stats Sytem]]
* [[Browser Plugin Spec]]
* [[0.9.0PlaylistTODO|0.9.0 Playlist TODO]] - Major changes in the upcoming version
* [[InteractionSystem]] - Interaction System
* [[ExternalAPI|External API]] - improving the external API to vlc
* [[MediaControlAPI|Media Control API]] - an high level player-independent media API, wrapping around our [[ExternalAPI|External API]]
* [[0.8.5StringReview]]
* [[2005StringsReview]]

=== Design ===
* [[WebsiteRedesign|Website Redesign]] and [[WebsiteDesign|Design Proposals]]

</div>

<div style="color:#000;background-color:#f5fffa;border:1px solid #a3bfb1;padding:10px;margin:6px; float: left;">
<h2 style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">
VideoLAN's Administration</h2>
* [[Bugday|VideoLAN bugdays]]
* [[Calendar|VideoLAN calendar]]
* [[VideoLAN Servers]]
* [[Add a skin|How to add a skin on the skins download page]]
* [http://mirrors.videolan.org Download mirrors integrity tests]
=== Wiki Admins ===

* [{{SERVER}}/Special:Listusers?group=sysop Admins list]
* [[SpamBlacklist]]
* [[VideoLAN_Wiki:TODO | TODO]]
</div>

|-
|}

VLC Developers Corner

2007-03-05T20:05:52Z

The DJ: add bugday and calender

__NOTOC__
__NOEDITSECTION__

{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc"
|style="width:56%;color:#000"|
{|style="width:280px;border:solid 0px;background:none"
|-
|style="width:280px;text-align:center;white-space:nowrap;color:#000" |
<div style="font-size:162%;border:none;margin: 0;padding:.1em;color:#000">Welcome to [[Developers_Corner|VideoLAN Developers Corner]],</div>
<div style="top:+0.2em;font-size: 95%"> This is a directory of everything to do with the development of VideoLAN's projects.<br />
Check [[VLC|VLC's page]] to get info on VLC.
</div>
<div id="articlecount" style="width:100%;text-align:center;font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>
|}
|style="width:11%;font-size:95%;color:#000" valign="top"|
*[[VideoLAN|VideoLAN]]
*[[VLC|VLC media player]]
*[[Documentation:Documentation|Documentation]]
*[[VideoLAN_Sites#Developers|Developers' Websites]]
|style="width:14%;font-size:95%" valign="top"|
* [http://developers.videolan.org Main Developers Site]
* [http://nightlies.videolan.org Nightly builds]
* [http://buildbot.videolan.org Buildbot for Automatic Builds]
|style="width:18%;font-size:95%" valign="top"|
* [http://trac.videolan.org Trac, bugs, features, roadmap]
* [http://mirrors.videolan.org Mirrors check]
* [ftp://ftp.videolan.org/pub/videolan/ Main FTP]
|}


{|
|- valign="top" width="100%"

|width="30%" valign="top"|
<div style="border: 1px solid #ddcef2; color: #000; background-color: #faf5ff ; padding: 10px; margin: 6px;">

<h2 style="margin:0;background:#ddcef2;font-size:120%;font-weight:bold;border:1px solid #afa3bf;text-align:left;color:#000;padding:0.2em 0.4em;">
VideoLAN other projects</h2>
Here is a short list of the main [[VideoLAN projects|projects]] hosted by the VideoLAN project:
* [[VLS]] is a streaming server, used for professional streaming solutions. [[VLC|VLC]] can now do the same. ''VLS is deprecated and unmaintained''.
* [[MiniSAPServer]] is a SAP server.
* [[x264]], a free [[H264]] / AVC encoder.

=== Libraries ===
* [http://en.wikipedia.org/wiki/Libdvdcss libdvdcss], a C library to access DVDs without having to bother about the decryption.
* [[libdvbpsi]], a C library to decode and generate MPEG TS and DVB PSI tables.
* [http://en.wikipedia.org/wiki/Libdca libdca], a DTS Coherent Acoustics decoder.

Discover also [[VideoLAN projects|lesser known projects]].
</div>

<div style="color:#000;background-color:#f5fffa;border:1px solid #a3bfb1;padding:10px;margin:6px; float: left;">
<h2 style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">
Build an application on VLC</h2>
There are several ways to build an application that uses VLC. Some are listed here.
* Build a GPL application using libvlc, in C/C++/[[C_Sharp|C#]]
* Use the python bindings [[MediaControlIDL]]
* Use the java bindings
* Use the ActiveX Controls
* Use the JavaScript API
* Talk to VLC through the [[DBus]] communication
</div>

|width="35%" rowspan="1" valign="top"|<div style="color:#000;background-color:#f5fffa;border:1px solid #cedff2;padding:10px;margin: 6px">

<h2 style="margin:0;background:#cedff2;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;">
Build VLC media player</h2>
Check the [http://trac.videolan.org/vlc/browser/trunk/NEWS?format=raw NEWS].

Check the [[Compile|generic compile HOWTO]].

To build VLC, you first need to get the [[GetTheSource|Source Code]].

* [[UnixCompile|How to compile on Unix/Linux]]
* [[Win32Compile|How to compile on Windows]]
* [[Win32CompileCygwin|How to compile on Windows using Cygwin]]
* [[Win32CompileMSYS|How to compile on Windows using MSYS]]
* [[OSXCompile|How to compile on Mac OS X]]
* [[BeOSCompile|How to compile on BeOS]]
* [[ARM-XCompile|How to cross-compile for ARM]]

* [[DirectFB_Compile|Compile DirectFB plugin]]
* [[Contrib_Status|Contrib Status]] - 3rd party libraries status.
* Diego 'Flameeyes' Pettenò 's [http://www.gentoo.org/proj/en/desktop/video/vlc.xml notes] about packaging VLC into [http://www.gentoo.org/ Gentoo].
</div>

<div style="margin:6px;border: 1px solid #FFA8D3;background-color:#FFECF5; color: #000; padding:10px; margin-top:12px">

<h2 style="margin:0; background-color:#FFA8D3;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em .4em;"> Code VLC</h2>
=== Start coding on VLC ===
* [[Getting Started At Coding|Get started at coding on VLC]].
* You might be interested in our [[Mini_Projects|Mini Projects]], which are some easy tasks that do not require a lot of VLC Code Knowledge.
* It is recommended that you join the vlc-devel [http://developers.videolan.org/lists.html mailing list], where all commits are archived.

=== VLC Code ===
* [[Unicode and Strings]]
* [[Code Conventions]]
* [[Documentation:Hacker%27s_Guide|Hacker's Guide]]
* [http://developers.videolan.org/vlc/vlc/doc/doxygen/html Code documentation]
* [[VLC variables help]]

=== Tools to code VLC ===
* [[Contrib_Status|Contrib Status]] - Contrib Libraries Status
* [http://trac.videolan.org/vlc Trac] list of bugs, todo's and history of commits.
* [https://bugs.launchpad.net/products/vlc Launchpad for VLC] ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs?field.searchtext=vlc&orderby=-date_last_updated&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package= recent bug changes]) ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs all bugs])
* [http://developers.videolan.org/i18n/ Translation information and stats]
* [http://cia.navi.cx/stats/project/vlc CIA commit statistics]
* [http://paste.videolan.org Pasteboard]
* [http://buildbot.videolan.org Buildbot]
* [http://planet.videolan.org Developer weblog]
* [[Nightly_Build| Nightly Builds]]
</div>

| width="35%" rowspan="1" valign="top" |
<div style="margin:10px;border: 1px solid #f2e0ce; color: #000; background-color: #fffaf5; padding:10px; margin: 6px;">

<h2 style="margin:0; background-color:#f2e0ce;font-size:120%;font-weight:bold;border:1px solid #bfb1a3;text-align:left;color:#000;padding:0.2em .4em;"> Development discussions under work</h2>

== Current discussions ==
* [[DBus-spec]] - Specification for a Common, Desktop neutral, Media Player D-Bus interface.
* [[VoutRework|Vout Rework]] - improving the video output subsystem.
* [[telnet rc rewrite]] - Merging the "telnet" and "rc" controls.
* [[SimplePreferences|Simple Preferences]] - We wish to add a "simple" preferences mode, additionally to the full mode we already have.
* [[QtIntfTODO|Qt Interface TODO]] - A brand new qt4 interface ... in order to get rid of wxWidgets.
* [[Usability Complains]]

=== Design ===
* [[DefaultSkinRequirements|Default Skin Requirements]] - Specifications of an eligible skin for default skin.

== Past discussions ==
* [[StatsSystem |Stats Sytem]]
* [[Browser Plugin Spec]]
* [[0.9.0PlaylistTODO|0.9.0 Playlist TODO]] - Major changes in the upcoming version
* [[InteractionSystem]] - Interaction System
* [[ExternalAPI|External API]] - improving the external API to vlc
* [[MediaControlAPI|Media Control API]] - an high level player-independent media API, wrapping around our [[ExternalAPI|External API]]
* [[0.8.5StringReview]]
* [[2005StringsReview]]

=== Design ===
* [[WebsiteRedesign|Website Redesign]] and [[WebsiteDesign|Design Proposals]]

</div>

<div style="color:#000;background-color:#f5fffa;border:1px solid #a3bfb1;padding:10px;margin:6px; float: left;">
<h2 style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;">
VideoLAN's Administration</h2>
* [[Bugday|VideoLAN bugdays]]
* [[Calender|VideoLAN calender]]
* [[VideoLAN Servers]]
* [[Add a skin|How to add a skin on the skins download page]]
* [http://mirrors.videolan.org Download mirrors integrity tests]
=== Wiki Admins ===

* [{{SERVER}}/Special:Listusers?group=sysop Admins list]
* [[SpamBlacklist]]
* [[VideoLAN_Wiki:TODO | TODO]]
</div>

|-
|}

Hardware Compatibility list

2006-12-06T01:58:15Z

The DJ: /* Capture Cards */ PVR-150 update

{{stub}}

Please add hardware known to work with [[VLC]]. Don't forget to specify the Operating System you know it to work on.

== Capture Cards ==
{| class="wikitable"
! Product || Vendor || Format || OS || Notes
|-
| Hauppauge WinTV 38101 || Hauppauge || Analog || Windows XP DirectShow || Set "Video input chroma format" to "RV24"
|-
| Hauppauge WinTV-PVR-150 || Hauppauge || Analog || Linux (using v4l2) / Windows (using DirectShow) || MPEG2 capture on windows possibly broken: "I have the same problem being unable to stream directly from my Hauppauge PVR 150 to the network. It looks like VLC tries to connect to a wrong output-pin of the "Hauppauge WinTV PVR PCI II Capture" filter called "Capture" (see log "trying pin Capture" ...). When building a filter graph using graphedit I use the output pin "656" and connect it to a filter called "Hauppauge WinTV PVR PCI II Encoder" which has an input pin called "656" and and MPEG output pin. This works fine in graphedit - I get MPEG video and audio this way. "
|-
| Hauppauge WinTV-PVR-250 || Hauppauge || Analog || Linux (using v4l2) / Windows (using DirectShow)||
|-
| Hauppauge WinTV-PVR-350 || Hauppauge || Analog || Linux (using v4l2) / Windows (using DirectShow)||
|-
| Hauppauge WinTV-Nova-S-CI PCI || Hauppauge || Satellite [[DVB-S]] || Linux || Bridge: Philips SAA7146A
|-
| Hauppauge WinTV-Nova-S PCI || Hauppauge || Satellite [[DVB-S]] || Linux || Bridge: Philips SAA7146A
|-
| Hauppauge WinTV-Nova-T PCI || Hauppauge || Terrestrial [[DVB-T]] || Linux || Bridge: Philips SAA7146A; Demodulator: Philips TDA 10045
|-
| Hauppauge WinTV-Nova-T USB2|| Hauppauge || Terrestrial [[DVB-T]] || Linux ||
|-
| Avermedia AVerTV DVB-T 771 || Avermedia || Terrestrial [[DVB-T]] || Linux (using VLS or VLC) || Bridge: Brooktree bt878 (Conexant fusion 878A); Demodulator: MT352 (Samsung MT352CG)
|-
| Avermedia AVerTV Studio 307 || Avermedia || Analo) || Linux (using v4l2) ||
|-
| Avermedia TvPhone/Capture 98 || Avermedia || Analog Tuner/S-video/Composite || Windows XP Pro +SP1 || Chipset: Philips Bt878, Drivers: Standart Conexant WDM drivers, Stream: 320x240/400x300, MJPG/WMV2, MP3, NO MUXER
|-
| PixelView Bt878p+ || PixelView || Analog || Windows / Linux (using v4l2) ||
|-
| Technisat AirStar 2 || Technisat || Terrestrial [[DVB-T]] || Linux (using VLS or VLC) || Bridge: B2C2 FlexCop Chipset; Demodulator: ST MT352
|-
| Technisat SkyStar 2 || Technisat || Satellite [[DVB-S]] || Linux (using VLC) ||
|-
| Technisat CableStar 2 || Technisat || Cable [[DVB-C]] || Linux (using VLC) ||
|-
| ATI Rage 128 Pro AIW || ATI Technologies || Analog || Windows 2000 DirectShow (not XP) || Must enter "YUV12" into the "Video input chroma format" field in the "Advanced options (DirectShow input)" dialog
|-
| ATI AIW 9800 PRO || ATI Technologies || Analog || Windows || uses ATI Rage Threatre chip, software decoder
|-
| Winfast TV2000/Expert || Leadtek || Analog Tuner/S-video/Composite || Windows XP Pro || Chipset: CX2388X 10bit ADC
|-
| Osprey 230 || Viewsonic || Composite/S-Video || Windows XP/2000 DirectShow || Simulstream works with multiple VLC streams & VLM
|-
| DVC100 (Dazzle, Rev:1.1) || Pinnacle || Composite/S-Video || Windows XP DirectShow || No sound, only picture. Pinnacle support giving no solution (09/2006)

|-
| Travel TV (PCMCIA/Cardbus) || Chronos || Analog Tuner/S-video/Composite || Linux (using v4l2) || Chipset: Philips SAA7134, not autodetected, use modprobe with card=67 (Behold)
|}

Related topics: [[How to Use a Capture Card]]

Useful Linux links: [http://www.linuxtv.org/ LinuxTV] and [http://ivtvdriver.org/ IVTV]

== Appliance Encoders ==

{| class="wikitable"
! Product || Vendor || Opinion || OS || Contact
|-
| VBrick MPEG2 || VBrick || Main Level, Main Profile 4:2:0. ISMA SAP announcements supported by VLC || Windows/MacOSX/Linux || http://www.vbrick.com (US) http://www.techex.co.uk (Europe)
|-
| VBrick MPEG4 || VBrick || MPEG4 RTSP stream works, ISMA SAP announcements supported by VLC || Windows/MacOSX/Linux || http://www.vbrick.com (US) http://www.techex.co.uk (Europe)
|}

== IP Cameras ==
{| class="wikitable"
! Product || Vendor || Opinion || OS
|-
| Axis 230 MPEG-2 || Axis || http stream works fine with VLC || Windows/MacOSX/Linux...
|-
| Axis 207 || Axis || MPEG4 rtsp stream also works fine || Windows/MacOSX/Linux...
|}

== Webcams (USB) ==
{| class="wikitable"
! Product || Vendor || Opinion || OS
|-
| StarCam 370i || MSI || udp stream works fine with VLC || Windows
|-
| 150 Spacecam Portable || Trust || works with VLC || Windows

|}

Knowledge Base

2006-12-06T01:52:17Z

The DJ: make this more prominent

This page is the starting point for the VideoLAN Knowledge Base. Its goal is to document as much information about codecs, fileformats, protocols etc. Although mainly consisting of technical information, it is intended to be easily understandible by all users. It is something like a dictionary or a encyclopedia on video/audio streaming/playing. We can then link to these definitions from our user documentation and stuff.

Mike Melanson and Diego Biurrun from the FFmpeg project also started the [http://wiki.multimedia.cx/ MultimediaWiki] where you can find tons of information about multimedia technology, and mostly about codecs.

* '''[[Codec]]'''
: About audio and video formats, like DivX and AC2
* '''[[Fileformat]]'''
: About different file types, like .avi and .mpg
* '''[[Protocols]]'''
: How data is sent from one place to another
* '''[[Dictionary]]'''
: Look up VideoLAN related words and concepts
* '''[[Players]]'''
: Other Multimedia Software
* '''[[Companies]]'''
: Software companies related (or not related) to VideoLAN
* '''[[Links]]'''
: Related web links
* '''[[Servers]]'''
: VLS, VLC and server software and hardware
* '''[[Projects]]'''
: 3rd party projects related to VideoLAN
* '''[[History|A brief history of VideoLAN]]'''
: About VideoLAN
* '''[[Video Output]]'''
: Different ways to display output
* '''[[Interface]]s'''
: Different ways to control VLC
* '''[[Buying Media to Play with VLC]]'''
: How to get [[DRM]]-free music.
* '''[[Hardware Compatibility list]]'''
: Hardware that works with VLC/VLS.

Hacker Guide

2006-12-06T01:50:31Z

The DJ: warning that this isn't finished

<div style="background:red;">
This guide is still being construced. Please see http://developers.videolan.org/vlc/ for the current information
</div>
===Authors===
* Derk-Jan Hartman

==Introduction==
* What is this?
* What you need to know about VLC

==The many layers of VLC==
* Core
* Access
* Demux
* Packetizers
* Codec
* Stream Output
* Interfaces
* Audio/Video Output
* VLM
* Filters

==VLC source code overview==
* VLC sourcetree
* VLC modules
* VLC objects
* VLC preferences
* VLC variables

==Coding for VLC==
* Coding style
* Adding a module
* Using libvlc
* Bindings

{{Documentation}}

VLC Developers Corner

2006-12-06T01:47:12Z

The DJ:

__NOTOC__

Welcome to VLC's developers corner. This is a directory of everything to do with the development of VLC. If you are looking for information about downloading or using VLC, you should have a look at [http://www.videolan.org our website].

{| cellspacing="3"
|- valign="top"
|width="40%" class="MainPageBG" style="border: 1px solid #ffc9c9; color: #000; background-color: #fff3f3"|

=== Compiling VLC ===

To compile VLC, you first need to get the [[GetTheSource|Source Code]].

* [[UnixCompile|How to compile on Unix/Linux]]
* [[Win32Compile|How to compile on Windows]]
* [[OSXCompile|How to compile on Mac OS X]]
* [[BeOSCompile|How to compile on BeOS]]

=== Rules ===
* [[Unicode and Strings]]
* [[Code Conventions]]
* [[Documentation:Hacker%27s_Guide|Hacker's Guide]]
* [http://developers.videolan.org/vlc/vlc/doc/doxygen/html Code documentation]

=== Tools ===
* [http://trac.videolan.org/vlc Trac] list of bugs, todo's and history of commits.
* [[Contrib_Status|Contrib Status]] - Contrib Libraries Status
* [https://bugs.launchpad.net/products/vlc Launchpad for VLC] ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs?field.searchtext=vlc&orderby=-date_last_updated&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package= recent bug changes]) ([https://bugs.launchpad.net/distros/ubuntu/+source/vlc/+bugs all bugs])
* [http://developers.videolan.org/i18n/vlc.html Translation information and stats]
* [http://cia.navi.cx/stats/project/vlc CIA commit statistics]
* [http://paste.videolan.org Pasteboard]
* [http://mirrors.videolan.org Download mirrors integritylist]
* [http://planet.videolan.org Developer weblog]



|width="60%" class="MainPageBG" style="border: 1px solid #c6c9ff; color: #000; background-color: #f0f0ff"|

=== Joining us ===

VideoLAN welcomes anyone wanting to help, either by writing code, finding or fixing bugs, starting or updating translations, doing graphics work, ...

==== Getting started ====

Getting started at coding is a matter of finding something to fix, and fixing it. Once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for an SVN account so you can fix things directly.

You might be interested in having a look at our [[Mini_Projects|Mini Projects]], which are some identified development efforts for which an existing VLC developer is willing to help a new developer in his progress. These [[Mini Projects]] generally don't require a great knowledge of VLC code.

It is recommended that you join the vlc-devel [http://developers.videolan.org/lists.html mailing list], where all commits are archived.

[[Getting Started At Coding|More information on how to get started at coding on VLC]].

|}

<div style="margin:3pt;width:100%;border: 1px solid #119900; color: #000; background-color: #ddffdd">

=== What is currently going on ===

These pages are used to coordinate some of the currently ongoing development or artwork works.

==== Development ====

* [[VoutRework|Vout Rework]] - improving the video output subsystem
* [[ExternalAPI|External API]] - improving the external API to vlc
* [[MediaControlAPI|Media Control API]] - an high level player-independent media API, wrapping around our [[ExternalAPI|External API]]
* [[0.9.0PlaylistTODO|0.9.0 Playlist TODO]] - Major changes in the upcoming version
* [[telnet rc rewrite]] - Merging the "telnet" and "rc" controls
* [[SimplePreferences|Simple Preferences]] - We wish to add a "simple" preferences mode, additionally to the full mode we already have
* [[QtIntfTODO|Qt Interface TODO]] - A brand new qt4 interface ... in order to get rid of wxWidgets.

==== Design ====
* [[DefaultSkinRequirements|Default Skin Requirements]] - what you need to make a skin that might be eligible for default skin
* [[WebsiteRedesign|Website Redesign]] and [[WebsiteDesign|Design Proposals]]
</div>

== Other software ==

VideoLAN is mainly about VLC, but not only.

Other software by VideoLAN include:
* [[libdvdcss]], a library to access DVD data without bothering about the CSS encryption
* [[libdvdplay]], a DVD navigation support library
* [[libdvbpsi]], a library to decode and create MPEG-TS and DVB-PSI tables
* [[libdca]], a DTS Coherent Acoustics audio decoder library
* [[x264]], a [[H264]] encoding library

== Miscellaneous how-to ==
* Cédric Bosdonnat 's [http://134.214.107.10:85/sims/index.php/Client_query notes] (fr) about developing a new module type.

* Diego 'Flameeyes' Pettenò 's [http://www.gentoo.org/proj/en/desktop/video/vlc.xml notes] about packaging VLC into [http://www.gentoo.org/ Gentoo].

* [[Add a skin|How to add a skin on the skins download page]]

Hacker Guide

2006-11-17T15:07:27Z

The DJ:

===Authors===
* Derk-Jan Hartman

==Introduction==
* What is this?
* What you need to know about VLC

==The many layers of VLC==
* Core
* Access
* Demux
* Packetizers
* Codec
* Stream Output
* Interfaces
* Audio/Video Output
* VLM
* Filters

==VLC source code overview==
* VLC sourcetree
* VLC modules
* VLC objects
* VLC preferences
* VLC variables

==Coding for VLC==
* Coding style
* Adding a module
* Using libvlc
* Bindings

Documentation:Documentation

2006-11-17T14:54:36Z

The DJ: Let's start a hacker's guide

Welcome to the VideoLAN wiki's Documentation main page. Pages in the "Documentation" namespace are part of the "Official" VLC media player documentation.

All pages in this namespace are licensed under the [http://www.gnu.org/copyleft/gpl.html GNU General Public License].

'''Note: many parts of this documentation are currently outdated / obsolete. If you have good knowledge of a particular subject and feel that it could be documented better, please update the appropriate wiki page.'''

== [[Documentation:Play HowTo|VLC Play HowTo]] ==

This document is the complete user guide for the client aspects of VLC.

== [[Documentation:Streaming HowTo|VLC Streaming HowTo]] ==

This document explains how to stream, transcode and save streams using the VideoLAN solution.

== [[Documentation:Hacker's Guide|The Hacker's Guide to VLC]] ==

This document will detail the inner workings of VLC and it's source code.

{{Documentation}}

Contrib Status

2006-11-16T01:25:34Z

The DJ: libcdio updated

{| class="wikitable" style="font-size: smaller; text-align: center; width: 100%; margin: 1em auto 1em auto; border : 1px"
|+ '''Contrib Status'''
|-
! Contrib lib !! VLC version !! Most recent version !! Compile !! Win32 !! BeOS !! MacOSX !! *Nix !! WinCE !! Comment
|-
! Autoconf
| 2.60 || 2.60 || {{up-to-date}} || {{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} ||
|-
! automake
| 1.9.6 || 1.9.6 || {{up-to-date}} || {{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} ||
|-
! Pkgconfig
| 0.15.0 || 0.20.0 || {{untested}} ||{{unNeeded}} || {{unNeeded}}|| {{Needed}}|| {{unNeeded}}|| {{unNeeded}} ||
|-
! Perl
| 5.8.8 || 5.8.8 || {{up-to-date}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} ||
|-
! libtool
| 1.55.6 || 1.55.22 || {{untested}} || {{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} || not tested yet.
|-
! libiconv
| 1.9.2 || 1.9.2 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{unNeeded}}|| {{Needed}} || {{unNeeded}} ||
|-
! gettext
|| 0.16.0 || 0.16.0 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! freetype2
|| 2.1.9 || 2.2.1 || {{middle}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} || 2.1.10 works. not 2.2.1. Should be changed to bz2. Should wait for 2.2.2: http://www.mail-archive.com/freetype@nongnu.org/msg01018.html
|-
! fribidi
|| 0.10.4 || 0.10.7 || {{no}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} || Patches are useless for 0.10.5. Not compiling because of libtool, neither on gcc and mingw - 0.10.7 does not compile with mingw32
|-
! libvorbis
|| 1.1.2 || 1.1.2 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! Ogg
|| 1.1.3 || 1.1.3 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} ||
|-
! libtheora
|| 1.0alpha7 || 1.0alpha7 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! speex
|| 1.2beta1 || 1.2beta1 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! shout
|| 2.2.2 || 2.2.2 || {{up-to-date}} || {{Needed}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} ||
|-
! libebml
|| SVN or 0.7.7 || SVN or 0.7.7 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libmatroska
|| 0.8.0 || 0.8.0 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! x264
|| svn || svn || {{up-to-date}} || {{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} ||{{unNeeded}} ||
|-
! a52
|| 0.7.4 || 0.7.4 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} ||{{unNeeded}} ||
|-
! MPEG2DEC
|| 0.4.1 || 0.4.1 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} ||{{unNeeded}} ||
|-
!libid3tag
|| 0.15.1b || 0.15.1b || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libmad
|| 0.15.1b || 0.15.1b || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! flac
|| 1.1.2 || 1.1.2 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! faad2
|| 2.5 || cvs-20040923 || {{untested}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} ||
|-
! faac
|| 1.25 || 1.24 || {{untested}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} || TODO !
|-
! lame
|| 3.97b2 || 3.97b2 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! ffmpeg
|| SVN || SVN || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} ||
|-
! libdvdcss
|| 1.2.9 || 1.2.9 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libdvdnav
|| CVS || CVS || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libdvdread
|| || || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}}
! TO take OUT of packages.mak
|-
! libdvbpsi
|| 0.1.5 || 0.1.5 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} ||
|-
! livedotcom
|| latest trunk || latest trunk || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! goom2k4
|| 2k4-0 || 2k4-0 || {{up-to-date}} || {{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libcaca
|| 0.9 || 0.9 || {{up-to-date}}|| {{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} || 0.99-beta2 is not a release version ?
|-
! dirac
|| 0.5.4 || 0.6.0 || {{Middle}} || {{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} || API changes in 0.6.0. We need to fix VLC first.
|-
! libdca
|| SVN || SVN || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libmodplug
|| 0.8 || 0.8 || {{up-to-date}} || {{Needed}} || {{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! mash
|| 5.2 || 5.4 || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}}
! TO take OUT of packages.mak
|-
! libcddb
|| 1.2.1 || 1.3.0 || {{no}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} ||
|-
! libcdio
|| 0.78.2 || 0.78.2 || {{no}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} ||
|-
! libpng
|| 1.2.12 || 1.2.12 || {{up-to-date}} ||{{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libgpg-error
|| 1.3 || 1.3 || {{up-to-date}} || {{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libgcrypt
|| 1.2.2 || 1.2.3 || {{untested}} || {{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! gnuTLS
|| 1.4.0 || 1.4.0 || {{up-to-date}} || {{Needed}} ||{{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! Opendaap
|| 0.4.0 || 0.4.0 || {{Up-to-date}}||{{unNeeded}} ||{{unNeeded}} ||{{Needed}} ||{{unNeeded}} || {{unNeeded}} ||
|-
! glib
|| 1.2.10 || 1.2.10 || {{Up-to-date}}||{{unNeeded}} ||{{unNeeded}} ||{{Needed}} ||{{unNeeded}} || {{unNeeded}} ||v. gtk 1.2+
|-
! libidl
|| 0.6.8 || 0.8.6 || {{Up-to-date}} ||{{unNeeded}} ||{{unNeeded}}||{{Needed}} ||{{unNeeded}} || {{unNeeded}} || ''Not up-to-date, but We don't need about new versions'', since we don't really build it. Mirror has changed. It is now on gnome site
|-
! glib-win32
|| 19990228 ~ 1.2.0 || 1.2.10 || {{Up-to-date}} || {{Needed}} ||{{unNeeded}} ||{{unNeeded}} ||{{unNeeded}} || {{unNeeded}} || ''Not up-to-date, but We don't need about new versions'', since we don't really build it.
|-
! libidl-win32
|| 0.6.3 || 0.8.6 || {{Up-to-date}} ||{{Needed}} ||{{unNeeded}} ||{{unNeeded}} ||{{unNeeded}} || {{unNeeded}} || ''Not up-to-date, but We don't need about new versions'', since we don't really build it. Mirror has changed. It is now on gnome site
|-
! gecko
|| 1.7.5 || 1.8b1 || {{Up-to-date}} ||{{unNeeded}} ||{{unNeeded}} ||{{Needed}} ||{{unNeeded}} || {{unNeeded}} ||''Not up-to-date, but We don't need about new versions'', since we don't really build it.
|-
! gecko-win32
|| 1.8b1 || 1.8b1 || {{Up-to-date}} || {{Needed}} ||{{unNeeded}} ||{{unNeeded}} ||{{unNeeded}} || {{unNeeded}} ||''Not up-to-date, but We don't need about new versions'', since we don't really build it.
|-
! twolame
|| 0.3.8 || 0.3.8 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libjpeg
|| 6b || 6b || {{up-to-date}} || {{Needed}} || {{Needed}} || {{Needed}} || {{Needed}} || {{unNeeded}} ||
|-
! libtiff
|| 3.8.2 || 3.8.2 || {{up-to-date}} ||{{Needed}} || {{unNeeded}}|| {{Needed}}|| {{unNeeded}}|| {{unNeeded}}||
|-
! SDL
|| 1.2.11 || 1.2.11 || {{up-to-date}} || {{Needed}} || {{unNeeded}}|| {{Needed}}|| {{unNeeded}}|| {{unNeeded}}||
|-
! SDL_image
|| 1.2.5 || 1.2.5 || {{up-to-date}} || {{Needed}} || {{unNeeded}}|| {{Needed}}|| {{unNeeded}}|| {{unNeeded}}||
|-
! libmpcdec
|| 1.2.2 || 1.2.2 || {{up-to-date}} || {{Needed}} || {{Needed}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} ||
|-
! wxWidgets
|| 2.6.3 || 2.6.3 || {{Up-to-date}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} ||
|-
! Qt
|| || 4.2.0-pl1|| {{up-to-date}} || {{Needed}} || {{unNeeded}} || {{Needed}} || {{Needed}} || {{unNeeded}} || Todo
|-
! zlib
|| 1.2.3 || 1.2.3 || {{Up-to-date}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || {{Needed}} ||
|-
! libxml2
|| 2.6.26 || 2.6.26 || {{up-to-date}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} ||
|-
! portaudio
|| 19 || 19 || {{up-to-date}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} ||Commented for Win32
|-
! Clinkcc
|| 171 || 171 || {{up-to-date}}|| {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || Commented for MacOSX
|-
! Upnp
|| 1.3.1 || 1.3.1 || {{up-to-date}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || Commented
|-
! expat
|| 1.95.8 || 2.0.0 || {{no}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} ||Commented for MacOSX
|-
! NSAM
|| Cvs 2006-01 || CVS || {{Untested}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} || For MacTels. Need to update cvs ???
|-
! libunicows
|| 1.1.1 || 1.1.1 || {{up-to-date}} ||{{Needed}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} ||
|-
! Tremor
|| SVN || SVN || {{no}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || Symbols missing in packages.mak ???
|-
! VCDimager
|| 0.7.23 || 0.7.23 || {{Up-to-date}} || {{unNeeded}} || {{unNeeded}} || {{Needed}} || {{unNeeded}} || {{unNeeded}} ||
|-
! Contrib lib !! VLC version !! Most recent version !! Compile !! Win32 !! BeOS !! MacOSX !! *Nix !! WinCE !! Comment
|}

We Use VideoLAN

2006-08-02T10:39:36Z

The DJ: /* The Balloon */

<div style="float: right;">__TOC__</div>

Do you have some cool project you use VideoLAN for?
Post a link and a small description here.



=====ACTlab.tv=====
: They are probably using x264 for their video encoding
: http://actlab.tv/technology.htm

=====Advene project=====
: Advene (Annotate DVDs, Exchange on the Net) aims at providing a format to share annotations about movies stored on DVDs, as well as tools to edit and visualize the annotations. It uses VLC to play/extract info from the DVD's
: [http://liris.cnrs.fr/advene/index_en.html website]

=====Annodex=====
: Annodex is a system for metadata, hyperlinking and browing media content. Their webmodule uses a customized version of our mozilla plugin
: http://annodex.net

=====The Balloon=====
: [http://www.maveric.org.uk/mavhome.html JediMaster and friends] are building a Mars balloon at the Univertsity of Kent which uses VideoLAN to stream images back to earth. Some [http://www.maveric.org.uk/photos/testing/ Images].
: http://www.maveric.org.uk

=====ControlAulas=====
[http://www.itais.net/controlaula/ ControlAulas] uses videolan to transmit video between students and teachers in a virtual classroom situation. It's part of the [http://linex.org gnuLinex] project and the source is available [http://forjamari.linex.org/projects/controlaulas/ here].

=====Cory Doctorow=====
: Writer [http://www.craphound.com/ Cory Doctorow] uses VLC Player [http://www.boingboing.net/2004/03/26/vlc_will_play_itunes.html] [http://www.msversus.org/node/234].

=====Cypherpunk version of MacBeth=====
: People at [http://www.pirateutopia.org/ Pirate Utopia] are using VLC in a MacBeth-inspired show to display ASCII-art video.
: http://www.pirateutopia.org/macbeth/techie.htm

=====Distributed VideoLAN Server Management=====
: Bart Kerver from [[SURFnet]] has created software to manage multiple VideoLAN servers.
: http://speeldoos.showcase.surfnet.nl/dvlsm/

=====DentiFreeX=====
: Dispositif d'Enregistrement Numérique pour la Télévision sur Internet par Flux Reçus En Environnement mac osX
: http://coolercolors.free.fr/forum

=====Elephant's Dream=====
: Community-developed movie using free tools - free with creative commons license.
: http://www.elephantsdream.org/

=====Free=====
: Free ADSL use VideoLAN. ''[http://adsl.free.fr/tv/freeplayer/ FreePlayer] permet de visioner des vidéo ou d'écouter des fichier audio d'un ordinateur sur la télévision.''
: http://adsl.free.fr/

=====Google, inc.=====
: As previously announced [http://www.boingboing.net/2005/06/26/google_to_launch_onl.html] [http://battellemedia.com/archives/001658.php], Google's video search used to use a browser plugin based on VLC.
: http://video.google.com/

=====Las Vegas Security Lines=====
: On the Las Vegas Airport, people in line for the security checks are treated to some 'how to keep the line as short as possible' movies. These movies are being streamed with VLC.
: [http://www.usatoday.com/travel/news/2004-10-05-vegas-airport_x.htm An article about this project]

=====Metavid=====
: Metavid uses the vlc mozilla plugin in a part of an all open source archive which aims to facilitate real-time collective [re]mediation of legislative proceedings.
: http://metavid.org

=====Mírame=====
: Mírame is a video surveillance web-based application that uses VLC to display MPEG-4 streams from [http://www.axis.com/products/video/camera/ Axis Network Cameras]
: http://www.mirame.net/

=====Neutrino MoviePlayer=====
: The [http://www.dbox2.info Neutrino] [http://www.giggo.de/dbox2/movieplayer.html MoviePlayer] now uses VLC so users can stream the movies on their computer to a a DBox.

=====Participatory Culture Foundation=====
: DTV is a webbased player for their RSS based videoblogging system that uses our mozilla plugin
: http://www.participatoryculture.org/

=====Plutohome=====
: They have a vlc module for their system. Exact use unknown.
: http://plutohome.com/

=====Songbird=====
: [[Songbird]] is an open source rival to [[iTunes]].
: http://www.songbirdnest.com/

=====SongSubtitles.org=====
: [[SongSubtitles.org]]'s goal is to create a base of music subtitles.
: http://www.songsubtitles.org/

=====Tryst=====
: This application is based on VLC and uses Bonjour announcements to share video broadcasts.
: http://www.trystx.com/

=====VLC Controller=====
: This Extension to Sailing Clicker to allow you to use a PDA or phone to control VLC trough a bluetooth connection.
: [http://www.snarb.tk/ website]

=====VLC Remote=====
: A very nice Dashboard widget that uses the VLC webinterface to control a remote VLC.
: [http://www.autopoetic.com/vlcremote/ VLC remote hompage].

=====VLC Romeo Plugins=====
: Plugins to use Romeo to control VLC trough a bluetooth PDA or phone.
: [http://homepage.mac.com/WebObjects/FileSharing.woa/wa/default?user=srouet&templatefn=FileSharing4.html&xmlfn=TKDocument.4.xml&sitefn=RootSite.xml&aff=consumer&cty=US&lang=en website]

VLC Dev Projects

2006-07-31T14:21:31Z

The DJ: /* Improved ASX support */

This is a list of small independent improvements to VLC for which we are looking for interested developers, because we simply don't have enough time.

These do not require advanced knowledge of VLC internals but they can still vastly improve many parts of VLC

For each project, we list a contact person, who knows the subject best and who will be able to assist you if you are interested in working on these. We generally are very often present on irc.videolan.org, chan #videolan, so please don't hesitate to drop by or to send a mail if you are interested in a given problem (our mail adresses are generally <nick>@videolan.org).

We also have a number of "easy" bugs. You can check them out [http://trac.videolan.org/vlc/query?status=new&status=assigned&status=reopened&difficulty=easy&order=priority` here]

= Network =

== RTCP support ==

Our RTSP implementation (for broadcasting and video on demand) does not support the RTCP protocol. This is a must to have a real support for RTSP.
Some work has already been started, but there is still much to do.

Contact: [[User:JPSaman|JPSaman]]

= Inputs =

== DVB support for Windows ==

DVB is the norm for :
* Digital Terrestrial TV (aka DVB-T)
* Digital Cable TV (aka DVB-C)
* Digital Satellite TV (aka DVB-S)

Several DVB input cards exist. We support these on Linux, but not on Windows. For Windows, we need to support so-called BDA drivers.

The problem is that we don't have both the time and the required hardware on Windows comps.

This project is probably not terribly complex, but you need the hardware.

Contacts:
* DVB specialists [[User:Meuuh|Meuuh]] [[User:JPSaman|JPSaman]] [[User:Dnumgis|Dnumgis]]
* Windows specialist [[User:Quovodis|Quovodis]]

== V4L2 support ==

VLC currently supports has a pvr module and a v4l (video for linux) module.
However
* some cards are only supported in the new v4l2 API
* The linux kernel will soon drop v4l support

So if someone could update VLC's current modules to work with V4L2 and the new ivtv api, this would be a welcome addition.
This is not a very difficult project, but you will need to have the hardware to test against.

= Video =

== DirectX 9 video output ==

DirectX 9 features some improvements that we could use in our video output

Contact: [[User:Quovodis|Quovodis]]

== Improvements to the X11 video output ==

Fullscreen support to improve .

= Interfaces =

== Streaming profiles ==

This is a big subject, that has barely started. Interested persons will need to work closely with existing developers to implement this.
Not much information is available yet. The idea is to make streaming very easy, and yet powerful by using parametrable profiles. These could be used either by the graphical interfaces or through HTTP/command line interfaces

Contact: [[User:Zorglub|Zorglub]]

= Playlist =

== Improved Podcast support ==

Our current podcast support is very weak. We can read them, but that's all. We need a real infrastructure to handle them correctly. This will require some changes to the playlist code, so you will need to work closely with existing developers.

Contacts: [[User:Dionoea|Dionoea]] [[User:Zorglub|Zorglub]]

== Improved ASX support ==

ASX is a playlist format used by Microsoft stuff. We can read it but we could do much better. More information is available at
https://trac.videolan.org/vlc/ticket/20
This project is mostly done, but could use some tidying up.

Contact: [[User:Dnumgis|Dnumgis]] [[User:The DJ|The DJ]] (hartman at videolan org )

== Disc probing ==

We currently have some miscellaneous code to detect discs (DVDs, Audio CDs, ...) but it's a bit scattered and it could be used much better in the playlist.

Contact: [[User:Zorglub|Zorglub]]

== Live folders ==

Some programs support so-called live folders. You add a folder to the playlist, and if the files in the folder are changed, the changes are copied to the playlist.

Having this would of course be great :)

It might require some work to be able to do this in Linux, Windows and OS X, but the current developers will of course be able to help on these.

Contacts: [[User:Zorglub|Zorglub]] [[User::TheDJ|TheDJ]]

= Misc =

== Subtitles autodetection ==

Our current subtitles autodetection feature is not very good, and far behind some other implementations.

The key problems should be identified and fixed. We already know we have many problems with encoding, but the detection features themselves seem to be weak.

We should also enable the subtitles when they are detected

Contact: [[User:Yoann|Yoann]]

== DBUS Integration ==

DBUS is a communication mechanism for Linux (mainly).

We would like VLC to be able to use it so that other programs can interact with vlc (start/stop, know what is being played, ...)

Contact: [[User:Xtophe|Xtophe]]

==Audioscrobbler==

A [http://www.audioscrobbler.net/ Audioscrobbler] VLC Plug-in for the social music network [http://www.last.fm Last.Fm]<br />
This is an idea, as unless it is an easy project i do not have the knowledge. [http://www.audioscrobbler.net/wiki/Protocol1.1 Protocol Info]

VLC Dev Projects

2006-07-31T14:19:46Z

The DJ: /* Inputs */

This is a list of small independent improvements to VLC for which we are looking for interested developers, because we simply don't have enough time.

These do not require advanced knowledge of VLC internals but they can still vastly improve many parts of VLC

For each project, we list a contact person, who knows the subject best and who will be able to assist you if you are interested in working on these. We generally are very often present on irc.videolan.org, chan #videolan, so please don't hesitate to drop by or to send a mail if you are interested in a given problem (our mail adresses are generally <nick>@videolan.org).

We also have a number of "easy" bugs. You can check them out [http://trac.videolan.org/vlc/query?status=new&status=assigned&status=reopened&difficulty=easy&order=priority` here]

= Network =

== RTCP support ==

Our RTSP implementation (for broadcasting and video on demand) does not support the RTCP protocol. This is a must to have a real support for RTSP.
Some work has already been started, but there is still much to do.

Contact: [[User:JPSaman|JPSaman]]

= Inputs =

== DVB support for Windows ==

DVB is the norm for :
* Digital Terrestrial TV (aka DVB-T)
* Digital Cable TV (aka DVB-C)
* Digital Satellite TV (aka DVB-S)

Several DVB input cards exist. We support these on Linux, but not on Windows. For Windows, we need to support so-called BDA drivers.

The problem is that we don't have both the time and the required hardware on Windows comps.

This project is probably not terribly complex, but you need the hardware.

Contacts:
* DVB specialists [[User:Meuuh|Meuuh]] [[User:JPSaman|JPSaman]] [[User:Dnumgis|Dnumgis]]
* Windows specialist [[User:Quovodis|Quovodis]]

== V4L2 support ==

VLC currently supports has a pvr module and a v4l (video for linux) module.
However
* some cards are only supported in the new v4l2 API
* The linux kernel will soon drop v4l support

So if someone could update VLC's current modules to work with V4L2 and the new ivtv api, this would be a welcome addition.
This is not a very difficult project, but you will need to have the hardware to test against.

= Video =

== DirectX 9 video output ==

DirectX 9 features some improvements that we could use in our video output

Contact: [[User:Quovodis|Quovodis]]

== Improvements to the X11 video output ==

Fullscreen support to improve .

= Interfaces =

== Streaming profiles ==

This is a big subject, that has barely started. Interested persons will need to work closely with existing developers to implement this.
Not much information is available yet. The idea is to make streaming very easy, and yet powerful by using parametrable profiles. These could be used either by the graphical interfaces or through HTTP/command line interfaces

Contact: [[User:Zorglub|Zorglub]]

= Playlist =

== Improved Podcast support ==

Our current podcast support is very weak. We can read them, but that's all. We need a real infrastructure to handle them correctly. This will require some changes to the playlist code, so you will need to work closely with existing developers.

Contacts: [[User:Dionoea|Dionoea]] [[User:Zorglub|Zorglub]]

== Improved ASX support ==

ASX is a playlist format used by Microsoft stuff. We can read it but we could do much better. More information is available at
https://trac.videolan.org/vlc/ticket/20

Contact: [[User:Dnumgis|Dnumgis]]

== Disc probing ==

We currently have some miscellaneous code to detect discs (DVDs, Audio CDs, ...) but it's a bit scattered and it could be used much better in the playlist.

Contact: [[User:Zorglub|Zorglub]]

== Live folders ==

Some programs support so-called live folders. You add a folder to the playlist, and if the files in the folder are changed, the changes are copied to the playlist.

Having this would of course be great :)

It might require some work to be able to do this in Linux, Windows and OS X, but the current developers will of course be able to help on these.

Contacts: [[User:Zorglub|Zorglub]] [[User::TheDJ|TheDJ]]

= Misc =

== Subtitles autodetection ==

Our current subtitles autodetection feature is not very good, and far behind some other implementations.

The key problems should be identified and fixed. We already know we have many problems with encoding, but the detection features themselves seem to be weak.

We should also enable the subtitles when they are detected

Contact: [[User:Yoann|Yoann]]

== DBUS Integration ==

DBUS is a communication mechanism for Linux (mainly).

We would like VLC to be able to use it so that other programs can interact with vlc (start/stop, know what is being played, ...)

Contact: [[User:Xtophe|Xtophe]]

==Audioscrobbler==

A [http://www.audioscrobbler.net/ Audioscrobbler] VLC Plug-in for the social music network [http://www.last.fm Last.Fm]<br />
This is an idea, as unless it is an easy project i do not have the knowledge. [http://www.audioscrobbler.net/wiki/Protocol1.1 Protocol Info]

Matroska

2006-03-01T17:05:41Z

The DJ:

{{website|Matroska|http://www.matroska.org/}}
{{open}}
'''Matroska''' is a [[container]] format for storing or streaming video and audio files. The Matroska format has many features, such as a DVD-style menu system.

File-extensions: .mkv .mka .mks

==Compatability==
VideoLAN can only read matroska files. Note that some of the (video)[[codecs]] that can be used inside this fileformat are not supported by VLC. Most notably the RealVideo 9 and 10 formats.

{{stub}}

== In French: ==

Site officiel: [http://www.matroska.org/index.html.fr http://www.matroska.org/index.html.fr]

Un article framasoft: [http://www.framasoft.net/article2113.html http://www.framasoft.net/article2113.html]

Matroska

2006-03-01T17:04:21Z

The DJ: /* Compatability */

{{website|Matroska|http://www.matroska.org/}}
{{open}}
'''Matroska''' is a [[container]] format for storing or streaming video and audio files. The Matroska format has many features, such as a DVD-style menu system.

==Compatability==
VideoLAN can only read matroska files. Note that some of the (video)[[codecs]] that can be used inside this fileformat are not supported by VLC. Most notably the RealVideo 9 and 10 formats.

{{stub}}

== In French: ==

Site officiel: [http://www.matroska.org/index.html.fr http://www.matroska.org/index.html.fr]

Un article framasoft: [http://www.framasoft.net/article2113.html http://www.framasoft.net/article2113.html]

Codec

2006-02-28T01:04:28Z

The DJ: /* Subtitle Codecs */

''See Also the [http://www.videolan.org/doc/vlc-user-guide/en/ch02.html Official documentation: list of codecs]''

''For more information of codecs in general, look ar [[wikipedia:Codecs|wikipedia]] and [http://wiki.multimedia.cx wiki.multimedia.cx].''

Codec is short for coder/decoder.
For portability to almost all decoders, we recommend
using the [[MPEG-1]] standard of vcodec=mp1v, acodec=mpga, and mux=mpeg1.

To save a file in a different codec, you can use the transcoding [[wizard]] or [[transcode]] from the [[command prompt]] with a command like this:
:vlc file --sout='#transcode{vcodec=''mp1v'', vb=''1024'', acodec=''mpga'', ab=''128''}:std{access=file, mux=''mpeg1'', url=''C:\file_name.mpg''}'

==Video Codecs==
Use the "name" part in you vcodec=... commands

{|
| '''''name'''''
| ''description''
|-
| '''mp1v'''
| [[MPEG-1]] Video - recommended for portability
|-
| '''mp2v'''
| [[MPEG-2]] Video - used in DVDs
|-
| '''mp4v'''
| [[MPEG-4]] Video
|-
| '''SVQ1'''
| [[Sorenson Video]] v1
|-
| '''SVQ3'''
| Sorenson Video v3
|-
| '''WMV1'''
| [[Windows Media Video]] v1
|-
| '''WMV2'''
| Windows Media Video v2
|-
| WMV3
| Windows Media Video v3 / VC9 ([[Common_Problems#WMV_files|unsupported]])
|-
| '''DVSD'''
| [[Digital Video]]
|-
| '''MJPG'''
| [[MJPEG]]
|-
| '''H263'''
| [[H263]]
|-
| '''h264'''
| [[H264]]
|-
| '''theo'''
| [[Theora]]
|-
| '''IV20'''
| [[Indeo Video]]
|-
| '''RV10'''
| [[Real Media Video]]
|-
| '''cvid'''
| [[Cinepak]]
|-
| '''VP31'''
| [[On2 VP]]
|-
| '''FLV1'''
| [[Flash Video]]
|-
| '''CYUV'''
| [[Creative YUV]]
|-
| '''HFYU'''
| [[Huffman YUV]]
|-
| '''MSVC'''
| [[Microsoft]] Video v1
|-
| '''MRLE'''
| Microsoft [[RLE]] Video
|-
| '''AASC'''
| [[Autodesc]] RLE Video
|-
| '''FLIC'''
| [[FLIC]] video
|-
| '''QPEG'''
| [[QPEG]] Video
|}

==Audio Codecs==
Use the "name" part in you acodec=... commands

{|
| '''''name'''''
| ''description''
|-
| '''mpga'''
| [[MPEG audio]] (recommended for portability)
|-
| '''mp3'''
| [[MP3 audio|MPEG Layer 3 audio]]
|-
| '''mp4a'''
| [[MP4 audio]]
|-
| '''a52''' or '''ac3'''
| [[Dolby Digital]] ([[A52]] or [[AC3]])
|-
|
| [[DTS]]
|-
| '''vorb'''
| [[Vorbis]]
|-
| '''spx'''
| [[ Speex]]
|-
|
| [[AAC (Advanced Audio Coding)]]
|-
|
| [[Windows Media Audio]]
|-
|
| [[DV Audio]]
|-
| '''flac''' or '''fl32'''
| [[FLAC]]
|-
|
| [[LPCM]]
|-
|
| [[ADPCM]]
|-
|
| [[AMR]]
|-
|
| [[QuickTime Audio]]
|-
|
| [[Real Audio]]
|-
|
| [[MACE]]
|-
|
| [[MusePack]]
|}

==Subtitle Codecs==
{|
|-
| '''CVD'''
| [[CVD|CVD Subtitles]]
|-
| '''SVCD (Overlay Graphics)'''
| [http://www.vcdimager.org/pub/vcdimager/manuals/0.7/svcd-ogt-subtitles.html SVCD Subtitle (OGT) Information]
|-
| '''SRT'''
| [[SRT|Subrip Subtitles]]
|-
| '''SSA/ASS'''
| [[SSA|Sub Station Alpha or Advanced Sub Station Subtitles]]
|-
| '''SubViewer'''
| [[Subviewer|SubViewer Subtitles]]
|-
| '''VobSub'''
| [[VobSub|VobSub Subtitles]]
|-
| '''DVD subtitles'''
| [[DVD Subtitles]]
|-
| '''VPlayer'''
| [[Vplayer Subtitles]]
|-
| '''MicroDVD'''
| [[MicroDVD Subtitles]]
|-
| '''Sami'''
| [[Sami Subtitles]]

|}

== Muxers ==
Use the "name" part in you mux=... commands

{|
| '''''name'''''
| ''description''
|-
| '''ts'''
| [[MPEG-TS|MPEG Transport Stream]], primarily used for streaming MPEG
|-
| '''ps'''
| [[MPEG-PS|MPEG Program Stream]], primarily used for saving MPEG data to disk
|-
| '''avi'''
| [[AVI]]
|-
| '''mp4'''
| [[MPEG-4]]
|-
| '''asf'''
| [[ASF]]
|-
| '''dummy'''
| [[dummy]] output, can be used in creation of [[MP3]] files.
|-
| '''ogg'''
| [http://www.xiph.org/ Xiph.org's] [[ogg]] container format. Can contain audio, video, and metadata.
|}

{{stub}}

VideoLAN

2006-02-28T00:50:51Z

The DJ: /* The History of VideoLAN */

== The History of VideoLAN ==

(this is still incomplete but it should give the background info people are likely to be looking for)

The [http://www.videolan.org VideoLAN project] was started as a school project in 1996 by students of [http://www.ecp.fr Ecole Centrale Paris], a French engineering school. These students wanted to be able to watch television in their PCs. (They also wanted to upgrade the [http://www.via.ecp.fr VIA Centrale Réseaux] network so they needed some bandwidth intensive application to justify the upgrade.)

They began writing VLS (VideoLAN Server) and VLC (VideoLAN Client) to stream and read MPEG2 streams. They succeeded serving and reading the first stream in 1998. These two software were planed to be modular, which meant a core consisting basically of communication functions to be used by the modules. This allowed easy porting of the OS specific modules.

In 2001, after many months (if not years) of negociation, [http://download.videolan.org/images/paper.jpeg the school's Director agreed to a change to the GPL licence]. Developers from all around the world started working on the project right away. One of them (gibalou) even submitted the Win32 port 6 months latter !

The first large scale multicast streaming tests occured in May 2002. 500 students on the VIA Centrale Réseaux network were able to participate in these tests. In January 2003, the first MPEG4 streams were tested and realtime MPEG4 encoding was available two months later.

== Misc ==

[http://people.videolan.org/~dionoea/servers/ The VideoLAN project's servers]

== Related Pages ==
* [[VLC]]
* [[VLS]]

{{stub}}

VoutRework

2006-01-05T00:11:44Z

The DJ: /* Misc */

= Draft design for the vout rework effort =

[[VoutReworkUserRequirements]]

[[VoutReworkOrganization]]

== Overall architecture ==

The current system (one vout_thread_t per window) will be splitted

* vout_core that manages all vout instances and windows. also takes care of vout_filters (wall, clone)
* vout_window object per displayed window. provides a "region for vout_renderers" to draw in.
* vout_render that renders the actual video, text and image

== OSD and subpictures ==

We need to be able to display them either:

* At video resolution, for DVD subtitles (on the "render")
* At screen resolution (text subtitles, OSD control) (on the "output")
** This will also allow us to draw subtitles outside of the video rendering
** Probably needs specific code for each vout

At the moment, subpictures have very annoying timing constraints. subpictures should be timed either on the stream (for subpictures) or absolute, from the vout_core
(for subfilters)

We should create two seperate systems. a vout_render level system which basically draws extra things into the region provided by vout_window. This can be both text, images and possibly even video. Material should be drawn in the resolution of the provided region, instead of the resolution of the main video. It should be seperate from the spu streams. However it should be possible to feed SPU based material to the vout_render system instead of the normal SPU stream pipeline and vice versa.

Comments from Gibalou: I agree overall but be aware that rendering on the vout window can be quite tricky. For instance on platforms which only support 1 overlay (already used by the video), we will have to constantly refresh the OSD (to handle resizing / refreshing of the vout window).
For this reason I would suggest we keep this feature as simple as possible and only make it support displaying of subpictures (subpicture_t/subpicture_region_t).

== Filters ==

Make a clean separation:

* vout_filters should not be the same as real vouts anymore (will come from the split)
Comments from Gibalou: they don't really need to be changed since they alreday don't create any window.
* pic_filter
** Currently called video_filter2, should be renamed
** Works on a single pic buffer
** Can be streamed
Comments from Gibalou: video_filter2 is not just about 1->1 picture conversion. It is actually designed to work on video and could for instance allow for temporal de-interlacing, inverse telecine, etc... So it really is a video_filter and not merely a pic_filter.

Two big areas of work to be able to integrate video_filters into the vout core will be:

- Proper support for direct-rendering.
Some filters won't actually modify the video frames directly (eg. auto-cropping) or will do in-place modifications so they will need to be able to allocate their pictures from the next filter in the chain and pass it on to the previous filter when requested. In short, picture allocation needs to be reviewed so it is done in an optimized way.

- Dynamic modification of the filter chain.
Again this is tricky because the decoder (which does direct-rendering) will be using pictures allocated from the filter. If this filter changes or is removed, we will need a way replace the pictures in use by the decoder. That could be done by having a mechanism that progressively replaces the picture buffers used by the decoder by indirect buffers and when non of the direct buffers are in use anymore then we switch the filter.
That will be a lot better then the current way of stopping/starting the decoder.
* subpicture_filter

== Modularization of specific calls ==

For many of the operations we need, OS specific calls exist (OpenGL, Quartz, DirectX). This should be modularized, with a native "C" fallback.
OS specific calls are often faster.

There should be only one module for all the calls, if possible. The best module would be loaded by the vout_core singleton, and function pointers set up for each of the functions we need. perhaps a vout_Control type could take care of all these things in the vout_renderer.
paramaters that should be handled this way are at least: alignment, AR, crop, pad

Comment from Gibalou: AR, crop (and soon pad) are already implemented in the vouts (see below). Alignment is also already supported and is only about placing the vout subwindow (frame or whatever you call it) into the main window.

== Misc ==

* Vout plugins (that provide vout windows) should allow reusing a vout by reusing it. This would much improve the experience)
* Vout windows must have a flag to tell if they are "main" or "helper" (audio visualization, ...). Helper vouts should get no OSD (if another vout is present) and should not "steal" the accelerated vout"
* cropping and padding (do at OS level, but provide a core call to set it up and configure) '''=> Done'''
* better hotkeys integration : need hotkey module redesign to act on selected vout and relevant input instead of the first we find
* vout windows should indicate if they are on a 4:3 or 16:9 screen (we can calculate this trough resolution). Note that this can change, because a window could be moved from one screen to another. Use callbacks. '''=> Why would you want to know the AR of the screen ? Aren't you confusing with the PAR ? This information could be used by the core to facilitate selection of cropping/padding etc for instance 4:3 display on a 16:9 screen. you might want to crop the top/bottom or stretch the view by default. Especially when you are also gonna add padding for subtitle rendering for instance, this information might become useful.
'''

== cropping padding functionality ==

* add padding in order to display subs under the video. what if we have a 4:3 movie in a 4:3 screen? do we create blackbars to the left and right sides? do we crop a part of the video ???
* 4:3 cropping to 16:9 (in order to remove blackbars at top and bottom
* 16:9 cropping to 4:3 (in order to remove blackbars left and right side)
* 4:3 to 16:9 (AR correction)
* 16:9 to 4:3 (AR correction)
* AR Freeform
* Support Moviescreen AR? (2.39:1 or 1.85:1)
* More info on AR: http://en.wikipedia.org/wiki/Aspect_ratio_(image)
* If we let the window provider pass/calculate the AR of the display, then we can even do some of this automatically if the uses desires.
* cropping should have priority over padding. Then we can first crop blackbars, then add padding for subs.
* coordinate specified cropping and padding

Comment from Gibalou: AR / Cropping (and soon Padding) has already been reworked and is now handled directly in the vout module (makes sense since cropping and resizing are supported by most sane graphic APIs).
All this is controled from the core by setting the relevant parameters in vout_format_t.
Now, what could be done is to add extra logic (eg. in video_filters) to do some clever things like auto-cropping, etc... All they need to do is to modify video_format_t to change the final cropping/padding/AR.

VoutRework

2005-08-28T14:03:49Z

The DJ: /* cropping padding functionality */

= Draft design for the vout rework effort =

== Overall architecture ==

The current system (one vout_thread_t per window) will be splitted

* vout_core that manages all vout instances and windows. also takes care of vout_filters (wall, clone)
* vout_window object per displayed window. provides a "region for vout_renderers" to draw in.
* vout_render that renders the actual video, text and image

== OSD and subpictures ==

We need to be able to display them either:

* At video resolution, for DVD subtitles (on the "render")
* At screen resolution (text subtitles, OSD control) (on the "output")
** This will also allow us to draw subtitles outside of the video rendering
** Probably needs specific code for each vout

At the moment, subpictures have very annoying timing constraints. subpictures should be timed either on the stream (for subpictures) or absolute, from the vout_core
(for subfilters)

We should create two seperate systems. a vout_render level system which basically draws extra things into the region provided by vout_window. This can be both text, images and possibly even video. Material should be drawn in the resolution of the provided region, instead of the resolution of the main video. Is should be seperate from the spu streams. However it should be possible to feed SPU based material to the vout_render system instead of the normal SPU stream pipeline and vice versa.

== Filters ==

Make a clean separation:

* vout_filters should not be the same as real vouts anymore (will come from the split)
* pic_filter
** Currently called video_filter2, should be renamed
** Works on a single pic buffer
** Can be streamed
* subpicture_filter

== Modularization of specific calls ==

For many of the operations we need, OS specific calls exist (OpenGL, Quartz, DirectX). This should be modularized, with a native "C" fallback.
OS specific calls are often faster.

There should be only one module for all the calls, if possible. The best module would be loaded by the vout_core singleton, and function pointers set up for each of the functions we need. perhaps a vout_Control type could take care of all these things in the vout_renderer.
paramaters that should be handled this way are at least: alignment, AR, crop, pad

== Misc ==

* Vout plugins (that provide vout windows) should allow reusing a vout by reusing it. This would much improve the experience)
* Vout windows must have a flag to tell if they are "main" or "helper" (audio visualization, ...). Helper vouts should get no OSD (if another vout is present) and should not "steal" the accelerated vout"
* cropping and padding (do at OS level, but provide a core call to set it up and configure).
* better hotkeys integration : need hotkey module redesign to act on selected vout and relevant input instead of the first we find
* vout windows should indicate if they are on a 4:3 or 16:9 screen (we can calculate this trough resolution). Note that this can change, because a window could be moved from one screen to another. Use callbacks.

== cropping padding functionality ==

* add padding in order to display subs under the video. what if we have a 4:3 movie in a 4:3 screen? do we create blackbars to the left and right sides? do we crop a part of the video ???
* 4:3 cropping to 16:9 (in order to remove blackbars at top and bottom
* 16:9 cropping to 4:3 (in order to remove blackbars left and right side)
* 4:3 to 16:9 (AR correction)
* 16:9 to 4:3 (AR correction)
* AR Freeform
* Support Moviescreen AR? (2.39:1 or 1.85:1)
* More info on AR: http://en.wikipedia.org/wiki/Aspect_ratio_(image)
* If we let the window provider pass/calculate the AR of the display, then we can even do some of this automatically if the uses desires.
* cropping should have priority over padding. Then we can first crop blackbars, then add padding for subs.
* coordinate specified cropping and padding

VoutRework

2005-08-28T13:57:26Z

The DJ: /* cropping padding functionality */

VoutRework

2005-08-28T13:55:31Z

The DJ: /* cropping padding functionality */

VoutRework

2005-08-28T13:54:04Z

The DJ: /* cropping padding functionality */

VoutRework

2005-08-28T13:52:40Z

The DJ: /* Misc */

= Draft design for the vout rework effort =

== Overall architecture ==

The current system (one vout_thread_t per window) will be splitted

* vout_core that manages all vout instances and windows. also takes care of vout_filters (wall, clone)
* vout_window object per displayed window. provides a "region for vout_renderers" to draw in.
* vout_render that renders the actual video, text and image

== OSD and subpictures ==

We need to be able to display them either:

* At video resolution, for DVD subtitles (on the "render")
* At screen resolution (text subtitles, OSD control) (on the "output")
** This will also allow us to draw subtitles outside of the video rendering
** Probably needs specific code for each vout

At the moment, subpictures have very annoying timing constraints. subpictures should be timed either on the stream (for subpictures) or absolute, from the vout_core
(for subfilters)

We should create two seperate systems. a vout_render level system which basically draws extra things into the region provided by vout_window. This can be both text, images and possibly even video. Material should be drawn in the resolution of the provided region, instead of the resolution of the main video. Is should be seperate from the spu streams. However it should be possible to feed SPU based material to the vout_render system instead of the normal SPU stream pipeline and vice versa.

== Filters ==

Make a clean separation:

* vout_filters should not be the same as real vouts anymore (will come from the split)
* pic_filter
** Currently called video_filter2, should be renamed
** Works on a single pic buffer
** Can be streamed
* subpicture_filter

== Modularization of specific calls ==

For many of the operations we need, OS specific calls exist (OpenGL, Quartz, DirectX). This should be modularized, with a native "C" fallback.
OS specific calls are often faster.

There should be only one module for all the calls, if possible. The best module would be loaded by the vout_core singleton, and function pointers set up for each of the functions we need. perhaps a vout_Control type could take care of all these things in the vout_renderer.
paramaters that should be handled this way are at least: alignment, AR, crop, pad

== Misc ==

* Vout plugins (that provide vout windows) should allow reusing a vout by reusing it. This would much improve the experience)
* Vout windows must have a flag to tell if they are "main" or "helper" (audio visualization, ...). Helper vouts should get no OSD (if another vout is present) and should not "steal" the accelerated vout"
* cropping and padding (do at OS level, but provide a core call to set it up and configure).
* better hotkeys integration : need hotkey module redesign to act on selected vout and relevant input instead of the first we find
* vout windows should indicate if they are on a 4:3 or 16:9 screen (we can calculate this trough resolution). Note that this can change, because a window could be moved from one screen to another. Use callbacks.

== cropping padding functionality ==
* add padding in order to display subs under the video. what if we have a 4:3 movie in a 4:3 screen? do we create blackbars to the left and right sides? do we crop a part of the video ???
* 4:3 cropping to 16:9 (in order to remove blackbars at top and bottom
* 16:9 cropping to 4:3 (in order to remove blackbars left and right side)
* 4:3 to 16:9 (AR correction)
* 16:9 to 4:3 (AR correction)
* AR Freeform
* Support Moviescreen AR? (2.39:1 or 1.85:1)
* More info on AR: http://en.wikipedia.org/wiki/Aspect_ratio_(image)

VoutRework

2005-08-28T13:38:03Z

The DJ: /* Modularization of specific calls */

= Draft design for the vout rework effort =

== Overall architecture ==

The current system (one vout_thread_t per window) will be splitted

* vout_core that manages all vout instances and windows. also takes care of vout_filters (wall, clone)
* vout_window object per displayed window. provides a "region for vout_renderers" to draw in.
* vout_render that renders the actual video, text and image

== OSD and subpictures ==

We need to be able to display them either:

* At video resolution, for DVD subtitles (on the "render")
* At screen resolution (text subtitles, OSD control) (on the "output")
** This will also allow us to draw subtitles outside of the video rendering
** Probably needs specific code for each vout

At the moment, subpictures have very annoying timing constraints. subpictures should be timed either on the stream (for subpictures) or absolute, from the vout_core
(for subfilters)

We should create two seperate systems. a vout_render level system which basically draws extra things into the region provided by vout_window. This can be both text, images and possibly even video. Material should be drawn in the resolution of the provided region, instead of the resolution of the main video. Is should be seperate from the spu streams. However it should be possible to feed SPU based material to the vout_render system instead of the normal SPU stream pipeline and vice versa.

== Filters ==

Make a clean separation:

* vout_filters should not be the same as real vouts anymore (will come from the split)
* pic_filter
** Currently called video_filter2, should be renamed
** Works on a single pic buffer
** Can be streamed
* subpicture_filter

== Modularization of specific calls ==

For many of the operations we need, OS specific calls exist (OpenGL, Quartz, DirectX). This should be modularized, with a native "C" fallback.
OS specific calls are often faster.

There should be only one module for all the calls, if possible. The best module would be loaded by the vout_core singleton, and function pointers set up for each of the functions we need. perhaps a vout_Control type could take care of all these things in the vout_renderer.
paramaters that should be handled this way are at least: alignment, AR, crop, pad

== Misc ==

* Vout plugins (that provide vout windows) should allow reusing a vout by reusing it. This would much improve the experience)
* Vout windows must have a flag to tell if they are "main" or "helper" (audio visualization, ...). Helper vouts should get no OSD (if another vout is present) and should not "steal" the accelerated vout"
* 4:3, 16:9, freeform Aspect Ratio
* cropping and padding (do at OS level, but provide a core call to set it up and configure).
* better hotkeys integration : need hotkey module redesign to act on selected vout and relevant input instead of the first we find

VoutRework

2005-08-28T13:27:04Z

The DJ: /* OSD and subpictures */

VoutRework

2005-08-28T13:19:26Z

The DJ: /* Overall architecture */

We Use VideoLAN

2005-08-21T15:06:08Z

The DJ:

Do you have some cool project you use VideoLAN for?
Post a link and a small description here.

'''The Balloon'''
[http://www.maveric.org.uk/mavhome.html JediMaster and friends] are building a Mars balloon which uses VideoLAN to stream images back to earth.
http://www.maveric.org.uk/photos/testing/

'''Distributed VideoLAN Server Management'''
Bart Kerver from [[SURFnet]] has created software to manage multiple VideoLAN servers.
http://speeldoos.showcase.surfnet.nl/dvlsm/

'''Cypherpunk version of MacBeth'''
People at [http://www.pirateutopia.org/ Pirate Utopia] are using VLC in a MacBeth-inspired show to display ASCII-art video.
http://www.pirateutopia.org/macbeth/techie.htm

'''Neutrino MoviePlayer'''
The [http://www.dbox2.info Neutrino] [http://www.giggo.de/dbox2/movieplayer.html MoviePlayer] now uses VLC so users can stream the movies on their computer to a a DBox.

'''Advene project'''
[http://liris.cnrs.fr/advene/index_en.html Advene] (Annotate DVDs, Exchange on the Net) aims at providing a format to share annotations about movies stored on DVDs, as well as tools to edit and visualize the annotations. It uses VLC to play/extract info from the DVD's

'''Las Vegas Security Lines'''
On the Las Vegas Airport, people in line for the security checks are treated to some 'how to keep the line as short as possible' movies. These movies are being streamed with VLC.
[http://www.usatoday.com/travel/news/2004-10-05-vegas-airport_x.htm An article about this project]

'''Plutohome'''
[http://plutohome.com/ They] have a vlc module for their system. Exact use unknown

'''ACTlab.tv'''
[http://actlab.tv/technology.htm They] are probably using x264 for their video encoding

'''Participatory Culture Foundation'''
[http://www.participatoryculture.org/ DTV] is a webbased player for their RSS based videoblogging system that uses our mozilla plugin

'''Annodex'''
[http://annodex.net Annodex] is a system for metadata, hyperlinking and browing media content. Their webmodule uses a customized version of our mozilla plugin

'''Google, inc.'''
As [http://www.boingboing.net/2005/06/26/google_to_launch_onl.html announced] [http://battellemedia.com/archives/001658.php recently], [http://video.google.com Google's video search] will feature video playback, by using VLC as a browser plugin.

'''Tryst'''
This [http://www.trystx.com/index.html application] is based on VLC and uses Bonjour announcements to share video broadcasts.

'''VLC Controller'''
[http://www.snarb.tk/ Extension] to Sailing Clicker to allow you to use a PDA or phone to control VLC trough a bluetooth connection.

'''VLC romeo plugins'''
[http://homepage.mac.com/WebObjects/FileSharing.woa/wa/default?user=srouet&templatefn=FileSharing4.html&xmlfn=TKDocument.4.xml&sitefn=RootSite.xml&aff=consumer&cty=US&lang=en Plugins] to use Romeo to control VLC trough a bluetooth PDA or phone.

'''VLC Remote'''
A very nice Dashboard widget that uses the VLC webinterface to control a remote VLC. [http://www.autopoetic.com/vlcremote/ VLC remote hompage].

We Use VideoLAN

2005-08-21T15:05:16Z

The DJ:

Do you have some cool project you use VideoLAN for?
Post a link and a small description here.

'''The Balloon'''
[http://www.maveric.org.uk/mavhome.html JediMaster and friends] are building a Mars balloon which uses VideoLAN to stream images back to earth.
http://www.maveric.org.uk/photos/testing/

'''Distributed VideoLAN Server Management'''
Bart Kerver from [[SURFnet]] has created software to manage multiple VideoLAN servers.
http://speeldoos.showcase.surfnet.nl/dvlsm/

'''Cypherpunk version of MacBeth'''
People at [http://www.pirateutopia.org/ Pirate Utopia] are using VLC in a MacBeth-inspired show to display ASCII-art video.
http://www.pirateutopia.org/macbeth/techie.htm

'''Neutrino MoviePlayer'''
The [http://www.dbox2.info Neutrino] [http://www.giggo.de/dbox2/movieplayer.html MoviePlayer] now uses VLC so users can stream the movies on their computer to a a DBox.

'''Advene project'''
[http://liris.cnrs.fr/advene/index_en.html Advene] (Annotate DVDs, Exchange on the Net) aims at providing a format to share annotations about movies stored on DVDs, as well as tools to edit and visualize the annotations. It uses VLC to play/extract info from the DVD's

'''Las Vegas Security Lines'''
On the Las Vegas Airport, people in line for the security checks are treated to some 'how to keep the line as short as possible' movies. These movies are being streamed with VLC.
[http://www.usatoday.com/travel/news/2004-10-05-vegas-airport_x.htm An article about this project]

'''Plutohome'''
[http://plutohome.com/ They] have a vlc module for their system. Exact use unknown

'''ACTlab.tv'''
[http://actlab.tv/technology.htm They] are probably using x264 for their video encoding

'''Participatory Culture Foundation'''
[http://www.participatoryculture.org/ DTV] is a webbased player for their RSS based videoblogging system that uses our mozilla plugin

'''Annodex'''
[http://annodex.net Annodex] is a system for metadata, hyperlinking and browing media content. Their webmodule uses a customized version of our mozilla plugin

'''Google, inc.'''
As [http://www.boingboing.net/2005/06/26/google_to_launch_onl.html announced] [http://battellemedia.com/archives/001658.php recently], [http://video.google.com Google's video search] will feature video playback, by using VLC as a browser plugin.

'''Tryst'''
This [http://www.trystx.com/index.html application] is based on VLC and uses Bonjour announcements to share video broadcasts.

'''VLC Controller'''
[http://www.snarb.tk/ Extension] to Sailing Clicker to allow you to use a PDA or phone to control VLC trough a bluetooth connection.

''VLC romeo plugins''
[http://homepage.mac.com/WebObjects/FileSharing.woa/wa/default?user=srouet&templatefn=FileSharing4.html&xmlfn=TKDocument.4.xml&sitefn=RootSite.xml&aff=consumer&cty=US&lang=en Plugins] to use Romeo to control VLC trough a bluetooth PDA or phone.

'''VLC Remote'''
A very nice Dashboard widget that uses the VLC webinterface to control a remote VLC. [http://www.autopoetic.com/vlcremote/ VLC remote hompage].

We Use VideoLAN

2005-07-25T12:30:51Z

The DJ:

VideolanStringGuidelines

2005-07-01T13:27:19Z

The DJ: /* Misc */

Draft 0.1

These goal of these guidelines is to ensure that all configuration and interface strings will be consistent, well-written and well-translated, ensuring a better user experience (bwahaha)

= Developers =

== Write correct English ==

Many VLC developers are not native English speakers, which often leads
to badly written strings.

Please always have your strings proofread, preferably by a native English
speaker (even if you are one yourself).

== Avoid technical jargon as much as possible ==

If some terms sound common to you, they may be impossible to understand
for others. If you cannot avoid using them, try explaining them
(for configuration options, use the extended descriptions, for interfaces,
use tooltips). Try not being too verbose either.

Of course, some advanced concepts are quite hard to explain. Don't try too much explaining things, and don't hesitate to ask the user to read the documentation.

== Make your string translatable if needed ==

Only strings that can be visible in the GUI must be translated:
* interface description
* module descriptions / longnames
* configuration options
* "mms://", "http://", "UDP", "RTP" don't need to be translated
* module shortcuts and shortnames must not be made translatable
* Debug messages must not be made translatable.

* _("") makes a string translatable and also actually does translation (calls gettext)
* _NS("") is the macosx variant of _(""). it is a short of [NSApp localizedString: ""] There is also a [NSApp delocalizeString:@""] OSX is entirely UTF8 native.
* N_() only makes a string translatable. it is safe to use it in #defines and in arrays. Also use this when translating strings during the creation of config variables.
* Try to keep strings UTF8 where possible, to make sure a string can be displayed in chinese just as easily as in english in your window.
* wxU is used for c UTF8 strings to unicode conversion. wxL2U transforms from current locale to unicode.

== Use correct syntax ==

* Sentences must end with a '.'
* All GUI strings should begin with a Capital letter :
** module names
** short and long descriptions
** menu items
* Debug messages don't start with a capital
* For menu items, put a Capital At Each Word.
* Put a space after ',' ';' ':' '.' '?' and '!'. There is no space before these characters
* ...

== Configuration option descriptions specifics ==

Configuration option descriptions have two parts: a short description and a long one.

=== The short description ===

The short description must be kept short (40 characters seems to be a maximum). Don't forget that translations are often longer than the english version.

The short description should be self-understanding for an advanced user.
The short description must not be a full sentence and does not contain questionmarks or words like "setting". It is logical that it is a setting, it is in the preferences.

=== The long description ===

The long description should not just repeat the short description (and in most cases, not repeat it at all). This is pointless and probably proves that your descriptions are not properly thought.

The extended description should _generally_ use complete sentences. Use of paragraphs is encouraged to improve readbility and separate ideas.

Don't be too verbose. This would clutter the help output and the interfaces.

Avoid using structures like : "Please choose", "select", "specify"

Bad: "Please specify an integer for foo"
Good: "An integer for foo, which is ..."

=== c. Specifics ===

* String, integer, float:
The short description should be a prompt, never a question
** Bad : "IP Address ?" or "Which channel ?"
** Good: "IP Address: " or "Channel: "
The short description must include range and unit, if available
Exemple: "Frequency (1000-20000 Hz)"
The long description should rather explain what the user should enter rather
than merely rephrasing the short description

* Multi-select choices:
Use a prompt. Do not use "please choose" or "please select", the user can
guess that...

* Booleans
The short description should be a question
"Video overlay ?"
For the long description, please prefer "Enable foo to get bar" rather than
"If you enable foo, you will get bar" (which produces long heavy sentences)

== Misc ==

* msg_Dbg can be quite cryptic. msg_Warn, msg_Info and msg_Err MUST be explicit and understandable
* All strings in all languages should be gender-neutral
* You should never use the first person (neither "I" nor "we"). Computers don't speak and our strings don't speak for the VideoLAN team
* Passive voice should be prefered over second person: Use "When this option is enabled" rather "If you enable this option"
* Try reusing strings. This avoids translation efforts and improves consistency
* Don't make assumptions on the way interfaces are organized. Don't forget your strings should apply to the command line and to the GUI. So don't use "If you choose yes", "If you tick this checkbox"

== Common translations ==

[TODO: Gather them in the wiki]

= Translators =

All user-visible strings are translated. Debug messages are not.

== Don't desperately try to translate ==

Many video specific terms have no equivalent in other langages. Don't desperately try to translate them. It often leads to quite ridiculous expressions.

What you can do is quote the english word in the short description / menu item and explain it in your own words in the long description / tooltip, without trying to translate word for word.

== Test your translation ==

Compile your translation and enable it (this is explained on the developers page). You should particularly look for overflows (too long translated strings).

If you feel you can't reduce the size of your string, you should contact the developer(s) so that the problem can be solved smoothly

== Consistency ==

It is recommended to choose translations for command terms and to use them everywhere. You should probably use the wiki [TODO]

VideolanStringGuidelines

2005-07-01T13:22:44Z

The DJ: /* The short description */

Draft 0.1

These goal of these guidelines is to ensure that all configuration and interface strings will be consistent, well-written and well-translated, ensuring a better user experience (bwahaha)

= Developers =

== Write correct English ==

Many VLC developers are not native English speakers, which often leads
to badly written strings.

Please always have your strings proofread, preferably by a native English
speaker (even if you are one yourself).

== Avoid technical jargon as much as possible ==

If some terms sound common to you, they may be impossible to understand
for others. If you cannot avoid using them, try explaining them
(for configuration options, use the extended descriptions, for interfaces,
use tooltips). Try not being too verbose either.

Of course, some advanced concepts are quite hard to explain. Don't try too much explaining things, and don't hesitate to ask the user to read the documentation.

== Make your string translatable if needed ==

Only strings that can be visible in the GUI must be translated:
* interface description
* module descriptions / longnames
* configuration options
* "mms://", "http://", "UDP", "RTP" don't need to be translated
* module shortcuts and shortnames must not be made translatable
* Debug messages must not be made translatable.

* _("") makes a string translatable and also actually does translation (calls gettext)
* _NS("") is the macosx variant of _(""). it is a short of [NSApp localizedString: ""] There is also a [NSApp delocalizeString:@""] OSX is entirely UTF8 native.
* N_() only makes a string translatable. it is safe to use it in #defines and in arrays. Also use this when translating strings during the creation of config variables.
* Try to keep strings UTF8 where possible, to make sure a string can be displayed in chinese just as easily as in english in your window.
* wxU is used for c UTF8 strings to unicode conversion. wxL2U transforms from current locale to unicode.

== Use correct syntax ==

* Sentences must end with a '.'
* All GUI strings should begin with a Capital letter :
** module names
** short and long descriptions
** menu items
* Debug messages don't start with a capital
* For menu items, put a Capital At Each Word.
* Put a space after ',' ';' ':' '.' '?' and '!'. There is no space before these characters
* ...

== Configuration option descriptions specifics ==

Configuration option descriptions have two parts: a short description and a long one.

=== The short description ===

The short description must be kept short (40 characters seems to be a maximum). Don't forget that translations are often longer than the english version.

The short description should be self-understanding for an advanced user.
The short description must not be a full sentence and does not contain questionmarks or words like "setting". It is logical that it is a setting, it is in the preferences.

=== The long description ===

The long description should not just repeat the short description (and in most cases, not repeat it at all). This is pointless and probably proves that your descriptions are not properly thought.

The extended description should _generally_ use complete sentences. Use of paragraphs is encouraged to improve readbility and separate ideas.

Don't be too verbose. This would clutter the help output and the interfaces.

Avoid using structures like : "Please choose", "select", "specify"

Bad: "Please specify an integer for foo"
Good: "An integer for foo, which is ..."

=== c. Specifics ===

* String, integer, float:
The short description should be a prompt, never a question
** Bad : "IP Address ?" or "Which channel ?"
** Good: "IP Address: " or "Channel: "
The short description must include range and unit, if available
Exemple: "Frequency (1000-20000 Hz)"
The long description should rather explain what the user should enter rather
than merely rephrasing the short description

* Multi-select choices:
Use a prompt. Do not use "please choose" or "please select", the user can
guess that...

* Booleans
The short description should be a question
"Video overlay ?"
For the long description, please prefer "Enable foo to get bar" rather than
"If you enable foo, you will get bar" (which produces long heavy sentences)

== Misc ==

* msg_Dbg can be quite cryptic. msg_Warn, msg_Info and msg_Err MUST be explicit and understandable
* All strings in all languages should be gender-neutral
* You should never use the first person (neither "I" nor "we"). Computers don't speak and our strings don't speak for the VideoLAN team
* Passive voice should be prefered over second person: Use "If this option is enabled" rather "If you enable this option"
* Try reusing strings. This avoids translation efforts and improves consistency
* Don't make assumptions on the way interfaces are organized. Don't forget your strings should apply to the command line and to the GUI. So don't use "If you choose yes", "If you tick this checkbox"

== Common translations ==

[TODO: Gather them in the wiki]

= Translators =

All user-visible strings are translated. Debug messages are not.

== Don't desperately try to translate ==

Many video specific terms have no equivalent in other langages. Don't desperately try to translate them. It often leads to quite ridiculous expressions.

What you can do is quote the english word in the short description / menu item and explain it in your own words in the long description / tooltip, without trying to translate word for word.

== Test your translation ==

Compile your translation and enable it (this is explained on the developers page). You should particularly look for overflows (too long translated strings).

If you feel you can't reduce the size of your string, you should contact the developer(s) so that the problem can be solved smoothly

== Consistency ==

It is recommended to choose translations for command terms and to use them everywhere. You should probably use the wiki [TODO]

VideolanStringGuidelines

2005-07-01T13:20:15Z

The DJ: /* Use correct syntax */

Draft 0.1

These goal of these guidelines is to ensure that all configuration and interface strings will be consistent, well-written and well-translated, ensuring a better user experience (bwahaha)

= Developers =

== Write correct English ==

Many VLC developers are not native English speakers, which often leads
to badly written strings.

Please always have your strings proofread, preferably by a native English
speaker (even if you are one yourself).

== Avoid technical jargon as much as possible ==

If some terms sound common to you, they may be impossible to understand
for others. If you cannot avoid using them, try explaining them
(for configuration options, use the extended descriptions, for interfaces,
use tooltips). Try not being too verbose either.

Of course, some advanced concepts are quite hard to explain. Don't try too much explaining things, and don't hesitate to ask the user to read the documentation.

== Make your string translatable if needed ==

Only strings that can be visible in the GUI must be translated:
* interface description
* module descriptions / longnames
* configuration options
* "mms://", "http://", "UDP", "RTP" don't need to be translated
* module shortcuts and shortnames must not be made translatable
* Debug messages must not be made translatable.

* _("") makes a string translatable and also actually does translation (calls gettext)
* _NS("") is the macosx variant of _(""). it is a short of [NSApp localizedString: ""] There is also a [NSApp delocalizeString:@""] OSX is entirely UTF8 native.
* N_() only makes a string translatable. it is safe to use it in #defines and in arrays. Also use this when translating strings during the creation of config variables.
* Try to keep strings UTF8 where possible, to make sure a string can be displayed in chinese just as easily as in english in your window.
* wxU is used for c UTF8 strings to unicode conversion. wxL2U transforms from current locale to unicode.

== Use correct syntax ==

* Sentences must end with a '.'
* All GUI strings should begin with a Capital letter :
** module names
** short and long descriptions
** menu items
* Debug messages don't start with a capital
* For menu items, put a Capital At Each Word.
* Put a space after ',' ';' ':' '.' '?' and '!'. There is no space before these characters
* ...

== Configuration option descriptions specifics ==

Configuration option descriptions have two parts: a short description and a long one.

=== The short description ===

The short description must be kept short (40 characters seems to be a maximum). Don't forget that translations are often longer than the english version.

The short description should be self-understanding for an advanced user.
The short description must not be a full sentence.

=== The long description ===

The long description should not just repeat the short description (and in most cases, not repeat it at all). This is pointless and probably proves that your descriptions are not properly thought.

The extended description should _generally_ use complete sentences. Use of paragraphs is encouraged to improve readbility and separate ideas.

Don't be too verbose. This would clutter the help output and the interfaces.

Avoid using structures like : "Please choose", "select", "specify"

Bad: "Please specify an integer for foo"
Good: "An integer for foo, which is ..."

=== c. Specifics ===

* String, integer, float:
The short description should be a prompt, never a question
** Bad : "IP Address ?" or "Which channel ?"
** Good: "IP Address: " or "Channel: "
The short description must include range and unit, if available
Exemple: "Frequency (1000-20000 Hz)"
The long description should rather explain what the user should enter rather
than merely rephrasing the short description

* Multi-select choices:
Use a prompt. Do not use "please choose" or "please select", the user can
guess that...

* Booleans
The short description should be a question
"Video overlay ?"
For the long description, please prefer "Enable foo to get bar" rather than
"If you enable foo, you will get bar" (which produces long heavy sentences)

== Misc ==

* msg_Dbg can be quite cryptic. msg_Warn, msg_Info and msg_Err MUST be explicit and understandable
* All strings in all languages should be gender-neutral
* You should never use the first person (neither "I" nor "we"). Computers don't speak and our strings don't speak for the VideoLAN team
* Passive voice should be prefered over second person: Use "If this option is enabled" rather "If you enable this option"
* Try reusing strings. This avoids translation efforts and improves consistency
* Don't make assumptions on the way interfaces are organized. Don't forget your strings should apply to the command line and to the GUI. So don't use "If you choose yes", "If you tick this checkbox"

== Common translations ==

[TODO: Gather them in the wiki]

= Translators =

All user-visible strings are translated. Debug messages are not.

== Don't desperately try to translate ==

Many video specific terms have no equivalent in other langages. Don't desperately try to translate them. It often leads to quite ridiculous expressions.

What you can do is quote the english word in the short description / menu item and explain it in your own words in the long description / tooltip, without trying to translate word for word.

== Test your translation ==

Compile your translation and enable it (this is explained on the developers page). You should particularly look for overflows (too long translated strings).

If you feel you can't reduce the size of your string, you should contact the developer(s) so that the problem can be solved smoothly

== Consistency ==

It is recommended to choose translations for command terms and to use them everywhere. You should probably use the wiki [TODO]

2005StringsReview

2005-06-30T17:56:38Z

The DJ: /* People interested */

This page is the central coordination point of the Summer 2005 Strings review campaign

== People interested ==

* zorglub
* nirnimesh
* xtophe
* dionoea
* thedj (on holiday until 19th of july)

== Work division ==

{| border="1" cellspacing="0"
! Module || First reviewer || Second reviewer || Current status
|-
|modules/access*|| || ||
|-
|modules/demux|| || ||
|-
|modules/codec|| || ||
|-
|modules/mux|| || ||
|-
|modules/stream_out|| || ||
|-
|modules/packetizer|| || ||
|-
|modules/audio*|| || ||
|-
|modules/control/rc.c|| || ||
|-
|modules/control/telnet.c|| || ||
|-
|modules/control/...|| || ||
|-
|modules/gui/skins2|| || ||
|-
|modules/gui/macosx|| || ||
|-
|modules/gui/wxwindows|| || ||
|-
|modules/misc|| || ||
|-
|modules/video*|| || ||
|-
|modules/services_discovery|| || ||
|-
|modules/visualization|| || ||
|-
|modules/misc|| || ||
|-
|src/libvlc.h|| || ||
|-
|src/...|| || ||
|-
|include/vlc_config_cat.h|| || ||
|-
|include/...|| || ||
|-
|mozilla|| || ||
|-
|activex|| || ||
|}

== Resources ==

[[VideolanStringGuidelines]]

What can VLC do?

2005-06-27T23:39:55Z

The DJ: /* How to adjust picture brightness/colors/contrast.. */

This area of the wiki contains a list with the possibilities videolan gives you. It was made to help ppl better realize the potential vlc has. Some entries will simply mention the possibility, others try to explain how to do it as well. Let me start by apologising for my horrible spelling, but i hope you will be able to decipher the texts anyway :)

== Mediaplayer ==

=== Play DVD/SVCD/VCD iso's / Images ===
If you have a DVD/SVCD/VCD packaged inside an image/iso file vlc can play this without you having to mount it or extract it in anyway. You can simply chose open file and pick the iso file. This is true for the standard .iso and .img files, not if its some proprietary format which is specific to a certain program (For example NERO's .nrg)

=== How to enable/use subtitles ===

Before you try to enable subtitles make sure the subtitles you have are in a format that VLC can read! You can find the list of compatible subtitle formats [http://www.videolan.org/vlc/features.html here].
If VLC has detected any sort of subtitles available, you will be able to turn them on under the menu: ''Video->Subtitles track->Track 1''

If you mainly use .srt subtitles or .sub, you can get them turned on automatically when they are detected, by setting the ''Input/Codecs->Advanced->Choose subtitle track'' to 0, it will automaticly turn on the subtitle track. You can also experiment with the ''Choose subtitle language'' on the same page. But if u experiment a bit with the settings u should be able to get subtitles turned on automatically.

=== Playing windows media files ===
VLC should be able to succesfully play both audio and video in wma and wmv 1 and 2, for the newest version (wmv3) only the windows version of vlc will be able to play it, since no opensource implementation of wmv3 have been made so far, so the windows vlc plays it by using the windows api. DRM files however can not be played on any OS.

=== How to adjust picture brightness/colors/contrast.. ===

'''If you are using the wxwindows userinterface:'''

You can adjust the typical values to tweak the picture of your video source by turning on the extended GUI. This is done in the menu: ''Settings->Extended GUI''. That will give you some extended control options for the video picture as well as an equalizer for the audio.

'''If you use Mac OS X or a skinned version of VLC:'''
You need to enter the preference menu: ''Settings->Preferences''. Once you have the preferences window open you go to: <u>Video->Filters->Image adjust</u>. Here you can adjust the different values. Note before they take effect you need to turn on the "Image adjust" filter in: <u>Video->Filters</u>

== Streaming - client ==

=== Listen to online radio ===
You can ofcourse always simply find a link to a radiostream and then open it as you would any other network stream in vlc. But if u would like to browse a list of online radios, you can try the list of shoutcast radio stations vlc can download for you. First you need top open the playlist window: View->Playlist. Once you have the playlist window open chose: ''Manage->Service discovery->Shoutcast radio listings''. After 10 seconds or so the playlist should have become populated by radio station entries. You obviously require internet access for this to work! If you want the stations sorted alphabetically, you can chose: ''Sort->Sort by title''. Also note shoutcast have many thousands stream availeble, per default in 0.8.2 250 stations are downloaded, this can be changed in the preferences under: <u>Playlist->Service discovery->Shoutcast</u>. Note that the more stations u want to add, the longer delay u will see when the station list is downloaded parsed and added to the playlist. Also note you should see 2 "Folder nodes" in the playlist under shoutcast called Genres and bitrate where the stations will be listed under their respective areas. Note that most stations claim to be multi genre, so a station might be listed under both Top40, pop and rock.

== Streaming - server ==

== Capture / Record things==

What can VLC do?

2005-06-27T23:38:12Z

The DJ: /* How to enable/use subtitles */

This area of the wiki contains a list with the possibilities videolan gives you. It was made to help ppl better realize the potential vlc has. Some entries will simply mention the possibility, others try to explain how to do it as well. Let me start by apologising for my horrible spelling, but i hope you will be able to decipher the texts anyway :)

== Mediaplayer ==

=== Play DVD/SVCD/VCD iso's / Images ===
If you have a DVD/SVCD/VCD packaged inside an image/iso file vlc can play this without you having to mount it or extract it in anyway. You can simply chose open file and pick the iso file. This is true for the standard .iso and .img files, not if its some proprietary format which is specific to a certain program (For example NERO's .nrg)

=== How to enable/use subtitles ===

Before you try to enable subtitles make sure the subtitles you have are in a format that VLC can read! You can find the list of compatible subtitle formats [http://www.videolan.org/vlc/features.html here].
If VLC has detected any sort of subtitles available, you will be able to turn them on under the menu: ''Video->Subtitles track->Track 1''

If you mainly use .srt subtitles or .sub, you can get them turned on automatically when they are detected, by setting the ''Input/Codecs->Advanced->Choose subtitle track'' to 0, it will automaticly turn on the subtitle track. You can also experiment with the ''Choose subtitle language'' on the same page. But if u experiment a bit with the settings u should be able to get subtitles turned on automatically.

=== Playing windows media files ===
VLC should be able to succesfully play both audio and video in wma and wmv 1 and 2, for the newest version (wmv3) only the windows version of vlc will be able to play it, since no opensource implementation of wmv3 have been made so far, so the windows vlc plays it by using the windows api. DRM files however can not be played on any OS.

=== How to adjust picture brightness/colors/contrast.. ===

'''If you are using the wxwindows userinterface:'''

You can adjust the typical values to tweak the picture of your video source by turning on the extended GUI. This is done in the menu: ''Settings->Extended GUI''. That will give you some extended control options for the video picture as well as an equalizer for the audio.

'''If you use a skinned version of vlc:'''
Then you are using the skins2 interface, and it is a little more complicated. You need to enter the preference menu: ''Settings->Preferences''. Once you have the preferences window open you go to: <u>Video->Filters->Image adjust</u>. Here you can adjust the different values. Note before they take effect you need to turn on the "Image adjust" filter in: <u>Video->Filters</u>

== Streaming - client ==

=== Listen to online radio ===
You can ofcourse always simply find a link to a radiostream and then open it as you would any other network stream in vlc. But if u would like to browse a list of online radios, you can try the list of shoutcast radio stations vlc can download for you. First you need top open the playlist window: View->Playlist. Once you have the playlist window open chose: ''Manage->Service discovery->Shoutcast radio listings''. After 10 seconds or so the playlist should have become populated by radio station entries. You obviously require internet access for this to work! If you want the stations sorted alphabetically, you can chose: ''Sort->Sort by title''. Also note shoutcast have many thousands stream availeble, per default in 0.8.2 250 stations are downloaded, this can be changed in the preferences under: <u>Playlist->Service discovery->Shoutcast</u>. Note that the more stations u want to add, the longer delay u will see when the station list is downloaded parsed and added to the playlist. Also note you should see 2 "Folder nodes" in the playlist under shoutcast called Genres and bitrate where the stations will be listed under their respective areas. Note that most stations claim to be multi genre, so a station might be listed under both Top40, pop and rock.

== Streaming - server ==

== Capture / Record things==