AWS Elemental: Encoding vs Transcoding Services

AWS Elemental provides 2 unique but complementary categories of services: Live and File Encoding (initial compression from raw inputs) and Transcoding (re-encoding existing media into new renditions). Each is designed for a different point in the workflow, with different latency and packaging requirements. Understanding the difference between them will help you create efficient pipelines for live and on-demand streaming.

Encoding Services (Initial Compression)

AWS Elemental MediaLive and Elemental Live appliances handle real-time encoding of raw or mezzanine inputs. These systems take SDI/HDMI/IP feeds, uncompressed files, or mezzanine formats such as ProRes and output compressed streams in H.264/AVC, H.265/HEVC, or VP9/AV1. Output containers include MPEG-TS, fragmented MP4 (CMAF), and RTMP for live distribution.

Key Technical Points

• Input Sources: SDI, RTP, RTMP, or high-bitrate mezzanine files.
• Codec Selection: H.264, H.265, VP9, AV1; choose based on device reach vs. compression efficiency.
• Segment and GOP Alignment: Short GOPs (1 to 2 seconds) for low-latency live and longer GOPs for efficiency.
• Hardware Acceleration: Elemental Live uses ASIC-based encoders to achieve predictable latency.

Transcoding Services (Re-Encoding Existing Media)

AWS Elemental MediaConvert handles file-based transcoding. It takes already encoded assets (e.g., H.264 MP4 mezzanine) and creates new renditions for adaptive bitrate streaming or codec migration. This process decodes the original, applies optional filters, and re-encodes to target specs.

Key Technical Points

• Bitrate Ladder Generation: Produces multiple renditions (resolutions/bitrates) from a single source for HLS/DASH.
• Codec Migration: H.264 → HEVC/AV1 to reduce storage or improve delivery efficiency.
• Filtering Stage: Scaling, frame rate conversion, color correction, and audio normalization before re-encoding.
• Quality Control: Each transcode introduces compression loss; start from mezzanine or high-bitrate source for minimal artifacts.

Manifest and Packaging Impact

Encoding

Elemental Live/MediaLive outputs compressed streams aligned to segment boundaries with init segments, ready for just-in-time packaging by MediaPackage. This allows real-time HLS/DASH manifest generation and supports low-latency streaming.

Transcoding

MediaConvert regenerates manifests and segment files offline from the mezzanine asset. It produces complete ABR ladders with static manifests, long cache headers, and versioned URLs for CDN edge persistence.

Latency and Workflow Differences

Encoding

Encoding services (like Elemental Live and MediaLive) are built for real-time operation. They compress incoming feeds and hand off segments immediately to packaging services like MediaPackage. This design keeps latency to just a few seconds or less for live streaming, where viewers expect minimal delay between capture and playback.

Transcoding

Transcoding with MediaConvert runs as a file-based process. It decodes an existing asset, optionally applies filters, and re-encodes it into multiple renditions. As it is not tied to a live feed, it operates offline or in non-real-time mode to focus on producing high-quality outputs and complete ABR ladders rather than minimizing latency.

Comparison Table