Editing and finishing

Timelines, conform, interchange, codecs, exports, subtitles and delivery

• articleWhich sample rate and sample format does Unity Recorder 5.1.7's Audio Recorder write, and can I choose them?
  The Unity Recorder (5.1.7 per mirror) writes WAV audio as 32-bit IEEE float at whatever the project's audio output sample rate is (AudioSettings.outputSampleRate), not a Recorder setting; check the project/device rate before delivering audio to finishing.
• articleWhat target formats and signal-capture practices does IASA-TC 06 (2019) set for video digitisation, including frame-level fixity?
  IASA-TC 06 (2019) gives several acceptable preservation targets for analogue videotape (AVI/QuickTime with FFV1 or v210, Matroska/FFV1, MXF uncompressed or JPEG 2000) with growing institutional consensus on Matroska/FFV1, notes AS-07 became SMPTE RDD 48 in 2019, describes frame-level fixity in sidecars (ffmpeg framemd5/framecrc) or embedded, and treats VTR alignment with TBC, proc amp, waveform monitor and vectorscope as part of signal capture.
• articleWhat does an ACES Metadata File (AMF) record at its published version 2.0 and what is optional versus required?
  AMF v2.0 (schema at aces-amf e2b99012) is an XML sidecar describing one ACES viewing pipeline: only amfInfo (with dateTime and a UUID) and a pipeline with pipelineInfo/systemVersion are required; clipId, the input transform, any number of ordered look transforms (CDL embedded with a declared working space, CDL referenced by ID from a file, or a CLF/other transform), an optional workingLocation marker and an optional output transform may follow, and earlier pipelines are kept as repeated archivedPipeline elements. The version attribute is fixed at 2.0. The user guide (list dated 21 July 2025) names Pomfort, Colorfront, Resolve 19.1+ and Baselight 6.0+ as exporters; per-tool behaviour was not tested. Conflict within the AMF work: the spec page gives applied="false" as the default, while the XSD makes the applied attribute required on input, look and output transforms. Writers should always emit applied explicitly.
• articleWhat is the ISDCF digital cinema naming convention (DCNC) structure, and how is it checked by tools?
  ClairMeta (commit b3b66a0) encodes the ISDCF naming convention as rule set '9.6' with fields in order: title (up to 14 characters), content type, aspect ratio, language (audio-subtitle, optional CCAP/OCAP), territory-rating, audio type, resolution, studio, date, facility, standard and package type. Reading the code (not run) shows two problems. Its language patterns accept only two- or three-letter codes, but the current ISDCF register has 91 four-letter codes, so names using them would probably be flagged. Its resolution pattern (^2K|4K$) is loosely anchored, so strings that merely start with '2K' or end with '4K' would pass. This is a tool's reading of the convention, not the convention itself.
• articleWhat actually helped in an 8-day AI video-editing trial (Jun 2026): editor plugins, agent-made B-roll, Claude + HyperFrames motion graphics, Omni footage edits
  Creator-reported: statements attributed to the creator(s) come from discovery's reading of auto-caption transcript excerpts; the curator checked the video metadata (title, date, length) and any cited documentation pages, not the spoken claims. Nothing was tested; promotional or sponsored framing applies where stated. Dan Kieft and team (2026-06-12) sorted tools into money-saving, speed and creativity. Useful: Higgsfield plugins inside Premiere Pro, After Effects and Figma (generate shots, reframe 16:9 to vertical, 4K upscale; background removal "mixed results"); Higgsfield "Supercomputer" agent producing intro scenes and B-roll/infographic "cards" for explainers, with failures retried on request; Claude Code + HyperFrames (HeyGen's Apache-2.0 open-source HTML-to-video renderer "built for agents", R6) to add titles, captions, lists, counters and UI animations around a raw talking-head recording by describing them, then iterating in plain language ("make the transition faster"); Googl...
• articleHow do I hand storyboard boards to an editor as an animatic, and what could OpenTimelineIO carry that Storyboarder's exporter carries?
  Partially verified: the curator re-read none of the cited sources; S10, S12, S8 rest on the producer's pinned reading. Storyboarder's Final Cut Pro XML export makes one clip per board named from its dialogue, otherwise its action text, otherwise the image filename, puts board notes in the clip description, rounds the timebase up from the project fps and sets the NTSC flag for fractional rates, and uses the project's default board timing (2000 ms in the example) when a board has no duration. A mapping onto OpenTimelineIO clips and markers is plausible but is a proposal, not a documented profile.
• articleWhat do the Unreal Engine 5.8 Movie Render Queue/Graph docs say about temporal sampling, warm-up frames, frame-rate override and audio output for offline capture?
  Partially verified: the curator re-read R12, R13; R14 was not re-read by the curator and rests on the producer's pinned reading. Unreal MRQ guidance uses render and engine warm-up counts (120 each in the guide) to build temporal history before output, supports .wav audio output, and uses temporal samples (sub-frame) for anti-aliasing/motion blur; exact temporal-sampling prose was not re-read by the curator.
