Renderer AOV and Compositing Output Guide

Supersampling - Supersampling becomes useful only when the reviewer can point to the part of beauty render, AOV package, EXR sequence, comp plate, or color-managed output that it changes. Supersampling (超级采样 / スーパーサンプリング) belongs to quality and cost control. Compare the noisy area, final sample setting, render time impact, and whether the same setting is acceptable for preview, bake, and final output. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.

Premultiplied Alpha - For a vendor-facing brief, Premultiplied Alpha is the anchor term and the localized labels explain the same inspected state. Premultiplied Alpha (预乘 Alpha / プリマルチプライアルファ) should be tested over a contrasting background, because edge halos often appear only after the image leaves the render preview. Record whether the delivery expects premultiplied or straight data before the compositor builds the comp tree. If that proof cannot be attached, the term should remain in review rather than be treated as covered.

Straight Alpha - The practical question around Straight Alpha is what evidence would make another reviewer agree with the same decision. Straight Alpha (直通 Alpha / ストレートアルファ) should be tested over a contrasting background, because edge halos often appear only after the image leaves the render preview. Record whether the delivery expects premultiplied or straight data before the compositor builds the comp tree. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.

Depth Map - Treat Depth Map as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Depth Map (深度图 / 深度マップ) is camera-dependent evidence. Keep the near and far range, camera source, bit depth, and any lens or calibration note beside the output so depth-based effects are not guessed later. The translation is therefore tied to evidence, not to an isolated glossary row.

Node Compositing - Node Compositing should be read through Nuke/Blender, not as a loose label in a translation sheet. Node Compositing (节点合成 / ノードコンポジット) should be documented as a visible comp structure. Save the node tree or layer stack, input plate, merge order, and final comparison frame so approval is not hidden inside a local project file. That keeps the article searchable while still giving lighting artist, render wrangler, or compositor something concrete to approve.

Layer Compositing - When 图层合成 or レイヤーコンポジット appears in a review note, the English term still needs the file state beside it. Layer Compositing (图层合成 / レイヤーコンポジット) should be documented as a visible comp structure. Save the node tree or layer stack, input plate, merge order, and final comparison frame so approval is not hidden inside a local project file. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.

Mask Channel - Mask Channel becomes useful only when the reviewer can point to the part of beauty render, AOV package, EXR sequence, comp plate, or color-managed output that it changes. Mask Channel (遮罩通道 / マスクチャンネル) is matte work. Review edge quality, spill or holdout behavior, animated mask range, and the result over a contrasting background before accepting the comp package. If that proof cannot be attached, the term should remain in review rather than be treated as covered.

Keying - For a vendor-facing brief, Keying is the anchor term and the localized labels explain the same inspected state. Keying (抠像 / キーイング) is matte work. Review edge quality, spill or holdout behavior, animated mask range, and the result over a contrasting background before accepting the comp package. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.