Skip to documentation
Deploy on AWS
Menu
Documentation · 14 of 19

Docs/Supported transcoding profiles

Supported Transcoding Profiles

JetEncode treats a transcoding profile as supported only when validation accepts it and the integration suite can produce an artifact that matches the expected FFprobe/Shaka properties.

The release gate uses the production encoders with real FFmpeg and FFprobe. When Shaka Packager is installed, streaming validation also uses real Shaka.

Video container / codec contract

ContainerSupported video codecsDefault
MP4H.264, HEVC, copy, no-videoH.264
WebMVP8, VP9, no-videoVP9
MPEG-TSH.264, HEVC, copy, no-videoH.264
MOVH.264, HEVC, DNxHD, ProRes, ProRes KS, copy, no-videoH.264

Codec/container combinations outside this table are rejected during validation rather than being passed optimistically to FFmpeg.

Audio codec contract inside video containers

ContainerSupported audio codecsDefault
MP4AAC, AC-3, copy, no-audioAAC
WebMVorbis, no-audioVorbis
MPEG-TSAAC, AC-3, MP2, copy, no-audioAAC
MOVAAC, AC-3, PCM S16LE (pcm / pcm-s16le), PCM A-law, PCM U8, copy, no-audioAAC

copy is intentionally source-dependent: the source stream must already be legal for the destination container. The validation suite verifies copy using its known H.264/AAC fixture.

Standalone audio containers

ContainerSupported codecsDefault
OGGVorbisVorbis
AACAACAAC
MP3MP3MP3
WAVPCM S16LE (pcm / pcm-s16le), PCM A-law, PCM U8PCM S16LE

Legacy tokens that do not have a supported destination profile (for example AMR-NB, WMA2, FLAC, or Theora in the current container inventory) are rejected. A token being understood by an old FFmpeg mapping is not a production support promise.

H.264 profiles and pixel formats

The following H.264 combinations are explicitly generated and FFprobed:

vprofileRequired supported pix_fmtExpected FFprobe profile
baselineyuv420pConstrained Baseline
mainyuv420pMain
highyuv420pHigh
high10yuv420p10leHigh 10
high422yuv422pHigh 4:2:2
high444yuv444p10leHigh 4:4:4 Predictive

H.264 without an explicit profile also validates yuv422p and lets x264 select the matching profile automatically.

HEVC supports normal yuv420p and validated 10-bit yuv420p10le. vprofile and level are currently part of the supported H.264 contract only.

DNxHD

DNxHD is intentionally not advertised as an arbitrary codec/resolution combination. The supported profile is:

  • MOV
  • 1280×720
  • 25 fps
  • 90 Mbps
  • yuv422p
  • PCM S16LE audio

Other DNxHD combinations are rejected until they are explicitly validated.

Resolution profiles

Landscape H.264 validation runs every accepted preset and verifies the actual output dimensions with FFprobe:

144p, 240p, 360p, 480p, 540p, 576p, 720p, 1080p, 1440p, 2160p, 4k, plus custom WxH.

Portrait input is tested separately so preset scaling is verified to preserve orientation.

4k is explicitly parsed as a resolution, not as a 4k bitrate token.

Frame-rate profiles

0fps, 15fps, 23.98fps, 25fps, 29.97fps, 30fps, 60fps.

0fps means preserve the source frame rate. It must not emit FFmpeg -r 0.

Encoding options

The validation suite verifies real artifacts for:

  • quality/CRF + maxrate on H.264, HEVC, VP8, and VP9
  • H.264 profile and level
  • supported H.264/HEVC pixel formats
  • fragmented MP4 with a real moof atom
  • H.264 two-pass
  • HEVC two-pass
  • watermark / transpose / flip / crop / trim operations

Two-pass is accepted only for H.264/HEVC, requires a video bitrate in the resolved output, and cannot be combined with quality/CRF mode.

Audio properties

Sample-rate validation covers 8000, 11025, 22050, 44100, and 48000 Hz.

Mono and stereo are asserted directly. multi is tested with a generated 5.1 source and must preserve six channels.

PCM codecs do not accept bitrate settings because that option is meaningless for these uncompressed profiles.

Image profiles

  • JPEG
  • PNG
  • WebP
  • GIF
  • WebP with automatic height (400x)
  • animated WebP scene extraction
  • number / interval / offset thumbnails
  • sprite generation and VTT output

Streaming profiles

The real integration suite verifies:

  • video-only HTTP-stream variants
  • audio-only variants
  • mixed audio/video variants
  • HLS packaging
  • DASH + HLS fMP4 packaging
  • AES-128 HLS post-encryption

Generated manifests and referenced files must exist and be non-empty. HLS media segments are probed with FFprobe.

Release commands

Media-only validation:

make test-transcoding

Full release gate with PostgreSQL available:

make test-release

There is deliberately no line-coverage requirement. The release criterion is that every advertised profile produces the expected media artifact and that the real job/infrastructure workflows pass.