• articleWhat do Unity Recorder 5.1.7 and Time.captureFramerate document about constant versus variable frame rate capture, audio capture and determinism?
  Partially verified: the curator re-read R5, R6; R10, R11, R7, R8, R9 were not re-read by the curator and rest on the producer's pinned reading. Unity Recorder offers Constant playback (fixed interval between recorded frames, recommended for non-interactive content) and Variable playback (game-view timing); Time.captureDeltaTime advances game time at a fixed interval regardless of real time. The docs read do not state that Constant mode uses captureDeltaTime (producer note kept).
• articleDo the content-light statistics x265 computes match the H.265 definition of MaxCLL and MaxFALL?
  By reading code against D.3.35, the x265 statistics differ from the spec rule in three ways: they use the Y (luma) plane code values, not per-pixel max(R,G,B) in linear light scaled to cd/m2; the frame average is over the whole stored frame; and the reported MaxFALL is the mean of frame averages, not the maximum. This is a code-derived inference about the statistics, not a statement about what x265 writes in the SEI, which comes from the --max-cll option. No execution was done.
• articleHow do I apply Murch's priority order to choosing among AI-generated takes and cut points, and which failures can I accept?
  Problem. Generated shots rarely satisfy every continuity criterion; reviewers need a rule for what to give up. Conditions. Multiple candidate takes or cut points for the same beat; labelled inference throughout, built on Murch's list (C3-B597-01). Method [inference]. (1) Emotion: pick the take whose performance or atmosphere is right for the moment, even if later criteria are flawed; reject takes that are clean but emotionally flat. (2) Story: the shot must show the story information (who, what changed); (3) Rhythm: choose the in and out point where the cut feels right, which is a free choice with generated footage because you can trim a clip anywhere inside it. (4) Eye-trace: check that the viewer's eye lands where the next shot expects (face, hand, object) in the first frames after the cut; generated clips often start with the subject not yet in position. (5) Planarity: screen direction and eyeline across the cut (see C3-B571-12 for the 180-degree rule, eyeline match and match-on-...
• articleDo the AMIA open-workflows list and OSSArcFlow materials define AV normalisation or conformance checking steps?
  The AMIA open-workflows README is a curated list of links (Archivematica case studies, OSSArcFlow, RAWcooked DPX workflows, MediaConch, NYPL specifications) and states no normalisation targets or conformance rules itself; AV normalisation and conformance parameters have to be taken from tool-level sources such as Archivematica's format policy registry or MediaConch policies (negative result for this list).
• articleWhat audio sample rate and channels does Unity Recorder 5.1.7's Movie Recorder write for H.264 MP4 / ProRes, and can I set them?
  In Unity Recorder 5.1.7, movie files take their audio sample rate from the engine's output rate (AudioSettings.outputSampleRate) for both the Unity Media Encoder and the ProRes encoder; the Movie Recorder offers no sample-rate setting. The Media Encoder records Mono or Stereo, ProRes Stereo only. Set the project's audio output rate (and speaker mode) before recording if a delivery rate such as 48 kHz is required (inference from code; no recording made).
• articleWhat state does an open-source interactive-video branching component keep, and does it preload or buffer branches?
  H5P Branching Scenario (1.10.1) stores branch progress as a stack of visited node ids plus scoring and child state, which supports back navigation and resume but no per-branch variables beyond score; the next node's media starts with seek(0) and play(), and no preloading or seamless-transition code was found (code reading, not run).
• articleWhat did Smith & Henderson's eye-tracking study find about continuity editing rules (match action, gaze match) and unnoticed cuts, and what does it mean for cutting AI shots?
  Problem. Continuity rules are taught as craft; is there evidence that they hide cuts? Conditions. Smith & Henderson (2008): participants watched seven feature-film excerpts (five minutes each, DVD-quality) and pressed a button when they saw an edit; eyes were tracked; edits were hand-coded for adherence to the rules, including Between Scene, Within Scene, Match Action and Gaze Match. Method (reported). Edits constructed according to the Continuity Editing Rules gave greater edit blindness than edits not adhering to them; a quarter of edits joining two viewpoints of the same scene went undetected, a third when the cut coincided with a sudden onset of motion. The Match Action rule is stated in the paper as a smooth cut between two viewpoints of the same action achieved by coinciding the cut with a sudden onset of motion. Only 8.8% of edits coincided with a saccade, and the authors conclude that most unnoticed cuts come from inattentional blindness as viewers follow the narrative. For ...
• articleHow do I place a dry TTS line in a room with an impulse response using FFmpeg's afir filter, and what are its limits?
  Problem: add a measured or generated room to a clean synthetic voice from the command line. Conditions: FFmpeg with the afir filter; a dry mono voice file and an IR file (mono, stereo or multichannel). Method: afir takes the first input as signal and further inputs as FIR coefficients; the documentation's example is ffmpeg -i input.wav -i middle_tunnel_1way_mono.wav -lavfi afir output.wav. Parameters: dry and wet gains, length (portion of IR used), irnorm (norm applied to IR coefficients, default 1, negative values leave the IR untouched), irgain (0 to 1, applied after irnorm), irlink (normalise multichannel IR channels together, default true), maxir (maximum IR duration, default 30 s, range 0.1 to 60 s), minp and maxp (partition sizes, default 8192; lower values reduce latency at CPU cost), nbirs and ir (several IRs switchable at runtime, up to 32), precision auto/float/double. The filter is described as usable for room equalisation, auralization and spatialization. Example (infere...
• articleHow should I bring an SDR AI plate (MP4, PNG) into an OCIO/ACES or Resolve colour-managed timeline: as display-referred or scene-linear, and which OCIO roles and rules matter?
  Problem. AI plates are rendered pictures with no camera log or scene-referred metadata, yet colour-managed timelines expect an input colour space. Conditions. OCIO v2 configs (docs 'latest' at 2026-10-23, CG config based on ACES 2.1); applies to any OCIO application. Method. OCIO documentation facts: a config has Roles, File & Viewing rules, Displays & Views, Looks, scene-referred Colorspaces, Display Colorspaces and Named Transforms; the CG config says baking in an ACES Output Transform needs a DisplayViewTransform rather than a ColorSpaceTransform, because applying a view transform is a different process from converting between colour space encodings; the data role should use a colour space with data: true so no transforms are applied; the default role is the fallback colour space only when strictparsing is false; ociocheck detects undefined colour spaces and roles; the authoring guide warns that applications vary in how they interpret roles. Workflow [inference, three cases]. (A)...
• articleWhat is Murch's Rule of Six as he wrote it (six criteria, the 51/23/10/7/5/4 weights, the sacrifice-from-the-bottom rule), and how seriously did he mean the numbers?
  Problem. The Rule of Six is quoted everywhere with varying numbers; an agent needs the original wording. Conditions. The text read is a course page that reproduces pp. 17-20 of Murch's In the Blink of an Eye (1995) and says so itself; it is a copy of copyrighted text, not the publisher's edition, so page numbering and wording should be checked against the book. Method (what the text says). An ideal cut satisfies six criteria at once: (1) it is true to the emotion of the moment, (2) it advances the story, (3) it occurs at a moment that is rhythmically interesting and right, (4) it acknowledges eye-trace, the location and movement of the audience's focus within the frame, (5) it respects planarity, the grammar of three dimensions transposed to two (stage line etc.), (6) it respects three-dimensional continuity of the actual space. Weights: Emotion 51%, Story 23%, Rhythm 10%, Eye-trace 7%, Two-dimensional plane of screen 5%, Three-dimensional space of action 4% (sum 100). Murch says th...
• articleHow can I measure and match colour and brightness between separately generated shots using FFmpeg (signalstats, colorbalance/colorcorrect/colortemperature, normalize, colormap)?
  Problem. Generated shots of the 'same' scene differ in exposure, white balance and saturation, and there is no colour chart in frame. Conditions. Two or more SDR clips decoded to the same colour space and range; a reference frame you accept as the look. Method. (1) Measure each clip. signalstats exports per-frame metadata keys such as lavfi.signalstats.YMIN and reports for Y, U, V: min, 10th-percentile (LOW), average, 90th-percentile (HIGH), max; SATMIN..SATMAX; HUEMED and HUEAVG; and YDIF/UDIF/VDIF (difference to the previous frame). Use YLOW/YAVG/YHIGH for black point, mid and white point, and SATAVG and HUEAVG for colour (values are in the file's coded range 0-255 as the doc states). The doc describes the filter as aimed at problems of digitised analog video, so use its numbers as relative comparisons only. (2) Correct. colortemperature (1000 to 40000 K, default 6500, mix, pl preserve lightness); colorcorrect (red/blue shift for shadows rl/bl and highlights rh/bh, saturation -3 t...
• articleGiven the structural rules, how should I cut, extend or loop a generated song to a picture duration without breaking phrase structure?
  Problem. Picture is locked to a duration; the generated song is not. Conditions. Pop/rock cue, structure labelled (manually or by an analyser); the generator offers extend/crop (see C3-B575-06). Method (synthesis, mostly inference). 1) Label sections and grid: sections 8-24 bars, phrases 4 bars, hypermeter 4 (C3-B614-01/05). 2) Choose the edit unit: whole sections, or sr/dc halves, never lone phrases (C3-B614-02). 3) To shorten: drop a repeated cycle (e.g. second verse-prechorus) rather than a mid-section phrase; keep the bridge once before the last chorus (C3-B614-03). 4) To lengthen: repeat the final chorus or insert an instrumental cycle, then take the outro (C3-B614-04). 5) Land key hits by shifting tempo or the section, not by squeezing a phrase (see C3-B007-G1-06). 6) Cross-fade at a grid boundary after a fill, and audition both sides. Failure modes: tempo drift and non-integer bar counts in generated audio; lyric lines cut in half. Limitations. Entirely derived from analytic ...
