SoftwareDecoderAvailability

What the linked FFmpeg can decode on the software path.

Phase 7 exists for codecs AVPlayer's HLS-fMP4 pipeline refuses, so the first question any routing decision asks is "does this build even have a decoder for it". That answer belongs to the binary, not to a table in our source: PrismCore links MPVKit's FFmpeg, Aether links its own MPVKit fork, and a configure flag either side of that line changes the answer. Hardcoding a codec list is how a router ends up promising a decode that fails at open.

So this is a runtime read of avcodec_find_decoder plus avcodec_get_hw_config, over the codec set phase 7 cares about. It is also what the availability test prints, which is the only honest way to document "what MPVKit ships" in a repo that doesn't own the FFmpeg build.

Hardware note: several of these codecs (VP9, MPEG-2, MPEG-4 ASP, H.264, HEVC) carry a videotoolbox hwaccel config in MPVKit's build, so "software path" is a routing name, not a promise about where the decode happens — SoftwareVideoDecoder takes the VideoToolbox route when it exists (see its docs) and only falls back to CPU decoding.