All posts by romain bouqueau

ISOBMFF, the technology at the heart of GPAC, awarded a Technology Engineering Emmy®

News,

Today, the National Academy of Television Arts and Sciences announced that it decided to honor the File Format subgroup under MPEG for the ISOBMFF technology.

We, the GPAC contributors and community, are proud to have been part of the development of this awarded technology from its beginning. GPAC started more than 20 years ago to demonstrate the features of the MPEG-4 Standard which includes ISOBMFF. Soon, GPAC’s MP4Box became the MP4 swiss-army knife used worldwide by MP4 aficionados, by multimedia researchers and by media companies in production.

In GPAC, we always strive to be amongst the first tools to implement the new ISOBMFF features. Movie fragments (required for adaptive streaming), Common Encryption, the Image file format (IFFs such as HEIF or AVIF), … the support of the GPAC open-source tooling and community proved crucial to create correct and effective standards.

In 20 years we made hundreds of contributions to the awarded MPEG File format Subgroup (and still counting!). We hope to continue to offer that level of innovation and commitment to you for the next 20 years. In 2020 we released GPAC 1.0 (filters) to make sure we’re technically on track for the future.

We would like to congratulate all contributors to this technology and thank our user base for feature requests and bug reports which helped us contribute and improve the ISOBMFF technology and our support of it.

GPAC 1.0.0 public release

Release

After almost 20 years of development, GPAC reaches yet another milestone. As the major number increment suggests, this GPAC version offers significant changes over previous releases.

Among the video community GPAC was known for its wide capabilities. Unfortunately these capabilities came with maintenance and usability challenges. This new version addresses these challenges by leveraging a new modular system called “filters”.

Filters make GPAC easier to use thanks to a unified API. Filters make GPAC easier to test, document, and maintain. Filters make GPAC more efficient thanks to a highly configurable resource manager. Filters make GPAC 1.0 the best GPAC ever. The multimedia ecosystem is very innovative and so is GPAC, now ready for the next 20 years!

This release comes with many new features thanks to the rearchitecture.

A special focus was made to make the transition as transparent as possible for our users. The APIs and the tool (MP4Box, MP4Client, …) are fully compatible to make the transition as smooth as possible.

For the last year we have maintained both the legacy and the new versions with both new features and bug fixes. From now on, the legacy version is marked LTS and will only receive bug fixes.

As usual pre-built installers are available for simplicity.

We strongly encourage users to update their codebase.

Of course there is still much to be done. Please help us and get in contact using our issue tracker.

We’d like to thank our community for the warm welcome of all these changes. You have been so patient and supportive during this transition period. Thank you.

Official AV1 and VP9 support in GPAC

Features,

Dear reader,

GPAC has added support for new codecs recently:

  • AV1 support is available in nightly builds since July 10th, 2018. This include file creation with MP4Box (including MPEG DASH generation) and file playback with MP4Client. Support for AV1 encryption was added on September 20th, 2018.
  • VP9 support was completed on October 14th, 2018.

This article gives you some useful command lines to use AV1 streams, but the same can be applied for VP9 streams.

Command-line for importing AV1 streams into MP4 files

To store an AV1 bitstream into an ISOBMFF/MP4 file , use the following command line. If the input file is called *.av1, its content can be OBUs (as specified in Section 5 of the AV1 specification), IVF or Annex B bitstreams. WebM streams are not supported. You can also call OBU-based bistream *.obu and IVF files *.ivf:

MP4Box -add file.av1 file_av1.mp4

If your file extension is not recognized by MP4Box, you can indicate the bitstream format with “:fmt=obu” or :fmt=AnnexB or fmt=IVF (case insensitive) as follows:

MP4Box -add file.xxx:fmt=obu file_av1.mp4

AV1 bitstreams may not contain frame rate information, you can use the following to indicate it:

MP4Box -add file.av1:fps=1000 file_av1.mp4

Command-line for AV1 adaptive streaming preparation

You can use the usual MP4Box command line parameters to segment your AV1 MP4 file and prepare it for adaptive streaming. The following command line will generate an MPEG-DASH onDemand manifest based on an AV1 representation (with its ‘codecs’ parameter) and it will create a segmented MP4 file with segments starting at AV1 KEY FRAMEs and targeting 1 second duration.

MP4Box -dash 1000 -profile onDemand file_av1.mp4

Command-line for AV1 encryption/decryption

Encryption of AV1 streams in MP4 files follows the general principles given by MPEG’s Common Encryption specification.  To use MP4Box for encryption or decryption, use the following command lines where the file ‘info.xml’ is an XML file that provides encryption parameters, as described in more details here. Example of such XML files can be found in our test base.

Encryption:

MP4Box -crypt info.xml -out file_av1_encrypted.mp4 file_av1.mp4

Decryption:

MP4Box -decrypt info.xml -out file_av1_decrypted.mp4 file_av1_encrypted.mp4

Acknowledgements and conclusion

The work on AV1 and VP9 was largely sponsored by Alliance for Open Media and Netflix. Kudos to them 🙂

As usual, if you find any bug or miss documentation, let us know.