Interview Bank

Build an AI Short-Drama Production Pipeline With Agents in 14 Days

D3 Character Consistency: Character Sheets, Reference Images, and Style Locking — Keeping the Same Person the Same Person in Every Shot

• Where does the character consistency problem in image generation come from, and what engineering mitigations exist, with what trade-offs?生成模型的角色一致性问题是怎么来的？工程上有哪几种缓解手段，代价分别是什么？

  Common in ChinaCommon overseasBasic#image-generation#consistency

  How to reason about it · think before answering

  1. The differentiator is your first sentence. Saying 'the prompt wasn't detailed enough' reads as a user, not an engineer; the answer they want is that each request is an independent sample with no memory across calls.
  2. Follow the mechanism: a prompt only constrains the degrees of freedom you actually wrote down, and everything unwritten gets re-sampled — while face recognizability lives exactly in the details text cannot exhaust.
  3. Present the mitigations in three layers by what each one actually locks: a prompt template locks style and framing at near-zero cost; a fixed seed locks reproducibility for one identical prompt and stops helping the moment the prompt changes; a reference image locks the face, but only one per request, so two faces in one frame cannot both be locked.
  4. The trade-off discussion is where candidates separate: using a reference image means you must first produce a base image, which forces a human 'pick the reference sheet' step into an otherwise unattended pipeline.
  5. Volunteer the counter-intuitive rule: every derived image must reference the same base image, never the previous one. Chaining references accumulates drift, and by the fifth image it is a different person.
  6. Expect the follow-up: what if consistency still fails? The answer is cinematography — split two-character frames into reverse-angle singles and push secondary characters to wider shots, working around the API's limits with shot design.

  分析过程 · 先想清楚再作答

  1. 这题的区分度在第一句。答「提示词写得不够细」就掉到了使用者视角；面试官想听的是「模型每次请求都是独立采样、没有跨请求记忆」这个机制层面的原因。
  2. 顺着机制往下推就有了完整答案：提示词只约束了你写出来的那些自由度，没写的部分每次重新掷一遍；而人脸的辨识度恰好集中在脸型、眼距、鼻梁这些你没法用文字穷尽的细节上。
  3. 手段按「锁得住什么」分三层说，不要混在一起：提示词模板锁风格与构图，成本几乎为零；随机种子锁同一提示词的可复现性，换提示词即失效；参考图锁人脸，但每次请求只能带一张，双人同框锁不了两个人。
  4. 代价这一段才是拉开差距的地方：参考图要求你先有一张基准图，于是流程里必须插入一次「定妆并由人挑一张」的环节，这是整条自动化流水线上少数值得保留的人工卡点。
  5. 还要主动说一个反直觉的做法：派生图必须都参考同一张基准图，不能参考上一张。参考上一张会让偏差逐张累积，第五张已经不是同一个人了。
  6. 可以预期的追问：一致性做不到怎么兜底？答案是改镜头语言——把双人同框拆成正反打的单人镜头、次要角色用更远的景别，用拍法回避接口能力的边界。

  Key points

  • The root cause is that each request is an independent sample with no cross-request memory, so unconstrained degrees of freedom get re-rolled
  • A prompt template locks style and framing at near-zero cost but cannot lock facial detail
  • A fixed seed locks reproducibility for one identical prompt and stops helping once the prompt changes
  • A reference image locks the face, but you must first produce a base image and only one reference is allowed per request
  • Derive every variant from the same base image rather than chaining off the previous one, or drift accumulates image by image

  答题要点

  • 根因是模型每次请求独立采样、没有跨请求记忆，提示词没约束到的自由度会被重新掷一遍
  • 提示词模板锁风格与构图，成本几乎为零，但锁不住五官
  • 随机种子锁的是同一提示词的可复现性，提示词一变就失效
  • 参考图锁人脸，代价是必须先有基准图，且每次请求只能带一张，双人同框锁不了两个人
  • 派生图统一参考同一张基准图，不要链式参考上一张，否则偏差会逐张累积

D5 Voiceover, Subtitles, and Audio Tracks: Multi-Character Voices, Timeline Alignment, and Subtitle Files