• articleWhat do ElevenLabs' Text to Dialogue and Studio docs say about request size, determinism, speaker count and paragraph locking for long dialogue?
  Problem: assemble long, consistent multi-speaker audio from an API. Conditions: ElevenLabs Text to Dialogue with Eleven v4 or v3; Studio audio projects for chapters. Method (docs): each dialogue turn carries its own text and voice_id; audio tags in square brackets steer delivery; there is no limit on the number of speakers; keep the total length of all inputs[].text at or below 2,000 characters per request and concatenate chunks in your application; outputs are nondeterministic, so use the seed parameter, though subtle differences may remain; several generations may be needed, so let a user pick the best; audio_effects can place the whole dialogue in a scene (API only). Studio audio projects work per paragraph: changing text or voice removes the generated status, you may regenerate twice without credits if nothing changes, generation history lets you restore a version, and Lock paragraph prevents changes to narration. Failure modes: voice or loudness drift across 2,000-character chu...
• articleI have a finished master: what are the handoffs to a cinema/streaming package, to captions and audio description, and to an archive, and which public tool or text checks what at each one?
  Synthesis supported by reviewed steps: the chain from master to archive has distinct handoffs (package to IMF or DCP; adding timed text and audio description; validation; archive packaging), each with its own primary text and open checker, and a validator's pass covers only what it implements (Photon aims to validate IMPs for listed applications; libdcp and ClairMeta check DCP structure; BagIt 'valid' only matches manifest checksums). ClairMeta profiles can downgrade or silence checks, so record the profile with any pass. No single tool spans the chain.
