-
Notifications
You must be signed in to change notification settings - Fork 123
Enable MultiMedia in Crosswalk
The Crosswalk binary includes free codecs (ffmpegsumo.dll for Windows and libffmpegsumo.so for Linux). This enables HTML5 multimedia features (<video> and <audio> elements) to work by default.
The codecs included are:
- Vorbis audio codec
- Theora video codec
- VP8 video codec
- PCM
While free codecs are included with Crosswalk binary downloads, the instructions below explain how to download compiled versions of the free codecs manually, if desired.
We also provide instructions for developers who want to build the free codecs manually.
Finally, a developer can enable proprietary codecs in a Crosswalk build. When an xwalk binary with these codecs is started, the end user must accept the EULAs for those third-party codecs to use them. Instructions on how to create such a build are given below.
Follow the steps below to get the codecs for a Crosswalk binary release:
- Download the appropriate upstream Chromium build. For example, for the current Crosswalk release, fetch chrome-win32.zip for Windows or chrome-linux.zip for Linux.
- Unzip and copy the ffmpegsumo.dll or libffmpegsumo.so file to the directory which contains the xwalk executable.
- Relaunch xwalk and multimedia will work.
Developers can also build the codecs for themselves. Please refer to Crosswalk Build Instruction for instructions. After building, the ffmpegsumo.dll or libffmpegsumo.so with open source codecs will be found in the build output directory.
Examples of proprietary codecs include:
- MP3 audio codec
- AAC audio codec
- H.264 video codec
To build Crosswalk with these codecs, a developer must run the build with the "must accept a EULA" switch turned on:
$ xwalk/gyp_xwalk -Dmediacodecs_EULA=1
Then build Crosswalk. The ffmpegsumo.dll or libffmpegsumo.so in the build output directory will contain the proprietary codecs.
Refer to Crosswalk Build Instruction for more details.
Also please note you might need to take legal advice to determine and resolve potential licensing issues if you want to include these codecs in a build.
For more details, please refer to Chromium Audio/Video.