FFmpeg 8.1 AV1 and ProRes encoding: Sume has no codec field

FFmpeg 8.1 lists D3D12 H.264 and AV1 encoding and Vulkan compute-based ProRes encoding. None of that is selectable through Sume: its media routes reject codec and crf with ffmpeg_fields_rejected because the server compiles ffmpeg. A frame-accurate trim re-encodes with libx264 and yuv420p, and you do not choose otherwise.

FFmpeg facts are from its news page; Sume facts from Video trim, Timeline 1.0 and Video filter, read 2026-10-01.

What encoders does FFmpeg 8.1 list?

The news lists Vulkan compute-based codecs (ProRes encoding and decoding, DPX decoding), D3D12 H.264/AV1 encoding with D3D12 filters, and Rockchip H.264/HEVC hardware encoding. They depend on your hardware and build, which the page does not detail.

Can I choose an encoder on Sume?

No. The docs for video trim, video filter and video inspect all say the same thing: a client sending vf, filter, ffmpeg, cmd, codec, crf or friends is refused, because the server compiles ffmpeg. Timeline 1.0 says callers never send filtergraphs, codecs or shell fragments.

What can I control instead?

Trim takes an optional output of { width, height, fps } on exact precision only: width and height 256 to 2160, fps of 24, 25, 30 or 60. Audio is keep or drop, and kept audio is remuxed as AAC on exact. Those are the knobs; the encoder is not one of them.

Why does that matter for a pipeline?

If your own ffmpeg build produces AV1 or ProRes masters, keep that step on your side and send Sume a file it can read from media.sume.com. Sume's steps then return files made by its own settings. Details on the refusal are in ffmpeg fields rejected.

What should I do next?

Decide which step needs a specific encoder. Keep it local, and use Sume trim, filter or Timeline for steps where the documented output is acceptable. For trimming rules see trim a video by API.