X video audio must be AAC-LC, not HE-AAC: check an AI video
X requires AAC Low Complexity audio, mono or stereo, with H264 High Profile and YUV 4:2:0. What Sume's exact trim keeps and re-encodes, and what it leaves.

X's media best practices require audio to be AAC with the Low Complexity profile; High-Efficiency AAC is not supported. Audio should be mono or stereo, not 5.1 or more. Sume's default exact trim re-encodes video to libx264 and yuv420p and remuxes kept audio as AAC, but the docs do not say which AAC profile or channel layout, so verify the file before upload.
X rules are from its best-practices page, read 2026-10-01. Sume behavior is from Video trim.
What does X require?
The audio and codec rows, as X lists them:
| Item | X requirement |
|---|---|
| Audio codec | AAC with Low Complexity profile (HE-AAC not supported) |
| Channels | Mono or stereo (not 5.1+) |
| Video codec | H264 High Profile |
| Pixel format | YUV 4:2:0 only |
| GOP | No open GOP |
| Scan | Progressive |
What does Sume's exact trim do?
precision: "exact" is the default: a frame-accurate re-encode with libx264 and yuv420p. With audio: "keep", the docs say exact remuxes kept audio as AAC. That is consistent with X's AAC, H264 and YUV 4:2:0 rows. It does not by itself prove H264 High Profile, the audio profile, or the channel count, and the docs make no such claim.
What about keyframe mode?
precision: "keyframe" is stream copy. Nothing is re-encoded, so the output carries whatever codecs the source had. If the source audio is HE-AAC or 5.1, keyframe mode keeps it, and X would not accept it. For an upload to X use the default exact mode; see trim without re-encoding for when stream copy is fine.
How do I get a mono audio track?
Audio detach can return a track with channels set to mono (default source), as wav or mp3. That is a separate audio file, not a re-muxed video. Check the final MP4 with a probe before posting.
Sources
Related posts
More in Developers
- X video max 1280x1024, ratio 1:3 to 3:1, 60 fps: conform a clip
X video must be 32x32 to 1280x1024, 60 fps or less, ratio 1:3 to 3:1. Read literally, a default 1080x1920 Timeline file is over; conform with video-trim.
- YouTube 48fps upload: keep the frame rate, conform to 24/25/30/60
YouTube accepts 48 and 50 fps and says to upload at the recorded rate. Sume's trim and Timeline output.fps conform only to 24, 25, 30 or 60.
- Deinterlace before YouTube upload: Sume has no deinterlace filter
YouTube says deinterlace 1080i60 to 1080p30 before upload. Sume's video-filter allowlist names no deinterlacer and refuses unknown filters.
- YouTube moov atom and edit lists: keyframe trim vs exact trim
YouTube asks for MP4 with moov first and no edit lists. Sume's keyframe trim is a stream copy; exact re-encodes. The docs do not state moov placement.
Written by Sume