• articleOverview: when a story written in ink, Yarn Spinner, Twine or articy goes into a game build, what does each step (compile, import, localise, save, record) keep and drop?
  Synthesis supported by reviewed findings: what ships differs from what writers edit. ink ships compiled JSON (comments dropped, tags kept), Yarn Spinner ships line IDs with text in string tables, Twine ships HTML whose specs define no save behaviour, and articy exports JSON with LocaIDs; save formats and compatibility belong to each runtime.
• articleWhen I record a playthrough of a story-driven game, which narrative-runtime behaviours follow the capture clock and which do not (typewriter text, randomness, audio)?
  Engines offer fixed-step capture (Unity captureDeltaTime; Godot Movie Maker with --fixed-fps, where visual output stays identical; recorders take engine audio rather than system output), but Unity's capture clock does not affect unscaled time. Yarn Spinner's letter typewriter measures elapsed scaled time (Time.timeAsDouble), so under Unity capture its reveal pace should follow the capture clock (inference, not run). ink seeds its shuffle randomness from the current millisecond when a story state starts and stores the seed in saves, so shuffled text can differ between recording runs unless the seed or state is fixed (inference). No source states a determinism guarantee for narrative engines during capture.
• articleIn an ISDCF Digital Cinema Naming Convention audio-type field, what do HI, VI (and VIN) mean, and where does the audio language go?
  In the ISDCF Digital Cinema Naming Convention, the Audio Type field marks accessibility audio as HI (Assisted Listening), VI (Audio Description) and SL (Sign Language), e.g. 51-HI-VI. No language is given for those tracks because it is normally the language already stated in the Audio Language field. VIN appears only as the channel label in the CPL MainSoundConfiguration, not as a naming token. ISDCF stresses that DCNC is a convention, not a standard.
• articleHow do I compute a tempo (or a tempo ramp) so that a musical downbeat lands on a given video frame, and what do DAW docs say about doing it?
  Partially verified: the curator re-read none of the cited sources; S8, S10, S9, S7 rest on the producer's pinned reading. Ardour's manual (at the pinned commit) says the preferred way to match tempo to existing material is to drag the beat/bar grid, that snapping a beat to a video frame makes a soundtrack 'punchy and synchronized to the sample', that audio-locked tempo and time-signature markers stay at their frame positions while music-locked ones move, that tempo ramps can be used in a video context for an accelerando by snapping to timecode frames, and that all fractional frame rates are fps x 1000/1001. The manual gives no formula; the arithmetic below is this worker's synthesis: convert the timecode to frames, divide by the exact frame rate to get seconds, then BPM = 60 x beats / seconds for a constant tempo. Worked example: a hit at 00:00:10:12 landing on beat 33 (32 beats after the anchor) is 252 frames = 10.5 s at 24 fps, so about 182.857 BPM; at 23.976 fps the same label is...
• articleHow did silent-film musicians fit music to picture timing in 1920, and what basic practices does the manual give a newcomer?
  Partially verified: the curator re-read none of the cited sources; S7 rests on the producer's pinned reading. Lang and West (1920) describe a workflow of a producer-supplied cue sheet (received about three days to a week before showing) listing numbered cues with minutes, title or description cues, tempo and suggested selections; the player selects music, times the numbers, the main theme and the improvised spaces, and changes music at scene boundaries. Speed of action sets tempo and lighting sets intensity; a flash-back keeps the music's continuity but raises speed and loudness; a climax should be synchronised with a named action (making the climax of a song coincide with the heroine fainting). They advise not to 'crowd the picture' and say a little silence is welcome. Rapee's 1924 Motion Picture Moods was not publicly readable (lending-only), so only this manual was used.
