The snippets, ordered obscure → unmistakable

  1. Snippet 1(Bitstream helper)
  2. Snippet 2(AVPacket lifecycle)
  3. Snippet 3(Codec registration)
  4. Snippet 4(Filter graph)
  5. Snippet 5(MUX / demuxer)
  6. Snippet 6(ffmpeg.c main)

Why this project gives itself away

The give-away. Snippets 1 and 2 use av_* / AVPacket — the FFmpeg API prefix is famous. Snippet 3 is the `FFCodec` decoder registration; the AV_CODEC_ID_H264 enum and H264Context struct nail it. Snippet 4 is the filter graph parser — AVFilterGraph is unique to ffmpeg/libavfilter. Snippet 5 names ff_matroska_muxer with the project's NULL_IF_CONFIG_SMALL macro. Snippet 6 is the ffmpeg.c main + the canonical project tagline.

How a Framed puzzle is built

Every Framed project ships exactly six snippets, hand-ordered from deeply obscure to unmistakable. The first snippet must be plausible for a dozen codebases — a generic loop, a small utility, a comment that could appear anywhere. The last snippet carries a project-specific tell: a function name, a code-comment idiom, a file header, a build invocation. Between them sit four snippets that gradually narrow the field. Reading them in order is half the puzzle: a returning Framed player learns to triangulate on indentation conventions, comment voice, naming, and the small-but-distinctive choices that betray a project's era and community.