Mediaengine Overview
Mediaengine Overview
mediaEngine
Overview
All-in-one transcoding factory for video processing workflows
Video transcoding, remuxing, and conversion in a highly-optimized,
cost-effective, and easy-to-use solution
Fits a wide range of scenarios All codecs and muxers in one solution
www.nablet.com
mediaEngine Overview 2
Introduction
mediaEngine is a multi-format transcoding factory that you can use to encode almost any
video source to virtually any professional video format. IP-cameras, SDI capture devices, net-
work streams, RAW data – mediaEngine can process it all and encode it to MXF, MOV, HLS,
DASH and other formats using AVC, AVC Intra, XDCAM, XAVC, and other highly-optimized
video codecs.
mediaEngine is a fully-configurable tool where you can control any aspect of video and audio
encoding process.
Support – mediaEngine supports multiple input formats, a wide range of pixel formats, and
can convert almost any input video source to a required destination. If something is missing,
nablet team is happy to adjust the functionality to match your scenario.
Features
Inputs
mediaEngine supports live feeds as long as local files as inputs. You can use SDI and HDMI
inputs from capture devices, NDI streams, network streams from IP cameras or from remote
locations using SRT, RTMP, UDP protocols. You can use MXF, AVI, MKV, MOV files of various
configuration and codecs as sources. It is possible to use RAW input as well as image se-
quences (PNG, JPG, DXP).
3 mediaEngine Overview
mediaEngine supports any possible frame rates, resolutions, aspect ratios, color parameters
for all the input types.
Outputs
With mediaEngine, you can get the transcoding output in forms of local files in MXF, MOV,
MP4, MKV formats. For VOD and OTT scenarios, you can use mediaEngine to get HLS and
DASH streams. And for direct streaming to CDNs or media servers, you can configure stream-
ing over UDP, RTMP, or HTTP protocols.
The list includes a highly-effective AVC encoder with a lot of pre-configured presets (XAVC,
AVC-Intra, Long G AVC). For GPU-powered machines, it is possible to use AVC encoding with
NVIDIA NVENC and Intel Quick Sync technologies. With MPEG-2 encoder, you can generate
professional XDCAM files, or mux DVB-compatible transport streams. Recently, we have
added an official ProRes encoder to make the range of use cases for mediaEngine even wider.
The other video codecs list includes HEVC, JPEG, PNG, DV. The audio codecs list includes
AAC, PCM, and all the MPEG audio codecs (MP1, MP2, and MP3).
From the muxer perspective, mediaEngine includes a professional TS muxer, and the best in
the world MXF muxer that matches any professional requirements with a support of edit-
while-recording functionality. The other muxers include MP4, MKV, and MOV.
Optimization
mediaEngine is a highly-optimized software. It means that it uses available hardware in the
most efficient way. We have added optimizations for different CPU architecture types includ-
ing ARM, so on all machines and cloud instances you can have the fastest transcoding results
with the highest possible quality. Keeping the quality as high as possible for any input type
whether it is 8- or 10-bit is a constant goal along the mediaEngine development.
It is not only the internal codecs and muxers that are optimized. mediaEngine uses a multi-
threading internal architecture that makes parallel video processing of videos even more ef-
fective. You can have multiple outputs of the same video encoding configuration at the same
time, for example, running a network streaming over RTMP and capturing the content into an
MP4 file.
Processing
The input sources don’t always match the output requirements, so mediaEngine has an inte-
grated video processing operation to convert and modify the original video and audio param-
eters to meet your desired parameters.
You can crop unnecessary parts of video, change its resolution up and down from SD up to
UHD. You can configure the output frame rate and aspect ratio. You can change the field
order, or make interlaced video to become a progressive one. There is an option to put your
logotype or any static image on top of the recorded video.
mediaEngine Overview 4
From the audio side, you can change the audio channels and audio tracks configuration. me-
diaEngine doesn’t have any limitations on the number of audio channels, so you can, for ex-
ample, record 64 audio channels in a single output file. And you can mix audio and video tracks
from multiple sources together to have desired results. For example, you can embed audio
channels from an external WAV file into a new MXF file.
Some processing can be done without actual transcoding – for instance, if you need to nor-
malize MXF files to match a specific standard. You can do it with mediaEngine by using its
remuxing feature – so the video and audio parts are untouched, but the container level is re-
configured.
Other features
Along with mediaEngine you have a web-based project to monitor the encoding process re-
motely. Also, to make the integration smoother, you can use a built-in REST API. With medi-
aEngine, you can work in both plain-text or JSON-based formats – it supports preset config-
uration and statistics in both formats.
You can run multiple instances of mediaEngine at the same time to process many streams at
once, also you can handle multiple inputs and outputs at the same time within a single instance
of mediaEngine.
Customization
Due to its module architecture, it is easily for nablet team to adjust mediaEngine functionality
to meet your technical and business requirements. If something should be changed to make
mediaEngine the best fit for your solution just contact us.