• articleWhat do current public Amazon, Apple and Disney delivery documents say about forced narratives, textless picture, and supplemental or alternate packages, and where do they differ?
  Partially verified: the curator re-read S17, S19, S20; S18, S21, S22 were not re-read by the curator and rest on the producer's pinned reading. Amazon has two delivery vocabularies: the Amazon MGM Studios manual uses non-subtitled picture plus separate FN and SDH-with/without-FN files and requires a fully textless master when 30% or more of the programme is texted; Prime Video Video Central (licensed content) asks for semi-textless picture (creative text allowed, no burnt-in subtitles) with FN as separate timed text for every dubbed language. Amazon's textless definition removes FN, text over picture and graphics text, which is not the same test as Apple's textless_master attribute (producer reading of Apple).
• articleWhat do Blackmagic's small public pages say about Resolve Voice Isolation's amount control, clip vs track scope, real-time vs render behaviour, and the defaults and channel limits of Dialogue Leveler and Dialogue Separator?
  Partially verified: the curator re-read none of the cited sources; S6, S8, S9, S5, S2, S4 rest on the producer's pinned reading. Mostly a scoped negative. The pages read document controls only for the Dialogue Leveler (waveform display, focus presets, three process options) and the Dialogue Separator (voice, background, ambience); Voice Isolation has no named control, and none of the pages or support descriptions states an amount value, defaults, mono/stereo/multichannel limits or a Studio-versus-free parameter difference. The wording 'track FX' and two Studio update notes (playback in 18.5.1, bounce sync in 18.6.3) are the only hints on scope and real-time versus offline behaviour.
• articleWhich of Resolve's AI dialogue tools (Voice Isolation, Dialogue Leveler, Dialogue Separator) arrived in which version, and do Blackmagic's small pages put them in Studio only or also in the free version?
  Partially verified: the curator re-read none of the cited sources; S5, S6, S8, S12, S1, S2, S11, S7, S15 rest on the producer's pinned reading. Blackmagic's own support listing dates the first Voice Isolation and Dialogue Leveler to Resolve 18.1 (11 Nov 2022) and every update note that mentions Voice Isolation is a Studio build; the Studio product page lists Voice Isolation and Dialogue Separator among Studio features (snapshots 2024-05-03 to 2025-10-09 and the live page on 2026-10-22). Dialogue Separator appears on the Resolve 19-branded What's New snapshot. No inspected page says in so many words that the free version lacks these tools, so Studio-only is supported by placement, not by an explicit exclusion; the Dialogue Leveler's edition is least clear.