• In a multi-character pipeline, how do you guarantee the same character keeps the same voice across episodes?多角色配音里，怎么保证同一个角色跨集用的是同一个声音？

  Common in ChinaCommon overseasBasic#tts#consistency#provider-abstraction

  How to reason about it · think before answering

  1. This looks like a voice question but is really about where state lives. 'Hardcode it in config' is not wrong, but stopping there shows no engineering judgment.
  2. Name the risk first: voice is part of a character's identity, and audiences are about as sensitive to it as to a face. Inconsistency across episodes has three usual causes — running each episode as an independent pipeline, picking voices from an ad-hoc or random mapping, and someone tweaking a character's global parameters while fixing the delivery of one line.
  3. The fix is to file the voice in the character record rather than in code: the record carries a voice id, and the dubbing step only reads it. Consistency then holds regardless of episode, run or operator — the same pattern as pinning appearance to a base reference image.
  4. Storing the voice id alone is not enough. Perceived sameness also depends on the baseline emotion and the speaking rate; the same voice at two different rates sounds like a different state of a person. Keep all three in the record, and allow per-line overrides of emotion only, never of rate.
  5. Add a defensive layer: record the voice id together with the model name in the artifact metadata. Vendors do retire and rename voices, and you want to be able to answer 'why does season two sound different' from data rather than memory.
  6. Expect the follow-up: what if the vendor retires that voice? Make voice selection part of the provider abstraction — the record stores the character's voice archetype, and the mapping to a concrete vendor voice lives in the adapter, so swapping vendors never touches the character records.

  分析过程 · 先想清楚再作答

  1. 这题看着像配音问题，其实考的是状态该存在哪里。答「配置里写死」不算错，但只答到这一层看不出工程判断。
  2. 先说清楚风险来自哪：声音是角色身份的一部分，观众对它的敏感度不低于脸。跨集不一致的典型成因有三个——每集独立跑一次流程、音色靠临时映射或随机挑选、以及某次为了改一句台词的语气顺手改了这个角色的全局参数。
  3. 解法是把音色归档而不是归代码：角色档案里带一个音色字段，配音环节只读不写。这样一致性由档案保证，跟哪一集、哪一次运行、谁跑的都无关。这跟角色形象靠基准图归档是同一套思路。
  4. 但只存音色标识还不够，跨集听感一致还依赖另外两项：基调情绪与语速。同一个音色用两种语速念，听起来像两个人的状态。所以档案里要一起存这三项，单条台词只允许覆盖情绪，不允许覆盖语速。
  5. 再补一层防御：把音色标识连同模型名一起记进产物元数据。厂商下线或重命名一个音色是会发生的，你要能查出「第二季为什么听起来不一样」，而不是只能凭记忆猜。
  6. 可以预期的追问：如果厂商真的下线了那个音色怎么办？答案是把音色选择也做成 provider 抽象的一部分：档案里存的是角色的音色角色定位，映射到具体厂商音色的表放在适配层，换厂商或补映射时不动档案。

  Key points

  • Store the voice in the character record and have the dubbing step read it only, so consistency is independent of episode, run or operator
  • Keep voice id, baseline emotion and speaking rate together; allow per-line emotion overrides but never rate overrides
  • Write the voice id and model name into artifact metadata so you can explain why a later season sounds different
  • Typical causes of drift are per-episode independent runs, ad-hoc mappings, and global tweaks made while fixing one line
  • Fold voice selection into the provider abstraction: records hold the archetype, the adapter maps it to a concrete vendor voice

  答题要点

  • 把音色存进角色档案，配音环节只读不写，一致性与集数、运行次数、操作人无关
  • 档案里要同时存音色标识、基调情绪与语速；单条台词只允许覆盖情绪，不允许覆盖语速
  • 把音色标识与模型名一起写进产物元数据，便于回答「为什么这一季听起来不一样」
  • 跨集不一致的典型成因是每集独立跑、临时映射、以及改一句台词时顺手改了全局参数
  • 音色选择应纳入 provider 抽象：档案存角色的音色定位，具体厂商音色的映射放在适配层