Here you can download experimental versions of VLC that are daily generated from the VLC code that is currently in development.
Several issues that existed in previous versions of VLC might be fixed here, but since this version of VLC is not yet finished, you should expect other problems and issues.
WARNING: The nightly builds are UNSTABLE and may not work at all. There is absolutely NO SUPPORT for it from the VideoLAN Team.
Download nightly builds
You’ll find the last development version in trunk-xxx directories, while branch-xxx directories contains bugfixes for the last released version.
Select your operating system to download VLC binaries:
- windows“>Windows (32 bits)
- windows“>Windows (64 bits)
- Mac OS X Intel
- debian“>Ubuntu
- android“>Android (ARMv6 with FPU)
- android“>Android (ARMv6 without FPU)
- android“>Android (ARMv7-A)
- android“>Android (x86)
- The packages for the following operating systems
are not automatically built every night: - openSUSE
- Gentoo
Source-code snapshots
Download here the tarballs (bz2) or use Git to get the latest source code.
Ubuntu PPA
The nightly builds for Ubuntu are available on Launchpad from the VideoLAN team’s master-daily PPA. Once you have activated the correct repository, you can simply update the VLC (vlc) package.
Those repositories contain a vlc-dbg package. We recommend you install it so you can produce useful backtraces if you need to report a bug.
VLC SVN Snapshots for openSUSE
For openSUSE 11.4, 12.3, 13.1, 13.2 and Tumbleweed we offer also RPMs from SVN snapshots. The packages are updated approximatively once per week.
In order to test it, follow the usual instructions to install VLC as described onhttp://www.videolan.org/vlc/download-suse.html, but replace the packagename vlcwith vlc-beta. You can only install one version, so either vlc OR vlc-beta. They conflict each other.
VLC Git Ebuild for Gentoo
Alexis Ballier maintains Ebuild for the master (vlc-9999.ebuild) Git branch in the Portage tree.
As it is a live ebuild it comes without any keyword so you’ll have to put a ‘**’ entry for it in package.keywords in order to be able to install it and, when appropriate, an entry in package.unmask .
