Editing and finishing

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

• article1916 practice plus a proposal: what check can an agent run on a scene list to decide whether and how to use a cut-back or flash, using Sargent's Chapter XXXIX?
  Agent check, labelled 1916 practice plus a proposal. Ten steps from Sargent (Ch. XXXIX) are listed as a checklist: name the job; weigh leader and close-up; choose anticipation or surprise; choose the cut-to scene (contrast or related); write numbered returns; keep inserts as flashes; leave extra cutting to the director; apply a stretch test; vary three-way order; remove returns with no reason. The stretch test and the proposed counting of returns that add no new fact are the agent's proposal, not Sargent's test; a human-audience experiment is outlined but not run.
• articleHow do Sargent's Chapter XXXIX claims about the cut-back compare, by candidate ID only, with the early-manual flashback and cut-back rows (C3-B039-S11), the cross-cutting and last-minute-rescue rows (C3-B160-S33) and Münsterberg on the cut-back (C3-B187-S41)?
  Comparison (synthesis; the other batches' rows are relayed, not re-checked). Münsterberg (C3-B187-S41-01) defines the cut-back as any return to an earlier scene and maps it to remembering; Sargent defines it by three jobs and by script form, and in this chapter ties it to the audience remembering within present-time action, not to character memory. On suspense Sargent agrees with the relayed 1913-1919 manuals (C3-B160-S33-02, C3-B039-S11-05) and goes further on how a long alternation fails and is repaired. Münsterberg warns of 'nervous jerking' from many changes (C3-B187-S41-03); Sargent warns of attenuation and laughter, with no count. One relayed quotation of Sargent (C3-B039-S11-05 E9) differs from his own wording here.
• articleWhat misuses and limits of the cut-back and flash does Sargent (1916, Ch. XXXIX) name, how do they bear on suspense and clarity, and what does the chapter not say?
  1916 practice: Sargent names these cautions: do not over-use the cut-back (the author writes cut-backs where good sense puts them and leaves extremes to the director); suspense carried too far snaps (his stretched rescue draws laughter); not all plays can be cut back, and cutting without reason can spoil the play; a flash should not be a six-frame fragment or a title held for seconds. On clarity he claims the cut-back keeps parts of the action from being forgotten, and warns that the surprise version needs the withheld figure established in the last scene; the form of reference is flexible if the author's intent is clear. Bounded negatives: the chapter gives no number or ratio for how often to cut back, and does not use the words confusing or misleading.
• articleWhat does Sargent (1916, Ch. XXXIX) use the cut-back for beyond suspense: contrast, information and comedy, and what does he claim it does for the audience's grasp of the whole action?
  1916 practice: for contrast, he cuts from a killing to a scene that shows the girl is not worth the deed; the contrast is stronger if the cut scene reproduces an earlier scene the audience remembers, and the two scripts refer to each other. For information, a cut-back to a sickroom in the middle of a funny dash for a train restores the stakes: the 'reminding cut-in' removes the humour. In comedy the cut-back seeks contrast more than suspense, as in a three-strand sequence (Bill, Grace, Jim) where each strand makes the others funnier and a laugh arises from anticipation. His general advice is that each section should gain in contrast with the other half, and scenes should help each other as bricks held by mortar.
• articleHow does Sargent (1916, Ch. XXXIX) say alternating cut-backs build suspense, how far can they be stretched, and what does he do to keep a long alternation from collapsing?
  1916 practice: Sargent says cut-backs make suspense by delaying the climax and by suggesting victory and defeat in alternation; one scene alone gives only a wait for the inevitable, and a rescue scene adds suspense. He then shows three versions of one rescue: a three-scene version (short-lived suspense), a stretched 23-scene version in which the ride is repeated until an adult audience is 'laughing heartily', and a version of the same number of scenes that adds plot incident (wrong trail, loosened saddle girth, a fight) and keeps the suspense. His rule: suspense is effective only if not carried too far, like a stretched rubber band, so add new factors while you stretch and stop when you cannot.
• articleWhen does Sargent (1916, Ch. XXXIX) cut back to bridge a break or shorten a long scene instead of using a leader or a close-up, and how does he compress a long fight?
  1916 practice: Sargent offers the cut-back as the way out of a set where nothing more can happen (the actress in the dressing room), as a replacement for a break leader, and as an alternative to a close-up for a long speech, where the cut-back's contrast 'does not form a rule' and may be weaker. Where tension is high a leader would break it, so a cut-back is preferable. For a violent scene he cuts to related action or a contrast because suggestion draws less objection than the physical action. To compress a fight he alternates it with an invented progression (a man running for the police): about twenty feet of fight suggests a half-hour struggle in under a minute. The cut-back also lets the writer choose anticipation or surprise.
• articleHow is a cut-back or flash written into a 1916 photoplay script: numbering, the 'Back to No.' and 'as in No.' wording, 'Flash of fight' entries, and where is the form flexible?
  1916 practice: in Sargent's examples every cut-back is its own numbered scene entry: number, place, then the action joined by dashes. A return to an earlier scene is written 'Back to No. 35' or 'as in No. 45'; in his shop-fight sequence the brief fight inserts are written 'Back to No. 43 -- Flash of fight.' There is no timing mark in these entries. He says the scene-reference rules of Chapter XXX are general practice, not rigid: when the author's intent is clear, any form is permissible and no script is rejected for writing 'Same as' instead of 'Back to'. Two scenes can also cross-refer so the director may play either first.
• articleWhat do 'cut-back' and 'flash' mean in Sargent's 1916 photoplay manual (Chapter XXXIX), how long is a flash supposed to be, and what jobs does he give the cut-back?
  1916 practice: Sargent opens the chapter by giving the cut-back three jobs: bridge awkward gaps in the action, heighten a situation through contrasting action, and raise suspense by delaying the crisis or climax; in the second and third jobs it is 'merely a flash'. A flash is a very brief scene, properly about three seconds, though in practice it may run much longer or shorter; he calls a six-frame (three-eighths of a second) scene a monstrosity, and no worse than a flashed letter held on screen ten or fifteen seconds. In this chapter 'flash' names a duration of an inserted scene, not a past or imagined moment (bounded: the chapter's text only).
• articleWhich checks does Sargent (1916, Ch. XLIV) give for keeping time, place and costume continuous across scenes, which failure modes does he name, and does he cover props?
  1916 practice (Sargent, ch. XLIV paras 8-26). Time: tell the audience when the action jumps (by inference or statement); a definite lapse needs a time leader; where time and fact are unimportant, break with another scene, and prefer a fact leader to a time leader. Place: leaving one room and entering another implies adjoining rooms; different floors need a stair; distant places need established distance and an intervening leader or scene; a person away from his own precincts must be explained or pre-established. Character: a costume change needs intervening action that allows the time. Two scenes in one setting run together read as one scene. Entrances: do not leave a needed character standing in the previous scene or show him already on. Props, wardrobe and make-up: not in these chapters (bounded scan, see findings). The numbered rules are Sargent's 'general guide, not infallible rules'.
• articleWhat does 'continuity' mean in Sargent's 1916 manual (Ch. XLIV), and what are the main ways he says a script breaks it?
  1916 practice (Sargent, ch. XLIV). 'Continuity' means the easy, orderly progress of the action, and as a noun it also names the written plot of action itself. He gives three aspects: the story moves steadily forward in chronological order; scenes are in proper time order with jumps made known by inference or statement; and the character stays continuous (dress and presence from scene to scene). The main break is 'visioning' back: every time leader, fact leader or vision costs attention. He allows it only when the gain outweighs the interruption. A second source of breaks is condensation in the cutting room. His river, steam-engine and train-boarding passages are analogies. This candidate defines the terms; rule-by-rule checks are in C3-B303-S108-05.
• articleWhat does Phillips (1914) require for entrances and exits between scenes, what does he mean by the 'scene principle' (reflective power) and by 'every camera shift is a new scene', and what reasons does he give?
  1914 practice (Phillips): a character who appears in the next scene is shown leaving the present one and arriving in the next, without the steps in between (unless something happens en route); an intervening scene without the character lets exit and entrance be omitted. The new scene is shown first and the character met at the door, optionally after a fragment of action. The scene principle is reflective power: each scene reacts to the previous and sets off the next toward the climax. A new scene is counted at every camera shift. Reasons given are natural movement, naturalness, illusion and (for identity) the speed of scene flow.
• articleThe chapter heading lists 'Perpetual Motion': what rule does the chapter text give under that name, and which nearby rules cover continuous forward action and pace?
  Negative result bounded to the pinned text: the phrase 'Perpetual Motion' occurs only in the contents page and the chapter's sub-heading line; the chapter body has no paragraph on it. The nearest rules are to begin at the beginning and always go forward (turning back only as a rare exception), to use short quick scenes and many returns in fast plays, and to skip the steps between scenes. The closest statement of continuous action is outside the chapter (Part II ch. IV: no pause in the plot, perfect continuity of time). Part III ch. V warns that perpetual short scenes harm harmony. Label: 1914 practice; the reading of the heading is interpretation.
• articleWhat did a microbudget director say happens when you plan to shoot minimal coverage and post-production later demands changes to a scene shot as one take?
  In a first-person MovieMaker piece (published 8 December 2014, updated 31 January 2023), director William Dickerson says he does not shoot coverage for its own sake. On Don't Look Back (14-day shoot) a scene he shot as one continuous POV take drew a producer demand in post to halve its length, jump time and adjust performance, which a oner cannot support; he reports solving it by reframing the shot as looking through a 3D camera's viewfinder so cuts could be motivated. It is one director's self-report and does not show how common the problem is.
• articleWhich Media Composer EDL Manager templates lift the 8-character reel limit, and where does it take the reel name from, according to an Avid document newer than the 2013 File-Based Workflows Guide?
  Zero-fetch re-read of a cycle-2 pin (C2-B89-U2 bibliography S4, listed there but not used in its claims). Avid's 2014 Media Composer white paper says EDL Manager offers File_16 and File_32 templates that lift CMX3600's 8-character source-reel limit (and raise the event limit), names Tape then Source File as the default reel source, and lists Labroll, Camroll and SoundRoll as alternative source columns. It is dated 2014, one year after the 2013 guide, so it does not establish current (2025/2026) Media Composer behaviour; no current EDL Manager page was fetched (storage stop) and the 2025 Editing Guide in the catalogue was not read for this.
• articleWhen I export a CMX 3600 EDL from Premiere Pro, what does Adobe's help page say about the clip-name comment and the 32-character names option, and does the page still read the same today?
  Re-pin of the curator-blocked Adobe page (C3-C-FEEDBACK-0065 item 2; cycle-2 C2-B89-U2-01 evidence E4/E5 not repeated). One plain GET on 2026-10-22T13:23:24Z returned 200. The page (footer 'Last updated on Jan 7, 2026') says each EDL clip gets a comment with its name (source clip name or timeline name, toggled in the Timeline panel) and that the 32-character names option in the EDL Export Settings (CMX 3600) dialog should be ticked when clip or tape names exceed eight characters. The literal phrase 'name comment' is not on the page; the page says 'a comment with its name'. Text is identical to the cycle-2 save of 2026-10-21.
• articleWhat do open-access empirical studies report about eyeline matches and editing-linked gaze that bear on shot/reverse-shot dialogue, beyond the 180-degree study already in cycle 2?
  Thin result. The one on-topic open item found is a conference abstract (Ildirar Kirbas and Smith, ICIS 2018) on whether 12-month-olds and adults follow a head turn across an eyeline-match cut: adults followed gaze in edited and unedited versions; infant data were preliminary and suggested less success across edits. Bruckert et al. (2021) report editing/scanpath links in movie clips (abstract only). Neither tests two-person dialogue coverage. The 180-degree experiments are cycle-2 C2-B01-A-06 and are not repeated.
• articleWhere should cuts fall in a dialogue scene (line boundaries, reaction, overlap) and how are rolled edits and split edits used to create cutting points?
  Only one inspected source describes dialogue cutting points in procedure form: the Wikibooks Movie Making Manual 'Scene Editing' page (revid 4341818, community text). It says a rough cut that follows each speaker looks like a tennis match, and recommends locking the dialogue audio and rolling the picture edit forward to show the first speaker's reaction or backward to show the next speaker's anticipation (the L cut / J cut), with the gap between lines the only adjustable audio element. Leake et al. place one cut decision per dialogue line. The OER textbooks give no cutting-point rule; early manuals time a title to the utterance.
• articleFor a two-person dialogue scene, what are a master shot and coverage, and which shot types do beginner open textbooks give for covering a conversation?
  Two CC BY-NC-SA 4.0 introductory textbooks (LMU's No-Nonsense Filmmaking, 2025; Reich, Exploring Movie Construction and Production) give the same basic workflow: shoot a master wide enough to show all relevant action, fixing geography, screen direction, blocking and lighting, then repeat the same action as coverage from other angles and sizes, and let the editor arrange the shots. For conversations Reich lists two-shot, speaker single followed by listener reaction, medium and close-up, and over-the-shoulder; a Wikibooks page calls over-the-shoulder the typical conversation set-up. None gives per-beat rules, counts or timings.
• articleWhat do the official 5.1.7 Movie Recorder pages state about ProRes, colour and tonemapping, and which part of CA-B309's "ProRes hard-codes Rec. 709" is only in mirror source?
  The official Movie Recorder page lists six ProRes codecs, says the ProRes encoder supports Stereo only, does not support variable frame rate, and is unsupported on Linux and Windows Arm64. It contains no colour, tonemapping, Rec. 709, Rec. 2020, PQ or HLG statement (0 hits in the whole 15,316-character page; 0 also in the linear-sRGB page for 709/2020/HLG/PQ and 0 in the changelog apart from dates). CA-B309's "Movie docs contain no colour-tag or tonemapping setting" is corroborated as an absence; "ProRes encoder hard-codes Rec. 709 with Rec. 2020/PQ/HLG commented out" is code-only (ProResEncoder.cs in the mirror) and cannot be byte-checked without the archive.
• articleWhich of CA-B309's Image Recorder colour-space statements (PNG/JPEG sRGB, EXR linear unclamped, tonemapping, dithering) do the official 5.1.7 pages state, reword, omit or contradict?
  Official pages state the conditions for the Linear, sRGB (unclamped) option exactly as CA-B309 summarises them: HDRP project, Source not Game View, EXR format. They also tell you to disable Tonemapping and Dithering to get unclamped values, and say the Recorder encodes EXR in 16 bits. Not stated officially: that PNG/JPEG are "forced" to sRGB (only implied by the EXR-only condition), any default for Color Space, the internal "HDR frame capture possible" test, and any statement that the Recorder embeds or omits colour tags. The two official pages disagree on UI paths for the same step (HDRP Default Settings vs HDRP Global Settings; Dithering under General vs Rendering).
• articleWhat does Unity's own documentation say about the Audio Recorder's sample rate and bit depth, and which part of CA-B309's audio claim rests only on mirror source code?
  Official Recorder 5.1.7 docs state: WAV is the only Audio Recorder format, only Mono or Stereo is supported (from Project Settings > Audio > Default Speaker Mode), and the audio goes to the Recorder rather than the system output. They state no sample rate, bit depth or sample format anywhere in the five official pages read (0 hits for sample rate, Hz, bit depth, float, 32-bit). So CA-B309's "WAV header rate = AudioSettings.outputSampleRate at Stop(), 32-bit IEEE float" is absent from Unity's documentation and rests on AudioRecorder.cs from the mirror; the "no rate/bit-depth property" and "mono or stereo only" parts are corroborated. The mirror's RecorderAudio.md equals the official page word for word.
• articleWhat sync or timing tolerance, picture-reference rule and QC check do the Netflix Live Action, Animation, 5.1 Mix Room and Secondary Audio pages (and the delivery spec the last one points to) state for dubbed dialogue, and what is absent?
  No numeric sync tolerance for dubbed dialogue (frames or milliseconds) appears in the four assigned pages. The sync statements are qualitative or about equipment: the 5.1 room page requires picture displays and DAWs to be in frame-accurate sync (four named causes of drift); the Animation page asks for frame-accurate futz edits, clips "in sync", no time-stretch artifacts, 24 fps timecode (or as provided) and a programme start of 00:00:00:00 or the proxy. The archived delivery-spec page (version 5.1, 2024-08-10) adds that all audio must sync to final picture including 1 second of black either side, no extra leader, and measurable levels (-27 LKFS +/- 2 LU dialogue-gated; -2 dBFS true peak). Its only time tolerance, half a second, is for subtitle files, not audio. QC criteria are not listed on the four pages beyond rejection for tonality differences.
• articleHow does an open head-tracked binaural rendering specification (AOMedia IAMF) express head-locked versus world-locked rendering and reverberant filter profiles, and does it cite or encode the externalization, room-acoustics or latency evidence?
  The AOMedia IAMF specification at commit 55683fae00e541cd4f0849918f19af0e04bc629c lets an element be rendered head-locked or world-locked when head tracking is enabled, and signals a binaural filter profile of AMBIENT, DIRECT or REVERBERANT. In the text searched (whole index.bs, whitespace-collapsed), the words externalization, HRTF, BRIR and latency do not occur and the profiles carry no stated acoustic parameters, so the specification names the switches that the psychoacoustic evidence is about without citing it or giving values. The mapping to the evidence (world-locked rendering ~ source fixed in the world; REVERBERANT profile ~ reverberant versus anechoic) is a synthesis.
• articleWhat exactly does Münsterberg claim about parallel action, forward glances/imagination and spectator versus character emotion, what limits does he put on those claims, and which later items in the catalogue touch them?
  For parallel action Münsterberg claims the spectator does not experience intercut scenes as successive ('omnipresence', a chord), yet he himself notes psychologists dispute whether attention divides, and warns that too many changes (170 in ten minutes in one Carmen) produce 'nervous jerking'. For forward glances he claims film can act as imagination acts, and for emotion he separates feelings that mirror the character's from feelings that differ (fear for the unaware child), adding that makers had hardly used the second kind. Later items located touch these only at the edges: cross-cut shots marked as new events in one clip, a suspense model that separates felt from perceived tension, and Kuleshov-type context effects on rated valence. No located item tests flash-forward reception. All are 1916 theory versus second-hand adjacent records.
• articleHas later empirical work in the catalogue or cycle-3 batches tested Münsterberg's claims that the close-up depicts the viewer's attention and the cut-back the viewer's memory?
  No catalogue or cycle-3 item located by c3dup tests the two mappings directly. Near neighbours measure different endpoints: edit detection (the JEMR 2008 edit-blindness study, 7 participants), event-boundary marking (Zacks 2010; Magliano and Zacks 2011), and comprehension/load of flashbacks versus chronological order (Sevenants and d'Ydewalle 2011, n 30 and 8). Smith's attentional theory of continuity shares Münsterberg's attention emphasis but is itself a theory with cited/illustrative gaze evidence. Münsterberg's mappings therefore remain 1916 theory; related findings are adjacent, small and mostly single-film. All cross-references are second-hand records, not re-read papers.
• articleIn Münsterberg's 1916 book The Photoplay, which mental act does each film technique (close-up, cut-back, forward glance, parallel scenes, emotional setting) stand for, and where exactly does he say so?
  Münsterberg (1916, a psychologist's study, not an experiment on audiences) pairs film devices with the spectator's mental acts: the close-up 'objectifies' attention, the cut-back remembering, forward glances expectation/imagination, intertwined scenes the mind's divided interest ('omnipresence'), and scenery shaped to echo emotion. His summary principle is that film overcomes space, time and causality and follows attention, memory, imagination and emotion instead. These are 1916 theory statements, each locatable by line in the pinned text. His own vocabulary is close-up, cut-back, cut off; he never writes 'flash-forward' or 'cross-cutting'.
• articleWhat defects or hardware/format limits for Resolve Voice Isolation do Blackmagic's own update notes mention, and which versions do they belong to?
  Blackmagic's support-listing notes mention three Voice Isolation fixes, all in Studio builds: short audio clips (18.1.1, 23 Nov 2022), playback on energy-efficient CPU/GPU systems (18.5.1, 14 Aug 2023) and audio sync when bouncing (18.6.3, 14 Nov 2023). The notes say 'improves' and do not describe the earlier behaviour or give thresholds, so what exactly went wrong in earlier builds is unknown. No later (19, 20, 21) update note in the listing mentions voice isolation.
• articleIs there an openly readable shot count for Griffith's The Lonely Villa (1909), and do public-domain manuals or open scholarship give shot counts for last-minute rescue cutting?
  One openly readable count was found: the Cinemetrics database (submitted by Yuri Tsivian, 2007) gives 54 shots, running time 10:47.5 at 17 fps, ASL 12.0 s for The Lonely Villa. The saved page has no per-shot data. C3-B160-S33 already records manual passages and Bordwell's sentence tying accelerated deadline crosscutting to The Lonely Villa; none of those recorded passages gives a shot count. Further leads from a search engine (not fetched, condensed): Brewster on earlier rescue films (Pathe, A Narrow Escape 1908), a BAMPFA shot-analysis record; both unread.
• articleWhat checklist should an agent use when planning shots that carry character viewpoint, covering techniques, failure modes and evaluation?
  This is the worker's synthesis of the other candidates, each item traceable to the cited rows. It is a proposal for curation, not a validated procedure. Core items: decide objective, sight link or POV; anchor the looker; use glance-first for POV and verify with your own test; place the camera at the looker; keep time continuous; keep one looker at a time; plan re-establishing shots for long runs; and treat identification claims as untested.
• articleDoes showing the glance before or after the object shot change whether viewers attribute the shot to the character, and how strong is the evidence?
  Ergo reports an order effect: in a Mechanical Turk experiment with stimuli the authors made, the glance-first order gave a median POV-attribution probability of 0.74 and glance-second 0.37 in the baseline short-glance condition. Lengthening the glance from about 2 s to 5 s reduced the difference. The authors state the limit themselves: one clip per condition, so no general effect across examples. Their explanation, incremental viewpoint grounding, is a proposal. This is the only empirical attribution study found in the open sources fetched.
• articleWhen a split edit moves AAF to OTIO (and on to EDL, FCP7 XML or FCPXML), what survives as timing and what is lost as pairing between the audio and video clips, according to specs, adapter code and the OTIO linking issue?
  AAF and OTIO both place audio and video on separate tracks, so a split edit is just two tracks whose clip boundaries differ; the AAF Edit Protocol calls such tracks synchronized but independent. Neither OTIO nor its AAF, CMX3600 and FCP7 adapters (as read at pinned commits) has a construct for saying the two clips belong together: OTIO issue 343 has been open since 2018, the CMX adapter TODO admits linkage is lost, and the FCP7 adapter drops link elements on write. Users report Resolve and Premiere put link ids in OTIO metadata, which is unverified. Net by reading: timing offsets can travel, pairing does not.
• articleHow does FCPXML represent a split edit (audioStart / audioDuration), on which elements, in which units, and does the OTIO FCPX adapter read it?
  Apple's FCPXML DTD (1.7 archive and the 1.10 page) declares optional audioStart and audioDuration time attributes on clip, mc-clip, ref-clip, sync-clip and asset-clip and says they define J/L cuts (split edits) on composite A/V clips; times are rational seconds. Two FCPXML 1.11 files in a third-party Swift library contain the attribute pair on sync-clips, with audioStart equal to start and audioDuration shorter than duration. The OTIO FCPX adapter at c61839e1 never mentions either attribute and skips clip/sync-clip/mc-clip as items, so a split edit expressed this way is not read by it. The sign convention of audioStart relative to start and offset is not defined in the DTD text; a third-party importer treats any difference between audioStart/audioDuration and start/duration as a split edit and then follows the video timing.
• articleWhen a CMX3600 EDL with a SPLIT: line is read by the OTIO CMX3600 adapter or by pycmx, what happens to the delay value, and what is lost when OTIO writes an EDL back?
  By code reading (nothing executed): four open-source EDL readers all fail to apply the SPLIT delay. The OTIO CMX3600 adapter at 4b02a666 recognises a SPLIT line, checks that exactly one delay is named, then consumes the next two event lines and discards the delay value; the per-track start offset may still differ between the video and audio tracks because first-clip placement is stored in track source_range. pycmx at 49a536f0 parses SPLIT: into a StmtSplitEdit that its Event/Edit classes never expose, and the statement is stored with the previous event. The OTIO writer cannot emit SPLIT, AUD or combined V+A channel codes and writes only the first track. A Rust OTIO port documents that the delay is not modelled because the row times already carry it, and a web editor's importer warns the user that it is not applied. Applied by hand to a real single-spaced SPLIT line, pycmx's fixed columns would mis-read both type and delay. None of the inspected test files contains a split-edit case.
• articleI need to hand a J-cut or L-cut from one editing tool to another: which interchange format has a field for it, and what do the OTIO adapters do with that field?
  Each format expresses a split edit differently. A CMX3600-style EDL uses a SPLIT: header plus paired video and audio rows (one worked example). FCPXML names audioStart and audioDuration as the J/L-cut mechanism in Apple's DTD comment. AAF has no split object: audio and video are separate slots that its edit protocol calls synchronized but independent. OTIO has separate tracks and no clip-linking construct (its linking issue is open). Of the open-source EDL readers inspected, the OTIO adapter validates the split marker and discards its value, a Rust OTIO port documents not modelling it, and one importer warns that it is not applied; the FCPX adapter never reads audioStart/audioDuration. Treat all of this as code-reading, not execution.
• articleWhat does a split edit (audio and video edit points at different times) look like in a CMX3600-style EDL, and how do I read which track is delayed and by how much?
  A split edit in a CMX3600-style EDL is a "SPLIT: AUDIO DELAY= <timecode>" (or VIDEO DELAY) header followed by two rows with one event number, a picture row and a sound row. A 1995 vendor guide example (audio 6 frames late, video-only row plus A row) and a real Avid-style list found in a public repository (video 6 frames late in one block, audio 1 s 19 f late in another) agree on the structure: the delayed row is listed second and the header value equals the difference of the rows' record-in values (at 24 fps for the real list). A practitioner explainer says the header states which element is delayed and by how much. Header spacing differs between the two examples. No formal CMX or SMPTE field definition was read, so this rests on two examples, one explainer and parser code.
• articleDo Ofcom or EBU texts set any rule about colour-vision deficiency for broadcast graphics or subtitles, and what do they say about colour in subtitles?
  In the texts read in full, none contains colour-vision-deficiency wording: the Ofcom Broadcasting Code (January 2019 text), Ofcom's Guidelines on Providing Television and On-Demand Access Services (capture of 20 Nov 2024), EBU Tech 3380 v1.0.1 and the BBC Subtitle Guidelines page each return 0 hits for colour-blind, colour vision, CVD and deficien*. What they do say about colour: Ofcom lists colour as one speaker-identification option and points to WCAG for subtitle contrast; EBU-TT-D recommends a highly contrastive default text colour; the BBC subtitle guide makes colour the preferred speaker cue, limits it to white, yellow, cyan or green on black, and gives legibility as the reason. A negative result bounded to these documents, not to Ofcom rulings or EBU output in general.
• articleI only have the built-in enhance function (Premiere Enhance Speech, Adobe Podcast Enhance Speech or Descript Studio Sound): what are its documented limits and pitfalls, and what should I know before using it on film dialogue?
  Adobe and Descript help pages state concrete limits: Premiere Enhance Speech takes mono or stereo and returns a mono downmix, is clip-based, is documented as running on-device, may leave "unexpected or unprocessed words or syllables" at very low SNR, struggles with beamforming-mic recordings, and needs Media Encoder add-ons for matching exports. Descript Studio Sound needs internet, applies per file, is for recorded (not synthetic) speech, can output a silent waveform on very loud noise (lower Intensity) and has a documented Chrome export drift bug. Adobe Podcast Enhance Speech returns the uploaded format, with a 1 GB cap on the capture read. None of these pages publishes a measurement.
• articleFor iZotope RX Dialogue Isolate, Repair Assistant and Scene Rebalance, which controls, quality modes and documented failure modes should a dialogue editor know, and what changed between the RX 11 and RX 12 documentation?
  iZotope documents Dialogue Isolate as an ML separator with three gain controls, a Sensitivity control that it says trades noise removal against artifacts and dialogue clarity, a Good/Real-time vs Best/Offline mode (Advanced), and four-band scaling. Scene Rebalance adds a Voice/Music/Effects split whose voice Sensitivity keeps more breaths but can leak other elements. Release notes record an offline-mode defect (muffled end of selection) fixed in 11.2.0. The one first-person review read reports artifacts when the noise control is pushed and a disappointing Repair Assistant result. No source here measures quality.
• articleFaced with a noisy production-dialogue clip, what do the common AI "enhance" and "isolate" tools (iZotope RX, Premiere Enhance Speech, Adobe Podcast, Descript Studio Sound, DaVinci Resolve Voice Isolation) take in, give back and let me control, per their own documentation?
  Vendor documentation describes two families. One-control tools return a single processed dialogue track with one blend or intensity control (Premiere Enhance Speech Mix Amount, Descript Studio Sound Intensity; the Adobe Podcast pages read describe no strength control). Component tools split the input and expose per-component gain (iZotope Dialogue Isolate: voice, reverb, noise; RX 12 Scene Rebalance: voice, music, effects). The Resolve 20 guide read shows Voice Isolation as a toggle (Voiceover tool, AI Audio Assistant) but not its parameters; the 209 MB reference manual was not fetched. All statements below are vendor statements, not tests.
• articleHow could an agent numerically check a graded frame's levels against EBU R 103 and BT.709/BT.2100 without a hardware scope?
  A proposed procedure assembled from the standards: decode to the stated bit depth and range, drop pixels outside the active picture, low-pass filter with R 103's separable filters (horizontal 1,2,3,4,3,2,1 over 16; vertical 1,2,1 over 4), compute the share of R,G,B,Y samples outside nominal, preferred and total bands, and flag out-of-gamut only when more than 1% of the image exceeds the preferred band. Colour balance and hue checks follow from per-channel percentiles and Cb/Cr angles. The method is the worker's synthesis; a small stdlib script reproduces the band arithmetic on synthetic data, and no real frame, tool or scope output was run or compared.
• articleWhat are the 75% and 100% colour-bar targets, which should a scope be set to, and what code values do they have?
  Vendor manuals expose 75% vs 100% as a setting that must match the bar signal being fed (Tektronix WFM5200 and 1740A, Blackmagic SmartScope): the vectorscope graticule targets are drawn for one or the other. ITU-R BT.2111-3 (HDR bars) tabulates the codes: 100% bars use 940/64 and 75% bars use 721/64 at 10-bit (2884 at 12-bit), with a 40% grey, -2%/+2%/+4% black (PLUGE-like) steps and an explicit note that the pattern is not for black level setting. No SDR bar standard (e.g. SMPTE RP 219, ITU-R BT.801) was fetched, so the SDR 75% code values here are the worker's arithmetic from BT.709 s3.4.
• articleIf I mark or emphasise event boundaries for viewers, do they remember the sequence better, and where was that tested?
  Gold, Zacks & Flores (2017) edited three single-shot everyday-activity movies (about 5.5-6.3 minutes each) with a bell, a brief slowdown and an arrow, placed at event boundaries or event middles, and tested younger and older adults. Boundary cuing improved recall (about 0.29 vs 0.26, d=0.17 in Exp 1; boundary-item recall 0.37 vs 0.27) and, in Exp 1, recognition; the Exp 2 replication reproduced the recall benefit but not a reliable recognition effect. Mid-event cuing helped less. The cues were not cuts or narrative devices and the activities were not stories, so transfer to scene construction is a proposal.
• articleWhere do viewers of a narrative film feel one event end and another begin, and what story changes create that feeling?
  In Zacks, Speer, Swallow & Maley (2010), 24 adults watched The Red Balloon in the scanner and later marked coarse (largest) and fine (smallest) event boundaries. Coarse events averaged 59.4 s and fine events 22.9 s, fine boundaries nested inside coarse ones, and the chance of a boundary in a 5-second interval rose with the number of simultaneous changes in characters, interactions, objects, space, goals and causes (character changes largest). Brain responses followed boundaries. This is one 1956 film and one lab sample; the behavioural part is described by the authors as a close replication of an earlier experiment.
• articleWhat minimum text sizes or proportions do broadcaster and streamer documents set for on-screen text in video, and are any given as x-heights?
  DPP/Channel 4 state a minimum SD font height of 20 SD lines and derive 40 HD and 80 UHD lines/pixels for burned-in text so it stays legible after down-conversion (arithmetic: 3.7% of frame height). BBC Subtitle Guidelines set an authoring line height of 7-8% of active video height (4% for 9:16) and let players present at 0.6-0.8x for most screens, never larger than authored. Netflix's Titles & Graphics page states no size minimum. No source read states an x-height or a contrast ratio for video text. Apple's tvOS 23 pt minimum is a UI guideline, not a video-graphics rule.
• articleHow can an agent check a frame, caption or lower-third placement against action-safe and title-safe rules, and what edge cases must the check state?
  No source read provides a safe-area test procedure, so this candidate is a synthesis from the stated rectangles. A check needs (1) a named rule set and raster, (2) rectangle coordinates with a stated numbering base, (3) the text or graphic's bounding box measured at delivery resolution, and (4) a policy for motion, 4:3 protection and per-spec force. Sources supply the rectangles and three subtleties: R 95 counts pixel 0 as the first sample; ATSC/BBC express subtitle limits as percentages (origin 5% 5%, extent 90% 90%); Netflix lets motion text leave the box if it is readable inside at some point. An automated layout/caption checker for generated frames is a proposed hypothesis with a test, not a documented use.
• articleWhat exact action-safe and graphics-safe rectangles does EBU R 95 define for 720p, 1080 and UHD 16:9 frames, and which numbers are stated versus only derivable?
  EBU R 95 version 1.1 (June 2017) is a free PDF. Note 5 states the action safe area is 3.5% and the graphics safe area 5% at top, bottom and sides of a 16:9 full-format picture. Figures 2, 4 and 5 give the pixel boxes for 720p, 1080p and 2160p, and Figure 6 for 4320p. Figure 4 also labels a 4:3 caption safe area as 16.25% of the 16:9 image per side (312 px at 1920 wide, 1296 px wide). The pixel counts in the figures are rounded integers of the percentages; the document also contains a mislabelled line range in Figure 2.
• articleWhen a mixer records a boom and lavs of the same speaker, what must be captured and avoided on set so post can combine them (alignment, comb filtering, matching)?
  Sources describe a workflow in which production records every mic on its own iso track, sets input gain carefully, and logs the mix; the dialogue editor rebuilds the mix, uses lav isos to avoid perspective jumps between scenes, and aligns boom and lav in time to avoid comb filtering. DPA's vendor article gives rules for when AI dialogue matching works (no more reverb than the reference, no compression or distortion in the source), and DPA's comb-filtering article states the within-10-dB condition. The sources are practitioner statements and vendor demonstrations; none reports a controlled measurement on film dialogue.
• articleWhat do Avid's public documents state about Media Composer's AI-assisted dialogue tools (PhraseFind AI, ScriptSync AI, Transcript Tool, Multicam Auto Cut): what they produce, licensing prerequisites, languages and limits?
  Avid's Media Composer 2026.8 What's New (31 Aug 2026) documents PhraseFind Multicam Auto Cut (camera switching from speaker assignments in PhraseFind AI transcripts) and Transcript Tool versioning (the original AI transcript is kept and edits stored separately). The 2026.8 ReadMe says the Transcript Tool needs an active PhraseFind AI option (ScriptSync AI alone excludes it) and that indexing runs in the background and is resource intensive. The only language statement found is the 2023 press release (21 languages for automatic detection, initial). No inspected Avid document says whether transcription is on-device or cloud; the 43 MB Editing Guide could not be fetched under the 25 MB rule.
• articleWhat do Blackmagic's guides state about DaVinci Resolve's transcription-driven editing features (text-based editing, speaker detection, IntelliScript, Multicam SmartSwitch): inputs, outputs, edition, matching rules and limits?
  Across the Resolve 19, 20 and 21 New Features Guides, transcription underpins text-based editing in the Transcription window (Resolve 19, Studio), speaker detection, SRT import/export, and IntelliScript (Resolve 20, Studio) which builds a timeline from a plain-text script and picks the best take by spoken-dialogue matching only. Resolve 21 adds Final Draft (.fdx) script import. Multicam SmartSwitch (Resolve 20, Studio) cuts to the active speaker using audio plus video cues. The guides inspected do not state language lists for transcription (they point to Project Settings and the reference manual) or whether transcription is local or cloud; the 209 MB reference manual was not fetched.
• articleWhat does Adobe say Premiere's Text-Based Editing takes as input, what it produces, which languages it supports and what its stated limits are?
  At the Adobe help-page versions pinned here (pages dated Jan 2026 to Jun 2026), Text-Based Editing auto-transcribes spoken dialogue into a timecode-aligned transcript and mirrors cut/copy/paste of transcript text onto the timeline. Adobe lists UI languages on the overview page and a separate 18-language Speech-to-Text list; the two lists differ, and no inspected page says whether transcription runs on-device or in the cloud. Stated limits are short: dialogue only, no captions workflow inside the feature, clean audio recommended.

More