• articleWhat are the elements of a POV structure that a shot planner must keep consistent, and what happens when one is changed?
  Partially verified: the curator re-read none of the cited sources; S3 rests on the producer's pinned reading. Branigan's chapter (German translation) decomposes the POV structure into six elements: a point in space, a glance, a temporal transition, a camera placed at that point, the object, and a character who perceives. For each element he gives film examples where altering the element creates ambiguity or a different reading: too many points (Marienbad), a glance with no clear target (Psycho tray), a repeated object without the glance (Ozu), a camera that is not at the point (Ozu's Bakushu corridor), a tracking shot that is too fast for its character, and a corpse with closed eyes. The decomposition is a descriptive analysis by one scholar, not a tested design rule.
• articleHow do I make it clear that a shot is a particular character's view, and what cues does the literature list?
  Partially verified: the curator re-read none of the cited sources; S3, S1 rest on the producer's pinned reading. Two openly readable sources list cues that attribute a shot to a character. Branigan's Element 2 gives indicators of a look (eye, head or body movement, a flashlight beam, a changed angle or distance, a camera move, speech, off-screen sound, music, shot duration). Ergo's footnotes add shot-internal cues for a POV shot with no glance shot (mask, onlooker-like camera movement, diegetic breathing, character-linked music) and note that framing can signal a character's attention. Both warn that a cut with no clear looker is ambiguous (Branigan's Psycho tray example).
• articleWhat is the difference between a POV shot, a glance shot plus object shot (sight link) and an eyeline match, and how do I classify a shot pair?
  Partially verified: the curator re-read none of the cited sources; S1, S3 rest on the producer's pinned reading. Cumming, Greenberg, Kaiser and Kelly (Ergo, open access, 2021) separate two film conventions for showing that a character sees: POV (one shot whose camera view is read as the character's) and sight link (a glance shot followed or preceded by an object shot of what is looked at). They say the two can occur independently, and describe eyeline match as a further mirrored-camera-setup rule. Branigan, in a published German translation of his 1984 book chapter, instead treats the POV shot as a subcategory of the eyeline match, so the vocabulary differs between sources and should be pinned before use.
• articleWhat can sound do narratively beyond illustrating the picture: how do silence, contrast and recurring sound motifs work, and what do the sources say about using them sparingly?
  Corrected 2026-10-23 - see C3-B622-01; the original statements below are kept for history and are superseded where the correction says so. For a newcomer the sources give three simple, source-named tools. Roles: direct narrative (cueing events), subliminal (emotional colouring) and grammatical (continuity across cuts). Silence: Murch says he used it rarely, citing the end of The Godfather Part II (drop to atmosphere, then nothing) and Welles's held silence in a 1938 radio drama; Weis adds that in dense tracks absence stands out. Motifs: a sound effect tied to a character or idea that prepares the audience for their appearance; Murch's character 'coronas'. All are practitioner or textbook assertions; none comes with audience testing.
• articleWhy do AI-generated clips show banding in skies and fog, and when should I use FFmpeg gradfun versus deband versus a 10-bit master?
  Problem. Smooth gradients (sky, fog, walls, vignettes) in generated clips show contour bands, usually worse after delivery encoding. Conditions. 8-bit delivery. BT.709 8-bit coding assigns black 16 and nominal peak 235 (219 steps); 10-bit assigns 64 and 940 (876 steps), so 10-bit has four times the steps over the same range (arithmetic from the table). Open tools quantise float frames to uint8 before encoding (see P-L1-4-03). Method. (1) Decide where the bands enter: at the 8-bit cast/export, or at lossy compression. (2) For a playback-only copy, FFmpeg gradfun=strength[:radius]: strength range .51 to 64 (default 1.2) is both the maximum change per pixel and the flat-region threshold; radius 8 to 32 (default 16); a larger radius gives smoother gradients but protects pixels near detail. The FFmpeg doc says it is designed for playback only and must not be used before lossy compression because compression loses the dither and brings the bands back. (3) deband filter: replaces banded pi...
• articleWhat quality criteria, numeric thresholds and reporting duties do Ofcom, CRTC, ACMA and the FCC publish for captions, and which of them set numeric accuracy or latency values?
  CRTC 2019-308 sets a live-caption lag limit of six seconds averaged over the program and a NER accuracy rate of 98 for English-language live programming (with a transition period from 1 September 2019 to 29 February 2020) and annual reports by 30 November; it is a mandatory numeric standard, unlike ACMA's observed 6-second level per producer.
• articleWhat loudness, peak, sample-rate and stem requirements does Netflix's publicly hosted Sound Mix Specification v1.4 state, and does a Non-Branded spec page add any?
  Netflix Sound Mix Specifications & Best Practices v1.4 (change log 2021-11-09; Internet Archive copy) states -27 LKFS +/- 2 LU dialog-gated, peaks not above -2 dB true peak, measured over the full programme per BS.1770-1, with a program-gated fallback of -24 LKFS +/- 2 LU (BS.1770-3) when near-field 5.1 dialog is under 15%. This curl-fetched archive is the preferred pin for the three-route cluster.
• articleDoes the official Unity registry confirm com.unity.recorder 5.1.7, and does the mirror's package.json at df67fd77 match the registry metadata for that version?
  Corrected 2026-10-23 - see C3-B598-03; the original statements below are kept for history and are superseded where the correction says so. The official UPM registry JSON (GET, observed 2026-10-22T12:21Z) lists com.unity.recorder 5.1.7 as dist-tags.latest, with registry time 2026-08-03T10:58:47.510Z and dist.shasum 0b23bb7a1fb4a062b8640ef5b1d174ca9b070467 (SHA-1 hex; no integrity/sha512 field in any of 42 versions). The mirror's package.json at commit df67fd77 equals the registry's 5.1.7 entry on every shared metadata field (name, displayName, version, unity, dependencies, description, keywords, samples, documentationUrl, _upm.changelog); the mirror file adds repository, upmCi and relatedPackages, the registry adds dist. This corroborates that the mirror's metadata is consistent with Unity's registry, not that its .cs bytes equal the archive.
• articleWhen an edit timeline moves between OTIO, CMX3600 EDL, AAF, ALE and FCP XML, what do the adapters at pinned versions preserve (tracks, names, reel, timecode, markers, CDL) and what do they drop or reject?
  At the pinned versions: the CMX3600 EDL adapter writes exactly one enabled video track and at most two audio tracks (otherwise NotSupportedError), keeps markers, transitions, linear speed and CDL (ASC comments), assumes 24 fps on read unless told, ignores FCM lines and does not keep AX reels; the AAF adapter round-trips multiple tracks, nesting, markers and transitions but not effects, CDL or image sequences (linear speed read only); the ALE adapter maps Source File to a media reference and CDL/ASC_SOP columns into cdl metadata; the FCP7 XML adapter keeps tracks, markers and nesting but drops transitions, effects, speed, CDL and image sequences. All from READMEs and code, not executed.
• articleAt DI and delivery, what do AMF/ACES and the IMF Application 2E standard say about reproducing on-set colour intent, and what is not carried?
  AMF lets finishing automatically recreate the on-set or dailies viewing reference, possibly with a different ODT for the better grading display, but holds no timeline data. IMF Application #2E fixes the finished image's colorimetry system (COLOR.1-COLOR.8) and allows optional all-or-none ST 2086 mastering-display items for COLOR.3/5/6/7/8, with nothing assumed when absent; its text names no ACES, timecode or CDL. AAF AS-01 defines tape names and timecode tracks but no CDL/ASC/LUT objects. So none of the documents read states that on-set colour intent itself travels into an IMF package.
• articleDoes Unity Recorder 5.1.7's Movie Recorder tag colour or tonemap video, and what colour space does ProRes output declare?
  The Unity Recorder ProRes encoder hard-codes the Rec.709 colour definition; Rec.2020, PQ and HLG values exist only as commented-out enum entries, so engine ProRes output cannot be tagged for HDR or wide gamut. Whether written files carry tags was not observed.
• articleDoes the Unity registry record for com.unity.recorder carry any integrity (sha512) field in its 42 versions, or only dist.shasum?
  Correction to C3-B222-G68-01 (nature: overstated absence claim). Original: no integrity/sha512 field in any of 42 versions. Audit result (registry JSON fetched 2026-10-23): version 5.1.7 still has only dist.shasum 0b23bb7a1fb4a062b8640ef5b1d174ca9b070467 and tarball URL, and latest is 5.1.7, as stated. But 7 of the 42 version entries (4.0.0, 4.0.0-pre.5, 4.0.0-pre.4, 4.0.0-pre.2, 3.0.3, 3.0.2, 2.5.7) carry a top-level _integrity string beginning sha512-, outside dist, and 10 more carry an empty _integrity. So the accurate statement is: no dist.integrity field in any version, no _integrity on 5.1.7, but historic entries expose leftover npm-style _integrity values. Treat them as publisher-supplied metadata of unknown reliability. Version/date: 2026-10-23.
• articleAgentic assistants driving Blender, DaVinci Resolve and After Effects for AI film pre-production and editing (GPT-6 Astra, Sept 2026)
  Creator-reported: statements attributed to the creator(s) come from discovery's reading of auto-caption transcript excerpts; the curator checked the video metadata (title, date, length) and any cited documentation pages, not the spoken claims. Nothing was tested; promotional or sponsored framing applies where stated. Dan Kieft (Higgsfield-sponsored, 2026-09-23) on OpenAI's GPT-6 Astra (launched early Sept 2026 per secondary news listings R4/R5, emphasising computer use; primary OpenAI page not read). Uses: (1) ChatGPT + Blender MCP builds a 3D set (a bar) from a prompt and references; he places cameras for shot angles, renders previs frames, has GPT Image 2.5 make them photoreal, then uses them as Seedance 2.5 references - more control than describing shots in text; Astra also built a web viewer of the set so non-Blender teammates can orbit/walk it. (2) Recreating rooms from photos to plan a studio layout. (3) Thumbnail ideation with own portrait, channel examples and inspiration, a...
• articleBWF MetaEdit (5b7f3d20) validation help says bext Version must be 0 or 1, while its bext parser reads the BWF v2 loudness fields when Version >= 2; the help text lags the...
  BWF MetaEdit (5b7f3d20) validation help says bext Version must be 0 or 1, while its bext parser reads the BWF v2 loudness fields when Version >= 2; the help text lags the code.
• articleSmall production tips from editor-integrated workflows: "no music, only sound effects", layered timelines, and AI dialogue re-language with lip sync
  Creator-reported: statements attributed to the creator(s) come from discovery's reading of auto-caption transcript excerpts; the curator checked the video metadata (title, date, length) and any cited documentation pages, not the spoken claims. Nothing was tested; promotional or sponsored framing applies where stated. From CapCut PC (2026-07-04) and Lumina (2026-08-18) videos: (1) end video prompts with "No music, only sound effects" so generated SFX are usable while you keep control of the score in the edit; (2) layer in a multi-track editor - generated clips on the main track, generated stills as overlays, music/sound design below, captions/motion graphics on top; simple keyframed fades between generated clips; (3) prompt vocabulary he uses for animated frames: ambient shadows, cinematic close-up portrait, shallow depth of field, emotional storytelling, photoreal CGI, highly detailed animated film frame; (4) Seedance 2.5 video editing on Lumina can change a clip's dialogue language...
• articleBuilding a fictional brand campaign end to end in an editor (CapCut PC, Sep-Oct 2026): logo, products, model/product sheets, 30 s generation, scene split and chat-based edits
  Creator-reported: statements attributed to the creator(s) come from discovery's reading of auto-caption transcript excerpts; the curator checked the video metadata (title, date, length) and any cited documentation pages, not the spoken claims. Nothing was tested; promotional or sponsored framing applies where stated. Mikkel Lassalle CapCut videos (2026-09-22, 2026-10-15) plus an Artlist Seedance 2.5 video (2026-08-11). Pipeline: invent the brand and make a logo with GPT Image 2 (his preference for logos and character sheets); develop products and style frames in a design workspace with Nano Banana Pro (his preference for cinematic frames); create one character sheet for the model and one for the product and tag both in the prompt; add camera/style cues (e.g. "ARRI Alexa 35 aesthetic"); generate up to 30 s with Seedance 2.5 (still capped at 720p in August per him; start/end frames also available); import into the editor, use "split scenes" to auto-cut the generation into shots, reord...
• articlepyaaf2 (08dcc3df, v1.7.1-era) embeds WAV audio only for PCM/extensible-PCM at 16 or 24 bit (32-bit integer or float raises wave.Error) and audio.py carries no bext/iXML/TimeReference handling; code is...
  pyaaf2 (08dcc3df, v1.7.1-era) embeds WAV audio only for PCM/extensible-PCM at 16 or 24 bit (32-bit integer or float raises wave.Error) and audio.py carries no bext/iXML/TimeReference handling; code is MIT.
• articleOpen-weight alternatives for upscaling AI video (SeedVR2, FlashVSR+) run in ComfyUI on a 24 GB GPU; generative upscalers trade fidelity for perceived sharpness, so check faces/text after upscaling
  Self-hosted counterpart to commercial finishing tools (C3-B479-01). SeedVR2 (ByteDance Seed): 3B and 7B weights on Hugging Face under apache-2.0; Comfy-Org hosts a repackaged set in fp16, fp8, int8, mxfp8 and nvfp4 precisions (652k downloads) and the community numz ComfyUI wrapper has ~2.9k stars (R1, R5). FlashVSR+ (13 Oct 2026, R2): hybrid local/sparse-global attention gives up to 2x DiT speed and 45% lower peak memory, "enabling spatially untiled 4K VSR on a single 24GB RTX 4090", with reward-weighted distillation for user-preferred one-step output; code, models and training data released (code Apache-2.0; ComfyUI wrappers exist, one GPL-3.0) (R2, R4). A zero-shot pipeline from pretrained parts reaches ~32 fps at 720p on one RTX 4090 but explicitly trades "reconstruction fidelity for strong no-reference perceptual quality" and struggles with hard motion (R3). Practical: (1) a 24 GB card can now upscale generated clips to 4K locally without tiling seams; (2) generative VSR invents...
• articleFinishing AI-generated video for professional delivery: generate at 720p, upscale, convert 8-bit to 10-bit before grading, and use creative upscalers only for stylised shots
  Two 2026 production accounts (vendor-published) describe the same finishing chain. Primordial Soup (Darren Aronofsky's AI studio) on TIME Studios' YouTube series "On This Day... 1776" (R1): Starlight Precise 2.5 to upscale/refine generated footage across the series; Hyperion 2.5 converted 8-bit generated sources to 10-bit ProRes before a masked ghost grade in DaVinci Resolve because "8-bit GenAI sources do not hold up well under intensive color grading"; Hyperion also reduced visible banding in an extreme close-up; Astra 2 (creative video-to-video upscaler that adds generative detail) used only for an anime-styled episode to sharpen linework. Production mixed SAG actors and performance capture with GenAI animation and conventional edit/sound/colour. Verena Puhm's "Nobody Dies on Mars" (Future Vision XPRIZE 2026 second place, $100,000) (R2): video mostly made with Seedance, "often generated at 720p", then upscaled to 4K with Starlight Precise 2.6 for theatrical presentation; Premiere...
• articleYouTube rules (R1): chapters split a video into sections with individual previews and may appear in transcripts. Manual chapters: in the description list timestamps and titles, first must be 00:00, at least three in ascending order, minimum chapter length 10 seconds; manual chapters override...
  YouTube rules (R1): chapters split a video into sections with individual previews and may appear in transcripts. Manual chapters: in the description list timestamps and titles, first must be 00:00, at least three in ascending order, minimum chapter length 10 seconds; manual chapters override automatic ones. Automatic chapters are on by default for new uploads ("Allow automatic chapters", per video, in bulk, or via Upload defaults > Advanced settings) but not all videos are eligible; chapters are unavailable if the channel has active strikes or the content may be inappropriate for some viewers; channels without access must apply for Advanced features. Google Search (R2): key moments let searchers jump to segments; Google tries to detect segments automatically but "will prioritize key moments set by you, either through structured data or the YouTube description". For YouTube-hosted video, the description timestamps are the mechanism (all Search languages). For self-hosted or embedded ...
• articleWhat does ClairMeta's CPL and AssetMap check code compute, and how severe is each result under the default profile?
  ClairMeta's CPL checker (23 checks: 14 CPL-level, 9 per asset) mostly tests what the CPL declares (title text, UUID formats, reel entry points and durations, cross-reel coherence of attributes such as SoundLanguage) or compares CPL metadata with MXF probe data; its encrypted-asset hash check only requires a Hash element, without recomputing it. The AssetMap checker (9 checks) is where files on disk are touched: existence, path syntax and declared Length versus actual file size. Checks default to ERROR unless the profile lists them (e.g. title/annotation matches are WARNING).

More