- Newest
- Most votes
- Most comments
Thank you for the detailed feature request. You've identified a real architectural constraint in how Smart Subtitles currently integrates with MediaLive when producing multi-aspect-ratio outputs.
You're correct that Smart Subtitles is designed to be aspect-ratio-aware—the feature automatically adjusts line length and wrapping based on the aspect ratio you specify (or defaults to 16:9 when omitted). This works well for single-aspect-ratio workflows, where horizontal video can accommodate more characters per line than vertical video, with no player-side logic required.
However, as you've discovered, MediaLive currently supports only one SMART_SUBTITLE caption selector per input attachment. This means you cannot create two separate subtitle tracks—each optimized for a different aspect ratio—within the same channel, even though the underlying Elemental Inference SubtitlingConfig does accept an aspectRatio parameter with width and height values.
Your proposed solutions are both architecturally sound approaches:
Option A (multiple selectors referencing different Inference outputs) would align with how other MediaLive features handle multiple variants of the same content type, allowing each selector to reference a distinct subtitling output configured with its own aspect ratio.
Option B (per-output-group aspect ratio override) would keep the single-selector model but allow the encoder to apply different layout hints at the output stage, which could be simpler operationally.
The current limitation does indeed force a choice between:
- Using one aspect ratio setting that compromises readability on one of your outputs
- Running two separate MediaLive channels (one per aspect ratio), which doubles your encoding costs and operational complexity
This is particularly relevant given that Smart Crop and Smart Subtitles are designed to work together in the same channel, and the documented use case of producing both landscape and vertical outputs from a single source is a common pattern for reaching both traditional broadcast and mobile/social audiences.
I'd recommend submitting this through the AWS Support Center at https://console.aws.amazon.com/support/ as a feature request, including the specific use case and technical details you've outlined here. Product teams prioritize enhancements based on customer demand and real-world use cases like yours. You might also consider discussing your current AWS Support plan options if you need faster engagement on feature requests or architectural guidance for interim workarounds.
Sources
Generate live subtitles with AWS Elemental Inference Smart Subtitles | AWS for M&E Blog
SubtitlingConfig - AWS Elemental Inference
Setting up Elemental Inference features for the first time - MediaLive
Using AWS Elemental Inference with MediaLive | AWS for M&E Blog
Relevant content
asked 2 years ago
asked a year ago
- AWS OFFICIALUpdated 2 years ago
