Current version: 1.1-DEV
Latest Release: 1.0.1
GPAC is an open-source multimedia framework focused on modularity and standards compliance. GPAC provides tools to process, inspect, package, stream, playback and interact with media content. Such content can be any combination of audio, video, subtitles, metadata, scalable graphics, encrypted media, 2D/3D graphics and ECMAScript. GPAC is best-known for its wide MP4 capabilities and is popular among video enthusiasts, academic researchers, standardization bodies, and professional broadcasters.
For more information, visit GPAC website
GPAC is distributed under the LGPL v2.1 or later, and is also available, for most of it, under a commercial license.
Please ! cite ! our work in your research:
GPAC can process, analyse, package, stream, encode, decode and playback a wide variety of contents. Selected feature list:
Features are encapsulated in processing modules called filters:
gpac -h filters
or check filters' wiki.MP4Box is a multi-purpose MP4 file manipulation for the prompt, featuring media importing and extracting, file inspection, DASH segmentation, RTP hinting, ... See MP4Box -h
, man MP4Box
or our wiki.
As of version 0.9.0, GPAC includes a filter engine in charge of stream management and used by most applications in GPAC - read this post for more discussion on how this impacts MP4Box and MP4Client.
The gpac application is a direct interface to the filter engine of GPAC, allowing any combinaison of filters not enabled by other applications. See gpac -h
, man gpac
, man gpac-filters
or our wiki for more details.
MP4Client is a media player built upon libgpac, featuring a rich media interactive composition engine with MPEG-4 BIFS, SVG, VRML/X3D support.
For GPAC configuration instruction, check MP4Client -h
, man MP4Client
or our wiki.
Stable and nightly builds installers for Windows, Linux, OSX, Android, iOS are available on gpac.io.
If you want to compile GPAC yourself, please follow the instructions in the build section of our wiki.
The general GPAC framework documentation is available on wiki.gpac.io, including HowTos.
GPAC tools are mostly wrappers around an underlying library called libgpac which can easily be embedded in your projects. The libgpac developer documentation is available at doxygen.gpac.io, including documentation of JS APIs.
GPAC has a test suite exercising most features of the framework. The test suite is in a separate repository https://github.com/gpac/testsuite/, but is available as a submodule of the GPAC main repository. To initialize the testsuite submodule, do git submodule update --init
.
For more details on the test suite, read this page and check the testsuite readme.
Per-commit build and tests results are available.
Please use github for feature requests and bug reports. When filing a request there, please tag it as feature-request.
A complex project like GPAC wouldn’t exist and persist without the support of its community. Please contribute: a nice message, supporting us in our communication, reporting issues when you see them… any gesture, even the smallest ones, counts.
If you want to contribute to GPAC, you can find ideas at GSoC page or look for a good first issue. In any doubt please feel free to contact us.
GPAC is brought to you by an experienced team of developers with a wide track-record on media processing.
The project is mainly developed at Telecom Paris, in the MultiMedia group, with the help of many great contributors
GPAC has a peculiar story: started as a startup in NYC, GPAC gained traction from research and a nascent multimedia community as it was open-sourced in 2003. Since then we have never stopped transforming GPAC into a useful and up-to-date project, with many industrial R&D collaborations and a community of tens of thousands of users. This makes GPAC one of the few open-source multimedia projects that gathers so much diversity.
Users are encouraged to use the latest tag or the master branch.
The previous v0.8.X release (the last one using the legacy architecture) is LTS until 30/06/2021. Important bug fixes will be backported but new features won’t. API compatibility between both versions should make the migration easy. If not please file a bug.
Targets: