Hardware-accelerated live video workflow
Use acceleration for measured stream density—not as a codec shortcut
Hardware-accelerated transcoding can turn one live contribution feed into several delivery-ready outputs while keeping CPU demand predictable. Enhanced RTMP can carry modern codecs such as HEVC when every component in the path implements the same specification. These are separate decisions: an accelerator changes how frames are processed; Enhanced RTMP changes how a codec is signalled over RTMP.
The practical answer
Choose the output contract first: codec, profile, resolution, frame rate, bitrate, GOP, audio format and destination protocol. Then benchmark that exact contract on the instance or accelerator you intend to operate. Do not buy capacity from a vendor’s maximum stream count alone, and do not send HEVC over RTMP until the publisher, relay and receiver have all passed an interoperability test.
Callaba can apply supported video and audio transcoding settings to a restreaming workflow in cloud or self-hosted deployments. The current product exposes software profiles and accelerator-backed profiles where the selected release and hardware support them. The product boundary is described on Callaba Live Video Transcoding; the operator procedure lives in the Restreaming user guide.
The moving markers show processing flow and changing workload, not measured latency or utilization. Motion is removed when reduced-motion is requested.
Separate four things that are often called transcoding
Encoding compresses a raw or baseband source for the first time. Transcoding decodes an existing encoded stream and creates a different encoded output. Scaling changes raster dimensions, although it normally happens inside a transcode. Transmuxing changes the container or delivery wrapper without re-encoding the audio and video.
This distinction controls both quality and cost. A copy or transmux path avoids a generation of compression when the source codec already fits the destination. A full transcode is justified when the receiver cannot decode the source, the bitrate is unsuitable, the frame size must change, the audio contract differs, or several audience profiles are required. Adding a transcode merely because the control is available consumes capacity and introduces another point of failure.
What media acceleration actually changes
A hardware video engine moves some decode, scale or encode work away from general-purpose CPU cores. The result can be higher stream density and more consistent processing time, but only for supported combinations. Filters, overlays, audio work, multiplexing and control processes may still consume CPU. Device memory, PCIe transfer, network bandwidth and the number of decode and encode sessions can become the new limits.
AWS describes EC2 VT1 instances as dedicated live-transcoding instances built around AMD-Xilinx Alveo U30 accelerators. Its published reference supports H.264 and H.265, resolutions up to 4K UHD, and parallel output profiles. AWS also publishes stream-density examples, but those figures belong to its reference workloads. They are useful for an initial shortlist—not a Callaba capacity promise and not a substitute for testing your codec, frame rate, filters and number of renditions.
Acceleration is a good fit when
You have many concurrent, repeatable live profiles; CPU encoding cannot meet density or latency targets; and the chosen device supports every required decode, scale and encode operation.
CPU may remain the better fit when
The workload is small or irregular, depends on unsupported filters or codecs, needs a quality mode unavailable on the accelerator, or cannot justify the operational complexity of another hardware runtime.
Enhanced RTMP is an interoperability contract
Legacy RTMP/FLV was built around older codec signalling. The Veovera Enhanced RTMP specification adds FourCC-based signalling for modern video codecs, including HEVC, VP9 and AV1, as well as HDR-related metadata. That makes modern codecs possible over an RTMP connection; it does not make every RTMP server, encoder, recorder or platform compatible.
For an HEVC-over-RTMP workflow, validate the exact chain:
- Publisher: confirm that the installed encoder or software release produces Enhanced RTMP rather than assuming every HEVC option can be paired with every transport.
- Ingest and relay: prove that the service preserves or correctly processes the enhanced codec signalling.
- Destination: check the current platform documentation and account controls. A platform that accepts H.264 RTMP may still reject HEVC RTMP.
- Playback: inspect the actual audience format. HEVC contribution does not imply that every browser receives HEVC.
Build the profile from the destination backward
| Decision | What to specify | What proves it |
|---|---|---|
| Codec and profile | H.264, HEVC or another supported encoder; required profile and bit depth. | The final receiver decodes representative motion, color and audio. |
| Raster and cadence | Output width or height, frame rate and any interlace handling. | No unintended crop, aspect error, duplicate cadence or field artefacts. |
| Rate control | Target bitrate, quality policy, preset and available headroom. | Measured output rate and acceptable picture quality during the hardest scene. |
| GOP | Keyframe interval required by the destination or packager. | Probe output keyframes and verify clean segment or rendition changes. |
| Audio | Codec, sample rate, bitrate and channel selection. | Listen to the selected program after the final handoff; meters alone are insufficient. |
| Capacity | Concurrent inputs, outputs per input and recovery reserve. | A sustained soak test at expected peak load plus one planned failure. |
Configure and prove the workflow in Callaba
- Create one reachable input and verify its codec, resolution, frame rate, bitrate and audio before enabling processing.
- In Restreaming, select that verified input and the required output. Enable only the supported transcoding settings needed to satisfy the destination contract.
- Begin with one output. Check decoded video, audio, sync, keyframes and destination acceptance. If Enhanced RTMP is required, use the exact supported publisher and receiver versions planned for production.
- Increase concurrency in controlled steps. Record CPU, accelerator utilization where available, memory, processing stability and network headroom.
- Interrupt the input, restore it, and confirm how the transcoder and output reconnect. A density benchmark without recovery evidence is incomplete.
- Add further renditions only after each one has an audience, platform or archive requirement.
Teams embedding the validated operation in another control surface can continue to the live video transcoding API workflow. The API is the second layer: it can reproduce an approved profile, but it cannot decide whether the profile is interoperable or visually acceptable.
Benchmark cost without freezing an old price into the design
Cloud instance prices and regional availability change. Instead of carrying an old hourly figure into a new proposal, calculate cost per accepted output hour: instance cost plus data transfer and adjacent services, divided by the number of outputs that pass the quality and recovery test. Compare like with like—same input, codec, resolution, frame rate, bitrate, quality target and concurrency.
HEVC may achieve similar subjective quality at a lower bitrate than H.264 for some material and encoder settings. The saving is not a universal percentage. Measure representative sports, camera noise, graphics and low-motion scenes, then include decoder and licensing constraints in the decision. The cheapest encoded gigabyte is not automatically the lowest-cost production path.
Troubleshoot by observing the boundary
Input is healthy, output never starts
Check that the selected codec and accelerator exist in the running deployment, then inspect output URL, container and destination support. Keep the healthy input unchanged while isolating the output.
Output connects but shows black video
Verify profile, bit depth, pixel format and codec signalling at the receiver. In an Enhanced RTMP test, confirm the receiver implements the same specification rather than treating a TCP connection as media proof.
Latency grows during the event
Look for a processing queue, overloaded decode or encode sessions, expensive filters and network backpressure. Reduce concurrency or simplify the profile before changing unrelated transport settings.
Quality collapses on motion
Test a representative scene, inspect target rate and encoder mode, and compare the chosen preset with the available processing budget. A static test card cannot validate a sports profile.
Authoritative references
- AWS EC2 VT1 instance overview — accelerator role, codecs and published workload characteristics.
- AWS VT1 launch and reference workloads — instance sizes, reference stream density and processing model.
- Veovera Enhanced RTMP V2 specification — current codec and metadata signalling contract.
- FFmpeg transcoding documentation — processing terminology and command behavior.
Frequently asked questions
Does hardware acceleration always reduce live-transcoding cost?
No. It can improve density for supported workloads, but the result depends on utilization, required filters, codec quality, network cost and operational overhead. Benchmark cost per output that passes acceptance, not theoretical sessions per device.
Is HEVC over RTMP the same as ordinary RTMP?
It uses the RTMP transport family with enhanced codec signalling. Every publisher, relay and receiver in the path must support the relevant Enhanced RTMP behavior. Ordinary H.264 RTMP compatibility does not prove HEVC compatibility.
Should every output be transcoded?
No. Preserve the source when its codec and media profile already meet the destination contract. Transcode only to solve a compatibility, bandwidth, resolution, frame-rate, audio or rendition requirement.
Prove one real profile before planning the fleet
Connect the source you actually use, create the destination profile it must satisfy, and measure quality, concurrency and recovery in the deployment model your team will operate.
Evaluate Callaba Live Video Transcoding
