VideoLAN Wiki - User contributions [en]

Git

2009-10-19T00:07:24Z

Hillbilly1980: /* Convert your tree to use your ssh push commit access */

= Basic Git usage =

If you are using '''Windows''', please read the [[Git_Windows]] page.

== Getting VLC or x264 source code via Git ==

$ git clone git://git.videolan.org/vlc.git
Voilà! The full VLC history should be on your hard disk in vlc/.

$ git clone git://git.videolan.org/x264.git
Voilà! The full x264 history should be on your hard disk in x264/.

If you want only the last 3 VLC revisions:
$ git clone git://git.videolan.org/vlc.git --depth 3

You can also clone using http with our repo.or.cz mirror.
$ git clone http://repo.or.cz/r/vlc.git

$ git log
to see the full log of the trunk.
$ gitk
to see the log graphically.

You can also browse the sources via [http://git.videolan.org/ gitweb].

== Configure your global git config ==
May need to use
$ git repo-config {various options}
1.4.4.2 Requires the repo-config command rather than just config

=== Personal Information ===
Tell git your name. (use mostly by git-commit)
$ git config --global user.name "Your Name"
$ git config --global user.email "me@example.com"

=== Using git with color (Tip) ===
If you want to use git with colored output use:
$ git config --global color.ui true

If you are using an old git version (prior to 1.5.5) and previous command didn't work, use:
$ git config --global color.diff auto
$ git config --global color.status auto
$ git config --global color.branch auto

=== Setting up "git up" (Tip) ===
If you want to be able to just keep in sync using "git up" use:
$ git config --global alias.up "pull --rebase"
And if you like your tree to be messy and don't want git to complain (like in svn) use:
$ git config --global alias.up '!sh -c "git commit -a -m "Before rebase" && git pull --rebase && git reset head^"'

=== Setting up "git wu" (Git What's Up) (Tip) ===
If you want to see what you are about to "git push":
$ git config --global alias.wu "log --stat origin..@{0}"
Now use:
$ git wu

=== Setting up "git wup" (Git What's Up - with patch) (Tip) ===
If you want to see what you are about to "git push", along with the diff:
$ git config --global alias.wup "log -p origin..@{0}"
Now use:
$ git wup

== General GIT Workflow ==
1. Make your file edits in your local repository.

2. "git commit" the changes in your local repository

3. "git pull --rebase" or "git up" (if you did ''git config --global alias.up "pull --rebase"'') to bring the rest of your local repository up to date

4. "git log origin..master" to check what you are going to commit

4. "git push" to move your changes up to the master

"git stash" if you want to "hide" your changes. Do this if you think there may be other commits against the same things you are working on and want to refresh your local checkout (using a git pull --rebase) from the master. Use "git stash apply" to get your stash back.

"git checkout -f master" if you think your tree is pretty hopeless, need a kill-and-fill to bring the master into your local repository.

== List the local branch ==
You can now list your local branch by doing
$ git branch
which should ouput
$ git branch
* master

== List your local non committed changes ==
$ git status | less

== Commit ==
Now you can start to work on your tree. As soon as you feel you have reached a step in developement where you can commit your work '''locally''', use
$ git commit -a
or
$ git commit <specific files>

If you wish to give credit to someone else's work (e.g. you are applying a third party patch):
$ git commit <specific files> --author "Name Surname <user@domain.com>"

== List your commits ==
$ git log

== Keeping your local working branch in sync ==
$ git pull --rebase

To shorten up that command type
$ git config --global alias.up "pull --rebase"

Now you can just type:
$ git up

== Use a graphical interface ==
$ gitk # Tree Browser
$ qgit # Tree Browser
$ git-gui # Commit/push/... editor

== Submitting patches to the vlc-devel or x264-devel ==

First make sure you have '''read''' our [[Sending Patches]] page. And that you've '''read''' the [[Sending Patches#Check_List| Check List]].

If you have been developing on vlc locally and (still) don't have write access, you can submit all your commits in one shot using:
$ rm -Rf patches
$ git format-patch -o patches origin
$ git-send-email --to vlc-devel@videolan.org patches
If you have multiple patch consider using:
$ git-send-email --compose --no-chain-reply-to --to vlc-devel@videolan.org patches
This will produce the patches for each local commit in the directory "patches" and send them.
Use --no-chain-reply-to make sure it doesn't reply.

For x264, do the same with x264-devel@videolan.org


Don't do:
* [PATCH 0/m]
** [PATCH 1/m]
*** [PATCH 2/m]
**** ...
But do:
* [PATCH 0/m]
** [PATCH 1/m]
** [PATCH 2/m]
** ..

= Advanced usage =
== Creating a secondary local branch ==
If you want to work on a specific project that could require a branch of the trunk, create a local branch of the current branch by doing:
$ git branch mywork
and to actually use it do:
$ git checkout mywork
Which could be summarized by:
$ git checkout -b mywork

Then do some commit on it... And you can go back to your original master branch by doing:
$ git checkout master

== Fetching a remote branch ==
To see the remote branch use:
$ git branch -r
If the remote branch is named 0.8.6-bugfix
$ git branch 0.8.6-bugfix origin/0.8.6-bugfix
Branch 0.8.6-bugfix set up to track remote branch refs/remotes/origin/0.8.6-bugfix.
$ git branch
0.8.6-bugfix
* master
To checkout that branch use:
$ git checkout 0.8.6-bugfix
To stay up-to-date a simple
$ git pull --rebase
Should be enough.

If warnings appear that files still need updating:
$ include/libvlc_internal.h: needs update
include/mediacontrol_internal.h: needs update
include/vlc/libvlc.h: needs update
include/vlc_update.h: needs update
modules/access/mms/mms.c: needs update
...

Then do a checkout -f to revert non committed local changes
$ git checkout -f

To stay up-to-date another
$ git pull --rebase
Should give no more warnings.

To push to the remote branch, use:
$git push origin 0.8.6-bugfix:0.8.6-bugfix

== Creating a remote branch ==
If the new remote branch is named 0.9.0-bugfix, and is based on the local master branch.
First make sure everything go as planned with the --dry-run option:
$ git push --dry-run origin master:refs/heads/0.9.0-stable
To git@git.videolan.org:vlc.git
* [new branch] master -> 0.9.0-stable

Then push it:
$ git push origin master:refs/heads/0.9.0-stable
To git@git.videolan.org:vlc.git
* [new branch] master -> 0.9.0-stable
$ git branch -r
origin/0.9.0-stable
origin/master

To checkout that branch now see ''Fetching a remote branch''

== Publishing your own fork ==
Goto [http://repo.or.cz/w/vlc.git http://repo.or.cz/w/vlc.git] and click [http://repo.or.cz/m/regproj.cgi?name=vlc/ fork]. You will be able to publish your work there.

Please don't forget to send a mail to the vlc-devel as soon as you create your fork.

== Revert your non-committed local changes ==
$ git checkout -f

==Edit or undo not yet pushed commits ==
This will undo the last commit
$ git reset HEAD^
which is the same as
$ git reset master^
(if your checked-out copy of your tree is master)
And also the same as
$ git reset a44a594 # note that there is no need to use the full sha id

If you have a stack of patch that you have not yet committed you can delete one patch from the list using git rebase --interactive
$ git rebase --interactive origin
pick eacf185 test
pick 56322eb VLMA owner is vlma prod.

# Rebase 826757e..56322eb onto 826757e
#
# Commands:
# pick = use commit
# edit = use commit, but stop for amending
# squash = use commit, but meld into previous commit

== Diff-ing ==
* You can diff between two branches using
$ git diff branch1 branch2
* You can diff between the previous 10th commit and current using
$ git diff HEAD~10 HEAD
* You can diff between the previous 10th commit and current of the branch "mywork" using
$ git diff mywork~10 mywork
* Imagine that git log is like
$ git log
commit e0394f269305edd09843257e7c1d1a66aaf48ab3
Author: jb <jb>
Date: Fri Apr 13 07:14:48 2007 +0000
qt4 - Mousewheel (2)
commit e80b339081aa6755f67c9bd8e2aacf93a9a79d95
[..]
commit ff7004b70fd239e4120deb160e2991bd5237b8df
[..]
commit a44a594898f981a145cfcace5f16f8973f9eb46f
[..]
commit 690df705c963cf6bf6f5746d54bc97a85ff91919
[..]
commit 679f8b1c3e0baa469efa970588b95a625c595d64
[..]

$ git diff a44a594898f981a145cfcace5f16f8973f9eb46f~2 e80b339081aa6755f67c9bd8e2aacf93a9a79d95
Will be equivalent to:
$ git diff ff7004b70fd239e4120deb160e2991bd5237b8df e80b339081aa6755f67c9bd8e2aacf93a9a79d95
And to:
$ git diff HEAD~4 HEAD^

* Remember that to produce a patch you should rather use git-format-patch than git-diff most of the time.

== Patch-ing ==
* You can apply patches using
$ git apply <patch>

== Tracking regression ==
git has a great tool called [http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html git-bisect] to help you to track a faulty commit. Imagine you are tracking a bug that is known to appear after 0.8.6 (assuming 0.8.6 is tagged):
$ git bisect start
$ git bisect bad # tell git current version has the bug you are tracking
$ git bisect good 0.8.6 # tell git 0.8.6 didn't has the bug
And then git will checkout a certain revision, and ask you to test it. And you simply say whether this version has the bug.
If it has the bug:
$ git bisect bad
if the bug is not present:
$ git bisect good
And so on by bisection... At the end git will indicate the faulty commit. Most of the time this tool is really efficient to track regression.

If you can provide a script that test the presence of the bug
$ git bisect run <script_name>
will be able to track down the regression by itself. See [http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html git-bisect Documentation].

= Using Git to push to VideoLAN git =
== Initial requirement ==
* Make sure you've set your name and email in your commits
$ git config --global user.name "Your Name"
$ git config --global user.email "me@example.com"

== Convert your tree to use your ssh push commit access ==
$ vi vlc/.git/config
And replace
git://git.videolan.org/vlc.git
With
git://git@git.videolan.org:vlc.git

== Staying up to date ==
$ git pull --rebase

If you don't want to have to type --rebase everytime you pull do:
$ git config branch.master.rebase true

This one creates a merge object which is not how SVN worked, so let's use the first version...
$ git pull

== Pushing your work ==
$ git log origin..master # Check what you are going to push
$ git push



= Documentation about git =
* [http://git.or.cz/ Official Git Website]
* [http://www.kernel.org/pub/software/scm/git/docs/tutorial.html Git Tutorial]
* [http://git.or.cz/course/svn.html Switching from SVN to git using cogito]
* [http://wiki.sourcemage.org/Git_Guide Very good Git guide]

[[Category:Building]]

Documentation:Modules/marq

2009-10-17T00:51:37Z

Hillbilly1980: &*

{{Module|name=marq|type=Video subfilter|description=Overlays text on the video}}

The marq subfilter can be used to display text on a video.

== Options ==

{{Option
|name=marq-marquee
|value=string
|default=VLC
|description=Marquee text to display. Since VLC version 0.9.0 you can use [[Documentation:Play_HowTo/Format_String|format strings]] to display meta data and time information}}

{{Option
|name=marq-x
|value=integer
|default=0 (0.8.6d and prior: -1)
|description=X offset from upper left corner. (0.8.6d and prior: This is only if both marq-x and marq-y are positive)
}}

{{Option
|name=marq-y
|value=integer
|default=0
|description=Y offset from upper left corner. (0.8.6d and prior: This is only if both marq-x and marq-y are positive)
}}

{{Option
|name=marq-position
|value=integer
|default=5
|description=Marquee position: 0=center, 1=left, 2=right, 4=top, 8=bottom, you can also use combinations of these values, eg 6 = top-right. (0.8.6d and prior: This is only used if marq-x or marq-y are negative)
}}

{{Option
|name=marq-opacity
|value=integer
|default=255
|description=Marquee opacity. 0 is transparent, 255 is fully opaque.
}}

{{Option
|name=marq-color
|value=integer
|default=16777215 (0xFFFFFF, white)
|description=Marquee color. Use the decimal value of the HTML color code.
}}

{{Option
|name=marq-size
|value=integer
|default=-1
|description=Font size in pixels. -1 uses the default font size
}}

{{Option
|name=marq-timeout
|value=integer
|default=0
|description=Number of millitseconds the marquee must remain displayed. 0 means forever.
}}

== Avalabile Format Variables ==

* Time related:
**%Y = year
**%m = month
**%d = day
**%H = hour
**%M = minute
**%S = second

*Meta data related:
**$a = artist
**$b = album
**$c = copyright
**$d = description
**$e = encoded by
**$g = genre
**$l = language
**$n = track num
**$p = now playing
**$r = rating
**$s = subtitles language
**$t = title
**$u = url
**$A = date
**$B = audio bitrate (in kb/s)
**$C = chapter
**$D = duration
**$F = full name with path
**$I = title
**$L = time left
**$N = name
**$O = audio language
**$P = position (in %)
**$R = rate
**$S = audio sample rate (in kHz)
**$T = time
**$U = publisher
**$V = volume
**$_ = new line

== Examples ==

Example command line use '''(VLC 0.9.0 and above)''':
% '''vlc --sub-filter "marq{marquee=\$t (\$P%%),color=16776960}:marq{marquee=%H:%M:%S,position=6}" somevideo.avi'''
% '''vlc --sub-filter 'marq{marquee=$t ($P%%),color=16776960}:marq{marquee=%H:%M:%S,position=6}' somevideo.avi'''
:This command line will show the stream's title ($t) and current position ($P) in the upper left corner and the current time in the upper right corner. Note that we have to escape $ characters when running this from command line in UNIX shells (this is why we use \$ instead of $). The second line uses single quotes to delimit the string so we don't need to escape the $ character.
:On windows the command line would be:
C:\Program Files\VideoLAN\VLC\>'''vlc.exe --sub-filter=marq{marquee=$t ($P%%),color=16776960}:marq{marquee=%H:%m%s,position=6} somevideo.avi'''

Example command line '''(All versions including VLC 8.6d and prior)''':
% '''vlc --sub-filter=marq --marq-marquee="Obvious Watermark" --marq-position=0 --marq-size=50 --marq-opacity=25 --marq-color=32768 somevideo.avi'''
:This command will show centered transparent green text. Text sized too large to fit the video window will not appear, and may crash VLC.

== See also ==
* [[Documentation:Modules/rss]]

{{Stub}}

{{Documentation}}

Uncommon uses

2009-10-09T13:08:09Z

Hillbilly1980: /* Pipe data to VLC */

The modular nature of {{VLC}} allows you to do quite strange and unusual things with it. This page tries to list some funny and insane uses.

== Caca and Goom ==

If you have vlc compiled with both caca and goom you can listen to music with [[caca]] rendering the output of [[goom]]. That means you can show the visualisations from an audio file as colour ASCII art! Try something like this:
vlc --audio-visual goom --vout caca somemusic.mp3

Likewise, if you would like to view a video file as colour ASCII art, try the following:
vlc --vout caca somevideo.avi

== Pipe data to VLC ==

You can pipe input from standard input to VLC, rather than open a file or stream. VLC accepts data this way if you use a dash as a filename, ie:
vlc -
You can access a named pipe using fd://, ie:
vlc fd://nameofpipe
Syntax in VLM conf file:
setup yourinput input fd://nameofpipe

Piping passes the output of one program into the input of another. An example of this is using [[wikipedia:Cat (Unix)|cat]], which is part of GNU coreutils (ie, on *nix systems). Cat displays the contents of a file to standard output (normally to the screen as text). In this case, we'll use the pipe character to redirect this into vlc's standard input, whch will then be played. To wit,
cat file.mpg | vlc -

All very sane (though pointless) so far: if you're looking for madness, read on. You can get input from anywhere. A good place to get input is [[ffmpeg]]. Say you have a [[wikipedia:.flv|.flv]] file (which VLC now supports from version 0.8.4a onwards) and you want to play it in vlc. You could use ffmpeg to transcode it on the fly and pipe the output to vlc. The following command will do this:
ffmpeg -i 0.flv -f asf - | vlc -
A longer version with all the options ffmpeg likes to have is:
ffmpeg -i 0.flv -vcodec mpeg4 -ac 1 -ab 64 -acodec mp2 -b 128 -f asf -s cif - | vlc -
The advantage of this is that you don't have to make a new file (possibly 100s of MB in size). But you'll probably need a good computer. Plus, you wont have much control when playing it. You can pipe into ffmpeg too, so I suppose you could pass things along ffmpeg forever, transcoding it a million different ways, and ending up in vlc (please don't try that, your computer really wouldn't like it).

== Encoding Lots of Files ==

This command shows how to encode a whole directory of files in Linux, without your input. When complete, it'll show a message to say it is complete. It's a single command split over several lines (with \)

for A in *.avi; do \
echo ************************* $A ********************* ;\
vlc --sout-all "$A" :sout="#transcode{...}:\
std{access=file,mux=avi,url=~/$A.avi}" \
vlc://quit -I dummy ;\
done ;\
Xdialog --title 'Complete' --msgbox 'All done' 0 0;

Make sure you really understand this command before using it. It's also a good idea to make sure you've got the right options in the transcode bit, and that it'll transcode the right files. The output is sent to your home folder in this example.

[[Category:How_To]]

MacOS

2009-07-14T07:12:46Z

Hillbilly1980: /* Keyboard Shortcuts */

<div style="width:820px;border: 1px solid #ffc9c9>
{{vlc_MacOS_toc}}
<div style="padding: .4em .9em .9em">

==Graphical Interface==
Many people who want to use [[VLC media player]] on Mac OS X will be intending to use the standard graphical interface that is provided by vlc. The standard interface consists of the eight menus in the menu bar and the 'VLC - Controller' window that opens up by default. This section outlines what vlc can do for you (at V0.8.6a current active is V{{VLC:latest version}}) and will be completed as I check the use of menu options.

The eight menu bar options are listed below along with the main interesting capabilities under each menu item:

* [[vlc_MacOS_VLC|VLC]] which allows you to check for an updated application, to access the preferences and to add an interface.
* [[vlc_MacOS_File|File]] which allows you to open a media file or an associated file such as subtitles. It also has a wizard to allow the streaming of video or the capturing of a streamed video to a file.
* [[vlc_MacOS_Edit|Edit]] which does nothing vlc specific.
* [[vlc_MacOS_Playback|Playback]] allows you do do all the things you might expect from a videoplayer, some of these features are duplicated graphically in the 'Controller' window.
* [[vlc_MacOS_Audio|Audio]] allows you to control the audio level as well as the output device and the audio track to use from the input.
* [[vlc_MacOS_Video|Video]] allows you to control the video display on your screen as well as which device to display on and which video source to show in that display.
* [[vlc_MacOS_Window|Window]] allows you to display seven helper windows that will display information about vlcs activity and control more detail of that activity.
* [[vlc_MacOS_Help|Help]] gives access to the help that came with the installation, the help info on the VideoLAN site and access to interaction mechanisms with the vlc developers.

In general, for many users, they find that they can get what they want from vlc 'straight out of the box' and have very little need of the menu options until they have been using vlc for a while and now want to try something 'more fancy'.

==Keyboard Shortcuts==
You can find most of the keyboard shortcuts by taking a look at the menus. Additional hotkeys are defined in the section "Hotkeys" of your VLC preferences.

Some handy key combo's are:

* You can use the spacebar to start/pause the video.
* When playing video, holding down the Apple key and pressing the F key enters and exits fullscreen. When in fullscreen you can also use the escape key to exit the fullscreen state.
* When playing video, holding the Apple and Shift keys and pressing the left/right arrow keys, jumps the video backward/forward about a minute.
* When playing video, holding the Apple and Ctrl keys and pressing the left/right arrow keys, jumps the video backward/forward about ten seconds.
* When you are watching a DVD and the video window is the front-most window you can use the arrow keys and the enter key to navigate the DVD menus.

* F - Decrease Audio Delay in microseconds
* G - Increase Audio Delay in microseconds
* H - Decrease Subtitle Delay
* J - Increase Subtitle Delay

==Latest developments==

===Streaming Wizard===
A streaming wizard is available since the VLC media player 0.8.4 release. This is available under the "File" menu.

===Command line===
You can run VLC on Mac OS X using a terminal application (for example Terminal.app in /Applications/Utilities) with the following command: ./VLC.app/Contents/MacOS/VLC [your options, "--intf=rc" for example].

This option can also be activated from the "VLC" menu.

=== No Dock ===
Note that you can replace the "VLC" at the end of the path with "clivlc" to suppress the launch of any Mac-like interface.
VLC won't even appear in the Dock then.

When [[transcoding]], clivlc should be used if running VLC from the command line crashes with a Bus error.

==Need Help?==
View the [[FAQ on MacOSX only issues]] or the [[Common Problems]] pages.
[[Category:Operating systems]]

</div>
</div>

VLC HowTo/Make a mosaic

2008-12-04T10:13:04Z

Hillbilly1980:

{{howto| set up a mosaic of a few videos or stream like a TV portal}}

==VLC mosaic howto==

This is a small example about how to use {{VLC}} to create a mosaic. What we basically want is a video mosaic mixing 3 video channels (channels 1, 2 and 3) on a background image (background.png) and streaming the resulting video on the network. Note that we will also be streaming the 3 sound tracks from channels 1, 2 and 3 in the same mpeg-ts stream.

Starting with VLC 0.8.5-test2, the http interface features a "Mosaic wizard". You might want to use it if you have no knowledge of VLC command line usage.

http://people.via.ecp.fr/~dionoea/videolan/mosaic1.png

Other neat examples :

[http://people.via.ecp.fr/~dionoea/videolan/mosaic2.jpg 12 video mosaic]

[http://people.via.ecp.fr/~dionoea/videolan/mos1.png 20 video mosaic]

[http://people.via.ecp.fr/~dionoea/videolan/mos2.png 20 video mosaic]

===Step 0===

Read the VLC streaming howto (chapters 3 and 5 concerning command line and vlm usage in VLC) : http://videolan.org/doc/

===Step 1===

Get VLC 0.8.4-test1 or newer and install it on your computer.

===Step 2===

You now have to get a background image. Many image formats are supported (JPEG, PNG ...).

You can also test it with VLC to see if it displays locally :
<pre>
./vlc --fake-file background.png --fake-aspect-ratio "4:3" fake:
</pre>
In 0.9.6< on windows and linux the arrangement and addition of the // must be included.
<pre>
vlc.exe fake:// --fake-file background.png --fake-aspect-ratio "4:3"
</pre>

===Step 3===

You now need to configure VLC to get the 3 source streams and blend them on the background image.

The vlm configuration file looks like :

<pre>
new channel1 broadcast enabled
setup channel1 input udp://@239.255.2.60:1234
setup channel1 output #duplicate{dst=mosaic-bridge{id=1,height=144,width=180},select=video,dst=bridge-out{id=1},select=audio}

new channel2 broadcast enabled
setup channel2 input udp://@239.255.10.200:1234
setup channel2 output #duplicate{dst=mosaic-bridge{id=2,height=144,width=180},select=video,dst=bridge-out{id=2},select=audio}

new channel3 broadcast enabled
setup channel3 input udp://@239.255.6.9:1234
setup channel3 output #duplicate{dst=mosaic-bridge{id=3,height=144,width=180},select=video,dst=bridge-out{id=3},select=audio}

new background broadcast enabled
setup background input fake:
setup background output #transcode{sfilter=mosaic,vcodec=mp2v,vb=10000,scale=1}:bridge-in{delay=400,id-offset=100}:standard{access=udp,mux=ts,url=239.255.12.42,sap,name="mosaic"}

control background play
control channel1 play
control channel2 play
control channel3 play
</pre>

Note that the source streams are network streams, which is likely to be the case if you're considering doing a mosaic.

===Step 4===

And now, the right command to launch vlc :

<pre>
./vlc --color -I telnet --vlm-conf ../mosaic.vlm.conf --ttl 12 \
--fake-file background.png --fake-aspect-ratio "4:3" \
--mosaic-width 360 --mosaic-height 288 --udp-caching 800 \
--mosaic-keep-picture --mosaic-rows 2 --mosaic-cols 2 \
--mosaic-position 1 --mosaic-order 1,2,3
</pre>

== Other examples ==

=== Dual webcam with alphamask ===

http://people.videolan.org/~dionoea/mosaic/dual-webcam.png

<pre>new isight broadcast
setup isight input v4l2:///dev/video0:width=320:height=240:audio-method=0
setup isight option v4l2-brightness=90
setup isight output #mosaic-bridge{chroma=YUVA,vfilter=alphamask{mask=../mask.png},width=320,height=240}
setup isight enabled

new logitech broadcast
setup logitech input v4l2:///dev/video1:width=640:height=480:audio-method=0
setup logitech output #transcode{vcodec=mp4v,vb=1024,sfilter="mosaic:marq{marquee='VLC dual webcam setup',position=8}"}:bridge-in:display
setup logitech enabled

new audio broadcast enabled
setup audio input v4l:///dev/dsp1
setup audio output #transcode{acodec=mp4a,ab=128}:bridge-out

control isight play
#control audio play
control logitech play</pre>

You can then launch it with:
vlc --vlm-conf ../dual-webcam.conf --no-media-library --plugin-path modules -v --no-video-title --mosaic-keep-picture

The mask.png file is used to set transparency values on the isight camera (uses the png alpha plane). An example file to use is available at http://people.videolan.org/~dionoea/mosaic/.

==See Also==
* [http://people.via.ecp.fr/~dionoea/videolan/mosaic-diagram.png Small Diagram That Might Help]
* [http://people.videolan.org/~dionoea/mosaic/ VLC Mosaic related resources]
* [[MosaicExampleSetup | Example set-up of conference web-streaming with two grabber cards]]

==Appendix==
* [[Documentation:Modules/mosaic]]
* [[Documentation:Modules/mosaic-bridge]]
* [[Documentation:Modules/bridge-out]]
* [[Documentation:Modules/bridge-in]]
===Mosaic specific video filters===
* [[Documentation:Modules/alphamask]]
* [[Documentation:Modules/bluescreen]]