A music player for Macs that’s been around for a while now, Clementine offers a host of helpful features that music lovers can appreciate. The ability to search their local music library, create smart and dynamic playlists, tabbed playlists, import and export M3U, XSPF, PLS and ASX, transcode music formats and tons more. Download GStreamer. If you're on Linux or a BSD variant, you can install GStreamer using your package manager. For other platforms, specifically Windows, macOS, Android, and iOS, we provide binary releases in the form of official installers or tarballs maintained by the GStreamer project.
If you're on Linux or a BSD variant, you can install GStreamer using yourpackage manager.
For other platforms, specifically Windows, macOS,Android, and iOS, we provide binary releases inthe form of official installers or tarballs maintained by the GStreamerproject.
Windows
Binary releases in the form of MSI installers are available. The installers aresplit into runtime and development packages. For development, you will want toinstall both packages.
- MSVC 64-bit (VS 2019, Release CRT)
- MSVC 32-bit (VS 2019, Release CRT)
- MinGW 64-bit
- MinGW 32-bit
For each of the above listed targets, a zip file with .msm
modulesis available for integration into your own WiX-based app installer.
If you are not sure which to pick between MSVC and MinGW, just pick MSVC.However, do see the toolchain compatibility notesbelow which may affect you based on what toolchain your app will be built with.
NOTE: The library names in MSVC are different from MinGW; specifically the DLLsare of the form foo.dll
instead of libfoo.dll
.
NOTE: GstSharp .NET bindingsrequire the MSVC binaries starting with 1.18.
NOTE: Some of the plugins shipped with the MSVC binaries link to non-gstreamerlibraries built with MinGW because they are built with Autotools. See belowfor what this means for your application.
Older 1.x binary releases are also available.
Universal Windows Platform
Binary releases built to target the Universal Windows Platform (UWP). Used forshipping apps on the Windows Store, such as for an XBox, HoloLens 2, etc.
- UWP Universal (ARM64, X86, X86_64) (VS 2019, Release CRT)
- UWP Universal (ARM64, X86, X86_64) (VS 2019, Debug CRT)
UWP apps cannot use plugins that use dependencies built with MinGW because offorbidden APIs. Hence, these plugins are omitted from the binaries.
Toolchain Compatibility Notes
On Windows, you can use a number of different toolchains and versions thereof,and it is not always obvious how these can be mixed and matched with thebinaries provided above by GStreamer.
The first step is ensuring that you're using the correct architecture. Youshould not try to mix 32-bit code built with any toolchain with 64-bit codebuilt with any toolchain.
Next, understand that since GStreamer is written mostly in C, all APIs exportedby GStreamer libraries and plugins use C ABIs. Even plugins written in otherlanguages such as Rust, C++, C#, Python, etc, are loaded using the C ABI.
This means you can consume the GStreamer binaries from any toolchain that usesthe same C ABI. Using the same CRT (C Runtime)is better, but it's not always a requirement. Here's the matrix outlining theCRT used for each GStreamer version:
GStreamer version | MinGW | MSVC |
---|---|---|
1.14.x | msvcrt.dll | N/A |
1.16.x | msvcrt.dll | ucrtbase.dll |
1.18.x | ucrtbase.dll | ucrtbase.dll |
This is the toolchain compatibility matrix with the stable releases:
App Toolchain | 1.16 MinGW | 1.16 MSVC | 1.18 MinGW | 1.18 MSVC |
---|---|---|---|---|
Visual Studio 2015 and newer (ucrtbase.dll) | PARTIAL | FULL | FULL | FULL |
Visual Studio 2013 and older (msvcrt.dll) | PARTIAL | PARTIAL | PARTIAL | PARTIAL |
MinGW (msvcrt.dll) | FULL | PARTIAL | PARTIAL | PARTIAL |
MinGW-w64 (msvcrt.dll) | FULL | PARTIAL | PARTIAL | PARTIAL |
MSYS2 MinGW-w64 (msvcrt.dll) | FULL | PARTIAL | PARTIAL | PARTIAL |
Cygwin | NONE | NONE | NONE | NONE |
FULL means full C compatibility, including debugging symbols.
PARTIAL means mixing the two should be fine as long as you are careful whilepassing memory across CRT boundaries.
NONE means fully unsupported, and will lead to crashes.
macOS
Binary releases in the form of .pkg
framework installers are available. Theinstallers are split into runtime and development packages. For development,you will want to install both packages.
- macOS 64-bit (target: macOS 10.11)
- macOS 64-bit (target: macOS 10.10)
GStreamer is also available on Homebrew, and you should beable to use that. However, please note that some plugins are not shipped byHomebrew, and you should avoid mixing Homebrew and the official installers onthe same system.
Older 1.x binary releases are also available.
Android
Binary releases are available with each in the form of a single 'universal'tarball with armv7
, arm64
, x86
, and x86_64
architectures in subfolders.
- Android Universal 1.18.2 tarball
- Android Universal 1.16.3 tarball
The Android NDKs used by the stable releases are:
GStreamer version | NDK Version |
---|---|
1.16.x | r18b |
1.18.x | r21 |
The Android APIs targeted by the GStreamer 1.16.x and 1.18.x stable release(s) are:
Architecture | API Targeted |
---|---|
armv7 | v16 (Jelly Bean) |
x86 | v16 (Jelly Bean) |
arm64 | v21 (Lollipop) |
x86_64 | v21 (Lollipop) |
Older 1.x binary releases are also available.
iOS
Binary releases that integrate into XCode are available in the form of a single'universal' package with fat library frameworks. Bitcode support is built-inand the target SDK version for 1.16.x was iOS 9.0, and for 1.18.x is 11.0.
- iOS Universal 1.18.2 framework (ARM64, X86_64)
- iOS Universal 1.16.3 framework (ARM64, X86_64, X86)
Older 1.x binary releases are also available.
Linux and BSDs
All Linux distributions and many BSD variants provide packages of GStreamer.You will find these in your distribution's package repository.
Note that some distributions split the GStreamer plugins up further than theupstream sources. Additionally, some distributions do not include some pluginsfrom the gst-plugins-bad package, or omit the gst-plugins-ugly and gst-libavpackages entirely in their main repository for legal reasons.
Sources
For building the aforementioned binary releases, you need to use the Cerberobuild aggregatormaintained by the GStreamer project which supports Linux, macOS, and Windows.
For downloading each GStreamer module individually, check our modulespage, or go straight to our source download directory.
Generally, you should not need to build from source yourself unless you needfeatures that are only available in a newer version of GStreamer than isprovided by your distribution or in the last stable release.
For doing GStreamer development, we recommend using the gst-buildproject whichwill aggregate all the GStreamer modules using Meson's subprojectfeature.
Get the latest stable version of Clementine for your operating system.
1.3.1Windows
32-bit
Downloads for other operating systems
1.3.1Debian Jessie
64-bit
1.3.1Debian Jessie
32-bit
1.3.1Raspberry Pi
32-bit
1.3.1Fedora 21
32-bit
1.3.1Fedora 21
64-bit
1.3.1Fedora 22
32-bit
1.3.1Fedora 22
64-bit
1.3.1Fedora 23
32-bit
1.3.1Fedora 23
64-bit
1.3.1Mac
64-bit
1.3.1Source Code
Clementine Para Mac Os
1.3.1Ubuntu Precise
64-bit
1.3.1Ubuntu Precise
32-bit
Clementine For Mac Review
1.3.1Ubuntu Trusty
64-bit
1.3.1Ubuntu Trusty
32-bit
1.3.1Clementine Para Macbook
Ubuntu Vivid
64-bit
1.3.1Ubuntu Vivid
32-bit
1.3.1Ubuntu Wily
64-bit
1.3.1Ubuntu Wily
32-bit
1.3.1Ubuntu Xenial
64-bit
1.3.1Ubuntu Xenial
32-bit
1.3.1Windows
32-bit
Ubuntu PPA
You can download the latest version of Clementine on Ubuntu from the official PPA:
Dependencies for Ubuntu Precise (12.04)
New versions of Clementine require GStreamer 1.0 which wasn't included in Ubuntu 12.04. If you get errors installing Clementine you should add the GStreamer PPA as well:
Clementine Remote for Android
Unofficial packages
If you don't see your distribution listed above then someone else might have created an unofficial package for you.
Compiling from source
Compiling Clementine from source is easy on Linux.Download the source code package from the list above, and in a terminal window:
Bleeding edge packages
Development on Clementine happens inthe git repository.Check out the code by running:
If you'd prefer not to compile the development version yourself then try one of the hourly packages:
There's also an Ubuntu PPA for these development builds: