Media Framework Technical Reference

Choose your OS:

This page outlines the currently supported file extensions, URLs, and capture devices, as well as pointing out some troubleshooting tips on how to enable Media Framework with different platforms. There are some known platform-specific issues and limitations which we are currently investigating and trying to resolve, each of which has been identified in the Troubleshooting and Known Issues sections.

If you are upgrading Media Framework content from a pre-4.18 project, see the Upgrading Media Framework Content to 4.18 page to successfully update your project.

Supported Files, URLs & Capture Devices

The table below indicates the supported file extensions based on each media player platform.

Click the image below to download a .xlsx version of the Supported Files & URLs spreadsheets.

MediaFrameworkExtentions.png

The list of supported file formats above is ongoing and support for additional file extensions will come online in future engine updates.

For the best compatibility and performance, it is recommended to use H.264 encoded MP4 (.mp4) container files.

The table below shows the supported URLs based on media player platform.

URLSheet.png

Capture Devices

Media Framework supports audio/video capture hardware on Windows (WmfMedia) and Android (AndroidCamera) as of 4.18 (consoles however, are not yet supported).

Please see the Playing Live Video CapturesNEW! page for an example guide on working with capture devices.

WMF Media Configuration Settings

Windows Media Foundation (WMF) handles standard audio/video playback and recording on the Windows Platform, however, WMF is also extensible. By default, WMF supports a number of different formats, encoding, and file containers, but it can also be extended with the use of optional codec packs that can be downloaded and installed from the Internet. What this means, however, is that certain users may not have a particular codec needed to decode and playback a media file.

In the past, Unreal Engine only supported default codecs that are supplied with WMF to ensure that everyone can handle and process media the same way. There may be times when you want to use a different method of encoding your media or your own proprietary media encoder that you want to ship your game with (for example, you ship your game with an installer that provides the needed encoder).

You can now enable and allow non-standard codecs for WMF Media from the Plugins section of Project Settings.

ProjectSettings.png

By default, the player plugin will attempt to detect audio and video codecs that are not supported by the operating system (OS), requiring the user to install additional codec packs. If the player plugin detects an unsupported format when accessing the media, a warning message is provided in the Output Log.

UnsupportedLog.png

Additionally, you can see media asset information inside a Media Player asset in the Info panel.

MediaInfo.png

When enabling Allow non-supported codecs, the Plugin player will skip the check and allow the usage of non-standard codecs.

Troubleshooting

As of engine 4.18 most player Plugins have had extensive logging added and will provide detailed logging of potential problems.

To enable logging, add the following to your project's Engine.ini file:

[Core.Log]
LogMedia=VeryVerbose
LogMediaAssets=VeryVerbose
LogAndroidMedia=VeryVerbose
LogAvfMedia=VeryVerbose
LogMfMedia=VeryVerbose
LogPS4Media=VeryVerbose
LogWmfMedia=VeryVerbose

If a media source fails to open or play, check the Output Log under the Developer Tools for additional details.

You can also check information about a Media Source inside the Media Player asset and Info tab.

InfoWindow.png

This will show what options are available for the media source, as well as the different Audio and Video streams and information about each stream.

Windows

The Windows Media Foundation (WMF) based player Plugin WmfMedia has a number of limitations for MP4 containers.

See Microsoft's MPEG-4 File Source page for more information.

Known Issues & Limitations

Media Framework is still in development and there are some known issues and limitations which are outlined below.

  • Android

    • Audio currently plays via the OS and cannot be piped through UE4's Sound System.

  • Editor

    • The Playlist UI inside the Media Player always has a playlist created internally.

    • Playlists can be saved from the Media Player, however, there is no way currently to edit the playlist in the Media Player.

    • Workaround - Save a Playlist from the Media Player then open and edit the Media Playlist asset.

  • Sequencer

    • Media Playback will not render out properly when recording cinematics from Sequencer.

      • We have this scheduled to release in the near future as we know this is important.

    • The ImgMedia Plugin will be synced with Sequencer.

  • Windows

    • QuickTime movie (.mov) support on Windows 7 and later is currently unreliable.

      • Workaround: This format is currently not recommended for use.