Editing and finishing

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

• articleHow does CTC forced alignment turn a transcript into word timestamps (frames, blanks, merge, score), and is the torchaudio API still available?
  Problem: you have an accurate transcript and need word start/end times for subtitles, dubbing timing or text-based editing. Conditions: CTC-trained acoustic model (tutorial uses the multilingual MMS alignment bundle). Method: compute the emission (frame-wise token probabilities); call forced_align with the tokenised transcript and blank index 0; the result is in the emission's frame coordinates with blanks and repeats; merge_tokens collapses repeats into token spans with scores; group tokens into words; word score is the average weighted by span length; convert frames to seconds with the ratio of waveform samples to emission frames. A special star token handles missing transcript. Failure modes: Inference: without the star token, untranscribed speech must be absorbed by neighbouring transcript tokens (the tutorial only says the star token handles missing transcript), and low word scores flag mismatched text. Limitations: the page itself warns that torchaudio moved to maintenance in ...
• articleHow do I request a native portrait video from Google's Gemini API (Gemini Omni Flash), and what resolution values does it allow?
  Problem: short-form needs 9:16 and an agent must know whether the model can render it natively. Conditions: Gemini API, model gemini-omni-1.1-flash via the Interactions API; the page also says the Veo 3.1 preview models in the Gemini API were shut down on 22 Oct 2026. Method: in response_format set type video and aspect_ratio to '9:16' (supported values listed as 9:16 and 16:9; 16:9 is the default); set resolution to 360p, 720p (default), 1080p or 4k. Example: the page's request sets response_format.resolution to '1080p'. Failure modes: the table labels 1080p and 4k as 'upscaled', so the model's native render is not stated to be 1080p; check the output file's dimensions rather than assuming. Only two aspect ratios are listed, so 1:1 or 4:5 need reframing. Limitations: page is a guide, not the full reference; no prices recorded. Version/date: fetched 2026-10-23.
• articleWhat licence terms cover RIFE and FILM frame-interpolation code and weights used by ComfyUI-Frame-Interpolation?
  Problem. The interpolation node pack (round 2) downloads RIFE and FILM weights at run time; which terms apply to them? Conditions. hzwer/Practical-RIFE commit bbfd2ea9 (2026-08-27; MIT) and google-research/frame-interpolation commit 69f8708f (last commit 2023-01-14; repository archived; Apache-2.0). Method. Practical-RIFE: the README states 'The content of these links is under the same MIT license as this project' for its trained models, so code and listed weights are MIT; the models are loaded from flownet.pkl files (pickle-family; see C3-B574-14). Third-party mirrors of rife47.pth etc. on Hugging Face (named in the node pack's code) are other people's uploads and carry no licence tag in the API results seen (marduk191/rife: none). FILM: the repository is archived, the code licence is Apache-2.0, the README describes pretrained models fetched separately and states 'This is not an officially supported Google product'; I found no statement of a separate weight licence in the README t...
• articleUsing c2patool, how do I record provenance for a generated asset, and what happens to the manifest when the file is transcoded or converted?
  Problem. Generated images/videos get re-encoded by editors and platforms; agents must know what the signed manifest does and does not survive. Conditions. c2patool commit c367d9c2 (2026-10-23, Apache-2.0, a separate repository from c2pa-rs since release 0.27.15) and c2pa-rs commit 8250bd96 docs. Method. c2patool -m manifest.json -o out.ext signs a manifest into the asset; the output extension must match the source and the tool will not convert file types. Intent flags: --create <IPTC digital source type> (for AI output, trainedAlgorithmicMedia is one listed value; it adds c2pa.created and cannot be combined with --update or --parent); default Edit intent adds the source as parent ingredient with c2pa.opened; --update is for non-editorial changes such as re-encoding or format conversion to an already-signed asset, which must already carry a manifest. --parent supplies the pre-edit file or an ingredient folder made with --ingredient. --sidecar writes a .c2pa file beside the output, --...
• articleWhat does Comfy's own upscaling handbook say about choosing and preparing upscalers for image and video, and how strong is that evidence?
  Problem. Choosing between conservative and creative upscalers and avoiding wasted passes. Conditions. Comfy blog post dated 2026-02-06; vendor-authored, qualitative side-by-side comparisons, includes partner-node (paid API) and local open models. Method. The post's takeaways: choose by use case (portrait skin, product photography needing faithful labels and edges, landscapes, illustration, archival video, CGI); conservative models for faithful materials and text; do not rely on upscaling to fix common AI artifacts; for SeedVR2 downscaling to about 0.35 megapixels with ImageScaleToTotalPixels before upscaling gives better results (its claim); video options named include SeedVR2, FlashVSR, HitPaw, Topaz Astra and Wan 2.2 upscale, with workflow downloads provided. Failure modes. Hallucinated detail from creative models; generation time varies strongly by model and hardware (the post lists per-model times without hardware or n for most items). Limitations. No objective metrics (PSNR/LPI...
• articleWhat does ComfyUI-Frame-Interpolation offer (RIFE, FILM, GMFSS...), what frame-count limits apply, and where does it download model weights from?
  Problem. Raising frame rate of generated clips and knowing what the node pack fetches at run time. Conditions. Fannovel16/ComfyUI-Frame-Interpolation, commit 26545cc2 (pushed 2026-03-29), version 1.0.11, MIT code. Method. VFI nodes (GMFSS Fortuna, IFRNet, IFUnet, M2M, RIFE 4.0-4.9, FILM, Sepconv, AMT, STMFNet, FLAVR, ATM-VFI, MoMo) take an IMAGE batch of at least 2 frames; STMFNet and FLAVR need at least 4 frames (README suggests FILM with multiplier=4 first for short inputs), STMFNet, FLAVR, ATM-VFI and MoMo are 2x only. clear_cache_after_n_frames limits memory. Multiplier values can be scheduled. GPU ops use cupy by default; a taichi backend (set ops_backend in config.yaml) is experimental for non-CUDA devices. Install is via install.py or install.bat (cupy-wheel is installed by the script). Weights: vfi_utils.py tries a list of GitHub release URLs (styler00dollar, the repo's own releases, dajes) and per-file Hugging Face mirror URLs at run time, calling torch.hub download_url_to_...
• articleHow do I chain Wan 2.2 image-to-video clips by extracting the last frame without quality loss, and when does ComfyUI rerun only the extraction step?
  Problem. Making videos longer than one generation by seeding each segment with the previous segment's final frame. Conditions. Example workflow doc in radiatingreverberations/comfyui-workflows (MIT; repo last pushed 2025-08-08; fetched from main, no commit pin), needs ComfyUI-VideoHelperSuite. Method. Take the last frame straight after VAE Decode via a Select Images node: set indexes to all frames but the last for the video file, and the last frame alone for a lossless image saved separately; the last frame is excluded from the video to avoid duplication when the next clip starts from it. Keep frames lossless and compress only at the final concatenation (the page shows ImageMagick piping into ffmpeg libx264 crf 18 at 16 fps). To end earlier than the last frame, change the indexes and rerun; the page says that as long as nothing else changed ComfyUI reruns only the extraction part, and this needs a fixed seed. Load the chosen frame with Load Image (from Outputs) and refresh, then cha...
• articleDoes 1.25x to 1.5x playback change quiz scores, satisfaction or how the speaker is judged, in preregistered online experiments?
  Problem. Whether a slightly faster pace changes viewer experience, speaker impressions and learning. Conditions. Three preregistered online experiments: Study 1 a tiramisu tutorial at 1x, 1.25x or 1.5x (final N = 326 after 53% exclusions); Study 2a an economics video at 1x vs 1.25x with a quiz-warning manipulation (N = 313 after 54.4% exclusions); Study 2b the same in undergraduates (N = 246 after 25.2% exclusions). Measured result. Faster playback reliably raised perceived audiovisual distortions and modestly reduced satisfaction; in Study 1 viewers were more satisfied at 1x (M = 4.17) than at 1.25x (M = 3.82, p = 0.011); the speaker was rated more positively at 1x (M = 4.44) than at 1.25x (4.24) or 1.5x (4.20), marginally significant (p = 0.055), and in Study 2b 1x beat 1.25x on speaker rating (p = 0.022). Objective quiz performance did not differ by speed. Failure modes. Very high exclusion rates; self-report scales; one video per content type. Limitations. Speed is a playback mu...
• articleHow much does speeding up narration or lecture video hurt learning, according to a 2025 meta-analysis, and how reliable is it?
  Problem. Choosing a narration pace (or a playback speed) for instructional or explainer video. Conditions. Evidence is about accelerated instructional video with different teacher appearance, subtitles and subject matter, mostly educational samples in China and the US. Method (what was measured). A meta-analysis of 12 experimental or quasi-experimental papers, converting speed to words per minute and pooling Hedges' g: acceleration raised cognitive load (g = 0.59, nine studies), lowered maintenance test scores (g = -0.41), lowered transfer ('migration') scores (g = -0.50) and lowered learning satisfaction (g = -0.24). Moderators: teacher on screen, subtitles, country and subject changed some effects; the review reports speeds from 1.1x to 2.5x across the pooled studies, and notes the satisfaction drop arose in samples whose original speech was already 183 to 251 wpm. Failure modes. Heterogeneity is large for cognitive load (I2 77.8%) and satisfaction (I2 96.4%); the authors find mis...
• articleCORRECTION to C3-B241-G73-04: is it true that none of the library pages read says whether temp or preview use is itself licensed? (Overstated: the FirstCom piece and Media Music Now both say something about permission for temp or preview use.)
  Problem. C3-B241-G73-04 concludes: 'None of the four library pages read says whether temp or preview use is itself licensed, or covers festival or pitch screenings.' Audit result. (a) Supported: Media Music Now says temp music can defer full licensing and producers 'come back to us for the fully licensed version'; Marmoset's 2013 post offers lower-resolution MP3 downloads that are not watermarked; FirstCom's Lonnie Sill (IDA, 2014) says an editor temp-scored a whole film from the catalogue before a distribution deal. (b) Overstated: the absence claim is too strong. The FirstCom piece says the editor 'had existing permission to access music from the library website' before temp-scoring, and that a blanket all-media worldwide licence was provided afterwards, which is a statement about the permission basis of temp use under that relationship. Media Music Now calls its downloadable previews 'free' and says temp use can avoid 'full licensing' until the work circulates, which implies a pr...
• articleWhich kinds of discontinuity at a cut make viewers feel a new event has started: space, time or action (Magliano & Zacks 2011)?
  Problem: how far can an AI sequence break spatial or temporal continuity before it reads as a new event? Conditions: narrative film shown continuously. Method (as reported): re-analysis of behavioural segmentation data (Study 1a, 41 participants; 1b, 24 participants) and fMRI data from viewers of The Red Balloon (33 minutes); edits coded as continuous in space/time/action, discontinuous in space or time but continuous in action, or discontinuous in action too. Result: discontinuities in action had the biggest impact on where viewers marked event boundaries; space and time discontinuities had minor effects; edits produced large transient responses in early visual areas, with different patterns for spatial-temporal vs action changes. Mapping to AI shot design (inference): the continuity worth protecting across a cut is the action/goal thread (who is doing what with which object), more than exact location; relocating a character or jumping time while action continues is tolerated, whil...
• articleWhich parts of a match-action cut (motion before, motion after, sound) create edit blindness (Smith & Martin-Portugues Santacreu 2017)?
  Problem: editors say a cut should start on the action; which side of the cut matters? Conditions: Hollywood clips containing match-action cuts. Method (as reported): motion was removed before the cut, after it, or both, with or without the original soundtrack, while viewers tried to detect cuts; lab eye-tracking with 32 recruited, 27 analysed participants (age 19-35); an online replication ran 80 clips across 8 conditions with 8 participants per clip-condition. Results: removing post-cut motion made cuts quicker to detect and less likely to be missed; removing pre-cut motion had no effect; viewers reoriented less to new content across intact match-action cuts; audio played a large part and edit blindness mostly disappeared without audio. Mapping to AI shot design (inference): when joining two generated clips, the second clip's first frames should already contain the motion that continues the first, and a continuous audio bed is part of the cut, not decoration; a silent preview can m...
• articleWhat does the Attentional Theory of Cinematic Continuity say about why match-action, eyeline and shot/reverse-shot cuts feel continuous, and what should an AI cutter check (Smith 2012)?
  Problem: continuity rules are taught as conventions; this is a cognitive account of why they work. Conditions: cuts between shots of a scene. Method (source's argument): viewers match perceptual expectations across a cut by attention, without needing a coherent representation of the depicted space; cuts are timed so the next shot supplies what attention was preparing to reach (a gaze shift, a movement, a face). The paper treats match-action, matched exits/entrances, shot/reverse-shot, the 180 degree rule and point-of-view cuts as consequences, and says the cut is not hidden in a blink or saccade because cuts rarely coincide with such periods. It also notes viewers default to the screen centre when a subject leaves the frame and are captured by suddenly revealed bright objects. Mapping to AI shot design (inference, labelled): when cutting generated clips, (a) end a shot with the direction of an eyeline or movement the next shot continues, (b) place the subject near screen centre at t...
• articleHow coherent is gaze on professionally cut footage compared with natural video, and what does the upper limit look like (Dorr et al. 2010)?
  Problem: how much agreement between viewers should a designer expect when guiding attention? Conditions: free viewing without a task. Method (as reported in the abstract): eye movements from 54 subjects on 18 high-resolution outdoor videos, variability measured with Normalized Scanpath Saliency extended over time; controls were stop-motion versions of the same content, Hollywood action trailers (probing the upper limit of coherence from deliberate camera work and cuts), and a repetition condition (same movies ten times over two days). Result: up to about 80% of subjects looked at the same region in some segments but variability was usually much greater; gaze on Hollywood trailers was significantly more coherent than on natural movies; static images show onset effects early and idiosyncrasy later. Mapping to AI shot design (inference): synchrony is not a property of 'video' but of composed, cut footage; uncut, wide, AI-generated establishing shots with many equal-salience elements wi...
• articleIf edited film makes viewers look at the same place, how much does individual comprehension still change gaze (Loschky et al. 2015 'tyranny of film')?
  Problem: designers of AI shots assume they can steer attention with framing and motion; does viewer understanding override that? Conditions: rapidly edited, centre-framed Hollywood-style sequence. Method (as reported): a 12-second, six-shot cross-cut James Bond (Moonraker) clip, shown silent at 720x480, 30 fps; one group saw only the clip, the other also saw the preceding 2 min 56 s (Context). Experiment 1 (think-aloud, 98 recruited, 10 discarded as having seen the film), Experiment 2 (event segmentation, 88, 5 discarded), Experiment 3 (eye tracking, EyeLink 2000, 176 participants, 87 per condition, 13 discarded). Results: Context viewers more often drew the predictive inference (91% vs 71% in Exp. 3); gaze showed strong attentional synchrony in both conditions against a chance baseline, with only small differences between them (slightly greater synchrony and lower processing load in the Context group at the first circus-tent shot). The authors read this as more consistent with 'tyr...
• articleWhat is worldizing, how is it actually done (equipment layout, tracks recorded, how they are mixed), and why use it instead of reverb?
  Corrected 2026-10-23 - see C3-B683-02; the original statements below are kept for history and are superseded where the correction says so. Three voices describe the same method: play a finished recording through a speaker in a real space and re-record it with a microphone. Murch's American Graffiti account (quoted on a filmsound.org glossary page from a published interview) gives the concrete layout: a speaker rotated while a microphone about fifty feet away is moved, two passes, then three tracks (dry plus two worldized) blended in the mix to move between present and distant. Welles's 1957-58 sound notes, as quoted in a 1998 article, specify a cheap horn in an alley and say an echo chamber plus filter is not enough. The stated purpose is perceptual: diffuse music leaves dialogue as the focus.
• articleHow do I keep timecode, frame rate and the tempo map consistent across a DAW, a notation program and picture revisions?
  Corrected 2026-10-23 - see C3-B683-03; the original statements below are kept for history and are superseded where the correction says so. Vendor and practitioner texts show that the picture reference carries a start timecode and frame rate that must be set consistently, and that the tempo map can be moved between tools as a MIDI file: Dorico 2.2 (Nov 2018) added tempo-track import and export (timecode offset, tempo changes, time signatures, markers) explicitly for updated edits; Sibelius 2024.3 added pasting a system selection as MIDI per a 2024 article; the orchestrator S10 returns a new tempo map whenever tempos are retimed and trims measure numbers while marking the sketch "Trimmed". Sources document the interchange but not a procedure for re-conforming music to a changed edit.
• articleWhere is OpenUSD's automatic timeCodesPerSecond scaling across composition documented?
  Problem. Candidate M5-01 says the user-guide passage on automatic scaling of layers with different timeCodesPerSecond is 'present only at dev head bc32a65, not at the existing 363a7c8 pin'. Nature: (e) changed since. Conditions. OpenUSD releases v26.08 and v26.11.1. Method. The guide docs/user_guides/time_and_animated_values.rst at the v26.08 release tag already contains the section 'Automatic Scaling of timeCodesPerSecond' at line 298; the file at v26.11.1 also has the section anchor, so it is documented in releases, not only dev head. The behavioural claim (silent retiming on composition) is supported. Limitations. Release v26.05 and earlier not checked. Version and date. 2026-10-23.
• articleDoes C3-B124-G45-07's version-specific tempo-map interchange evidence appear on its cited pages?
  Correction (d, unsupported details) to C3-B124-G45-07. Problem: the candidate states Dorico 2.2 (Nov 2018) added tempo-track import/export with timecode offset, time signatures and markers, and that Sibelius 2024.3 added pasting a system as MIDI. On re-fetching the four cited pages, none contains '2.2', '2024.3' or '2018'. What they do support: Scoring Notes says Dorico has File > Import > Tempo Track so tempos match prior DAW work; a film orchestrator marks the sketch and score 'Trimmed' when trimming measure numbers; the Logic page describes frame-rate settings. Method: cite Dorico tempo-track import without a version number or date from these sources; get the version facts from Steinberg or Avid release notes. Limitations: Dorico export of tempo tracks is not shown on these pages.
• articleWhich ISDCF-naming, hearing-impaired (HI), visually-impaired (VI) and language fields does ClairMeta compare with the CPL, and which does it only parse?
  Corrected 2026-10-23 - see C3-B645-06; the original statements below are kept for history and are superseded where the correction says so. ClairMeta (b3b66a02) parses the DCP title against its ISDCF 9.6 rule set, including HI and VI flags and the audio language, but no check module uses those parsed values: its 12 title-claim checks compare frame rate, dimension, aspect ratio, subtitle and caption presence, channel count, immersive sound, resolution, standard, Dolby Vision, EclairColor and package type with CPL or probe data. The only language comparison is subtitle XML versus CPL. All dcnc checks report at INFO by default, so a default run does not treat title/CPL mismatches as errors.
• articleWhat do AC-3 dialnorm, Android's MPEG-4/MPEG-D DRC decoder keys and Apple's iTunNORM tag document about stream-carried loudness metadata, and what do players do with it?
  Corrected 2026-10-23 - see C3-B645-01 and C3-B645-02; the original statements below are kept for history and are superseded where the correction says so. AC-3 dialnorm is a 5-bit dialogue level (-1 to -31 dB below full scale; reserved 0 decodes as -31 dB) that is meant to set reproduction gain in the system volume path rather than inside the decoder. Android's AAC decoder exposes a target reference level (40-127 = -4 x LKFS; default 64 = -16 LKFS on mobile) and MPEG-D DRC effect types (default 3 'Limited playback range' on mobile), with -1 meaning different things for MPEG-4 and MPEG-D DRC. mpv defaults AC-3 DRC to off despite the standard's default. Apple's iTunNORM is known only from a reverse-engineered 2013 wiki.
• articleHow many ISDCF-name claim fields does ClairMeta cross-check against the CPL?
  Problem. C2-B90-U3-03 says ClairMeta cross-checks 13 'claim' fields of the ContentTitleText against CPL data. Conditions. In dcp_check_isdcf_dcnc.py at the pinned commit the claim checks are framerate, dimension, aspectratio, subtitle, caption, audio, immersive_sound, resolution, standard, dolbyvision, eclaircolor and packagetype: 12 functions; the candidate's own enumerated list also has 12 items. Method. Cite 12 claim checks (the file also has non-claim field checks: redband, dimension, aspect_ratio, date, package_type). Failure modes. A reviewer reconciling the count against the code finds a mismatch. Limitations. If the candidate counted a different convention (e.g. including a helper), that was not stated. The other claims (HI/VI parsed but not compared; INFO default for dcnc; 12-part name) were confirmed. Version/date. ClairMeta b3b66a0, fetched 2026-10-23.
• articleIs there a Dutch rule of at most 4.5 LU between voice loudness and programme loudness?
  Problem. C2-B27-C4-09 reports a Dutch rule of at most 4.5 LU between voice loudness and programme loudness. Conditions. EBU Tech Review (June 2022) section 4.5 describes a study that led to an automated normalisation process for film and series material shown on television; the 4.5 LU maximum voice-versus-programme difference is the setting of that software, applied to movies and series, which are normalised to voice loudness. Method. Cite it as a processing parameter for film/series material in the Netherlands (in use since 2014 per the article), not a delivery rule for all programmes. Failure modes. Applying 4.5 LU to factual or live content as if it were a requirement. Limitations. Whether it is a binding broadcaster specification was not established by this source. Version/date. EBU Technical Review, June 2022, fetched 2026-10-23.
• articleWith FFmpeg, how do I tag an export as Rec.709 without changing pixels, and when do I need to convert instead?
  Corrected 2026-10-23 - see C3-B681-06; the original statements below are kept for history and are superseded where the correction says so. At FFmpeg commit 9047fa1b (tag n8.1), tagging and converting are different tools. Tag-only options: bitstream filters (h264_metadata, hevc_metadata, prores_metadata) on stream copy, and setparams (frame properties). Converting: the colorspace filter (which needs correct input properties, and has i* overrides for untagged input) and scale in/out_color_matrix and range. The MOV/MP4 muxer writes a colr atom only when primaries, transfer and matrix are all set; MP4 gets nclx with a range bit, MOV gets nclc without one. Nothing here was run.
• articleWhen does FFmpeg's MOV/MP4 muxer write a colr atom?
  Problem. C3-B232-G71-02 says the muxer 'writes a colr atom only when primaries, transfer and matrix are all set'. Correction type: (b) overstated. Method. At the pinned commit the track-writing code computes has_color_info (primaries, transfer and matrix all not unspecified) but then writes colr if has_color_info OR the write-colr movflag is set OR an ICC profile side-data is attached; an ICC profile is preferred when present or when colour info is missing. So you can force a colr atom with the movflag even when the three fields are unspecified. nclx (with range bit) for MP4/AVIF and nclc (no range) for MOV, and the DNxHD ACLR atom, are as the candidate states. Limitations. The movflag's public documentation name was not found in formats.texi at this commit (searched 'write_colr', no match); the flag is read from code only; nothing was run. Version and date. n8.1, fetched 2026-10-23.
• articleHow do I add a YouTube audio description track, and what must already exist before I can upload one?
  Problem: delivering a narration track that describes on-screen action for blind or low-vision viewers on YouTube. Conditions: Advanced features access; YouTube Studio on computer > Languages > video > language. Method: the language's original or dubbed audio track must be uploaded first; then, next to Descriptive audio, Add > Select file > Publish. The file must be a supported audio-only format and roughly the same length as the video. To replace a track, delete the descriptive audio for that language and upload again. YouTube describes the track as narration placed in natural pauses in the audio. Failure modes: no descriptive slot appears if the base-language audio track is missing; an audio file that is much shorter or longer than the video. Limitations: this page gives no writing guidance (tense, density, extended description), which earlier candidates cover from ACB/DCMP/Netflix/Ofcom; supported file types are not listed inline; availability is gated. Version/date: help page rea...
• articleHow do I read YouTube's audience retention report: what do flat lines, slow declines, spikes, dips and the 30-second 'intro' figure mean, and when does the report exist?
  Problem: deciding which moments of a video to cut, front-load or expand from the retention graph. Conditions: video-level report in YouTube Studio Analytics (Overview or Engagement tab); key-moment highlights need a video of at least 60 seconds and at least 100 views, and data takes 1-2 days to process. Method (as documented): read four shapes. Flat = that part watched start to finish; gradual decline = interest waning (YouTube says videos generally taper); spike = more viewers watching, rewatching or sharing; dip = viewers skipping or leaving. 'Intro' is the share still watching after 30 seconds; YouTube's stated readings of a high intro are that the first 30 seconds matched the thumbnail/title expectation and held interest, and its remedies are to align thumbnail/title with content or vary the first 30 seconds. 'Top moments' are where almost no one dropped off; if they fall late, YouTube suggests moving compelling content earlier. 'Typical retention' compares your 10 latest videos...
• articleWhat do YouTube's audience retention segments (new vs returning, subscribers vs non-subscribers, organic vs paid) and the detailed-activity report let me separate, and why can segment views exceed total views?
  Problem: a blended retention curve hides that different viewers behave differently. Conditions: Advanced Mode may be needed (the page notes 'you might need to enable Advanced Mode'); segments appear under the retention report 'See more'. Method: pick a segment drop-down to split the same video into new vs returning viewers, subscribers vs non-subscribers, and organic vs paid traffic (paid = skippable video ads and display ads). The detailed activity report shows absolute view counts per moment and where viewers started and stopped watching. Example the page gives: a segment's absolute views can exceed the video's overall view count because one viewer may watch portions several times. Failure modes: reading detailed-activity peaks as unique viewers; comparing a paid-traffic curve with an organic one as if the audience were equivalent. Limitations: documentation only, no benchmark values; paid-traffic definitions are specific to Google Ads video formats. Version/date: help page read 2...
• articleHow do I add captions to a YouTube video (file upload, auto-sync, typing) and what limits does YouTube state for auto-sync and automatic captions?
  Problem: getting accurate, timed captions on a published video. Conditions: YouTube Studio > Subtitles, per language. Method: add the language, then choose Upload file (with timing or without timing), Auto-sync (paste or upload the transcript and YouTube aligns it), Type manually, or rely on automatic speech-recognition captions. The page tells creators to include sound cues such as [applause] so viewers know what is happening. Auto-sync needs a transcript in the same language as the speech and in a language supported by YouTube's speech recognition; transcripts are not recommended for videos over an hour or with poor audio. Automatic captions are created only in the video's default language. Failure modes: a transcript in a different language from the audio; poor audio quality undermines alignment. Limitations: this page does NOT give a word-error rate or an accuracy caveat for automatic captions, and does not list supported file types inline (a link is referenced but its list was ...
• articleWhat are YouTube's documented limits for end screens and info cards (duration, element counts, suppressions) that affect where to place calls to action?
  Problem: planning the final seconds and mid-video prompts so they are actually shown. Conditions: long-form videos in YouTube Studio > Content > Editor. Method (documented limits): end screens occupy the last 5-20 seconds, the video must be at least 25 seconds long, and a 16:9 video can hold up to four elements (other aspect ratios may allow fewer). Element types: video (latest, best for viewer, or chosen), playlist, subscribe, channel and, for Partner Program channels, an external link. Cards: up to 5 per video; types video, playlist, channel, link (Partner Program); a channel card needs message and teaser text. Interactions: card teasers and video watermarks are suppressed during the end screen; viewers can hide end screens; cards do not show if a Content ID claim has an active campaign, and videos displaying cards show no Call-to-Action overlay. Neither is available for made-for-kids videos; end screens are also unavailable on mobile web and 360 videos. Failure modes: designing a...
• articleHow do I plan music to picture: hit points, tempo choice and frames per beat?
  Problem: AI or library music has to end on the cut and land accents on picture events. Conditions: a locked or near-locked cut with timecode. Method (Music Technology, Jan 1988, a composer's workflow): the picture dictates to the music; first fix the cue's exact length and list hit points (action points to accent) as timecode hours:minutes:seconds:frames, often with a one-hour offset (01:00:00:00 start); then choose a tempo that suits the mood, and check where hit points fall on bars and beats; you will not get all on downbeats, so pick the most important hits, change tempo, insert a 3/4 or 5/4 bar, or use ritardando/accelerando; there is no rule that every hit lands on a downbeat. The article notes the old frames-per-click notation and that software of the time calculated the layout. Frame maths (my arithmetic, not from the article): frames per beat = fps x 60 / BPM, so at 24 fps, 120 BPM is 12 frames per beat and 48 frames per 4/4 bar; 90 BPM is 16 frames per beat; at 25 fps, 120 ...
• articleWhich parameters does the Topaz upscale API expose (model, upscale_factor, target_fps, recover_detail), and when should I not upscale an AI video at all?
  Problem. Choosing whether and how to upscale generated footage. Conditions. Topaz upscaling via fal's API (hosted). Method. Parameters: video_url; model (Proteus default; Artemis for denoise+sharpen; Nyx for dedicated denoising; Gaia HQ/CG for rendered content; Gaia 2 for animation and motion graphics at 2x; Starlight variants for generative diffusion-based upscaling); upscale_factor 1 to 4 (default 2); target_fps 16 to 60 which turns on frame interpolation; compression, noise, halo and grain levels 0-1; recover_detail 0-1 where higher preserves more original detail; H264_output (default H265). Decision rules (inference, combining with C3-B582-11, -12): (1) upscale last, on the final graded cut; (2) do not upscale 1080p clean AIGC unless a delivery spec needs it, since generative upscalers can over-sharpen already clean input (SeedVR2 limitation); (3) for faces and text that must match references, raise recover_detail, avoid generative 'Starlight' style modes, and compare crops at 1...
• articleWhat does Phillips (1914, Ch. IV) say a 'vision' insert is, and where does he defer the rules for using it?
  1914 practice (Phillips): Chapter IV defines the vision insert as the screening of thought, memory, dream or hallucination bearing on the character's conduct, gives one example (Example 21, with a nested close-view and a 'Continued' scene return) and defers fuller treatment. Cautions found by keyword location elsewhere: turning backward is a rare exception, yet a vision should add data that moves the play forward. Negative result: no length, count or placement limit for visions appears in Ch. IV.
• articleWhat does Phillips (1914, Ch. IV) actually say under 'Breaking Up Long Scenes' and 'Preserving the Illusion' (two sub-headings with no section of their own)?
  1914 practice (Phillips): the sub-heading names breaking long scenes and preserving the illusion, but the chapter treats them inside other sections. Breaking a scene with an insert is defended against the persistence-of-vision objection; the close-view is called the best device for dangerously long scenes (no length given); illusion is preserved by making inserts feel natural and by tying close-views to a character's hands. Script notation: scene 'Continued'. Negative result: no length or count limit.
• articlePROPOSAL (1914 practice as the basis): when is an intertitle, insert or close-up justified in a silent or minimal-dialogue scene, as a check an agent can run?
  Agent check, labelled 1914 practice plus a proposal: five steps drawn from Phillips (Ch. IV): try to show the point in action; if not, test it against his named cases (continuity-essential subtle point, lapse of time, mental process, premise); pick caption, simple insert, close-view, vision or spoken line by his definitions; drop the device if repeated or not carrying the story to the climax; keep the illusion by tying objects to a character's act. The order and combination are mine; no source tests the check, and Ch. IV gives no numbers.
• articleAccording to Phillips (1914, Ch. IV), what is a close-view, when is it 'indispensable', and how does it differ from a simple insert?
  1914 practice (Phillips): the close-view is a magnified object or a close segment of action. He lists uses (emphasis and dramatic effect, small essential objects, subtle emotion, hidden things, the strong-glass effect) and claims it breaks dangerously long scenes better than any device, and divides inserts into static 'simple inserts' and live 'close-view inserts'. Example 18 and Example 22 treat the letter differently, a tension the text leaves unresolved. He gives no number for how many close-views or how long a scene must be before one is needed.
• articleAccording to Phillips (1914, Ch. IV), what is an insert, when is it justified (letter, telegram, newspaper, premise), and what misuses does he warn against?
  1914 practice (Phillips): an insert is film cut into a scene that the audience should take as natural scene matter. He values it for economy and for setting up the premise, but calls letter, telegram and newspaper inserts 'dangerous expedients' if overused, and insists an insert be interpretive matter that moves the story toward the climax or be dropped. He uses 'insert' in two senses (all inserted matter; and the narrow 'simple insert' for static matter). No numeric limit appears in this chapter.
• articleDoes Phillips (1914, Ch. IV) give any length or number limits for captions, inserts and other devices, and do the chapter's own examples fit the limits stated elsewhere?
  1914 practice (Phillips) negative result, bounded to Ch. IV: no word, footage, count or frequency limit appears; limits are qualitative ('too frequently', 'dangerously long', 'mercilessly'). The 15-word caption and 20-word insert figures are in Ch. IX (cited via C3-B259-S74-05). A code-derived count of the chapter's printed examples shows every caption counted at 12 words or fewer, but letter inserts of 20-21 and 35-36 words, so Phillips's own Example 17 exceeds the Ch. IX insert figure unless abridged.
• articleAccording to Phillips (1914, Ch. IV), what is a caption, when should a photoplay writer use one, and what misuses does he warn against?
  1914 practice (Phillips, a US trade manual for silent photoplays): the caption (his preferred word for what others call leader or sub-title) is an action-title, written by the author and shown intact. His rule is to translate a point into action first and caption only what is essential to continuity but too subtle to act; his stated purposes are economy, a lapse of time, and a mental process. He warns against captions that tell what the next scene shows, mere labels, and poetic titles in a harshly realistic play. Chapter IV gives no word or footage limit (the 15-word figure is in Chapter IX, see C3-B259-S74-05).
• articleAccording to Phillips (1914, Ch. IV), when may a silent photoplay show a spoken line, in what form, and what restraint does he require?
  1914 practice (Phillips): 'dialog' as conversation is out of the photoplay, but a single spoken line may appear as an insert after its utterance or as a caption that voices the next sequence. He requires that it come naturally, bridge a gap, supplement not replace action, and be omitted if the play is better without it. His text contains a timing tension (simultaneous versus follows) and no count or length limit. Earlier rows cite two of its sentences for a staging question (C3-B231-S58-04).
• articleWhat does Apple say about spatial metadata and disparity adjustment when converting side-by-side 3D to spatial video?
  Problem. Stereo files can be uncomfortable or treated as plain stereo. Conditions. Side-by-side stereo video converted to MV-HEVC for Apple Vision Pro. Method. (1) Convert by splitting each frame and writing left and right halves to the left- and right-eye layers. (2) Spatial metadata describes the left/right cameras (baseline, horizontal field of view, disparity adjustment). Adding it makes Apple platforms treat the file as spatial rather than just stereo and enables visual treatments that reduce common stereo discomfort. (3) Sample values: virtual cameras 64mm apart with 80 degree horizontal field of view; a disparity adjustment of +2% of image width gave a comfortable result in a window, placing the nearest object just behind the front of the window while keeping depth. Failure modes. Wrong baseline or field of view metadata for the content; nearest objects in front of the window plane. Limitations. The values belong to Apple's sample content; other content needs its own choices....
• articleWhat may other creators reuse from my Shorts (audio, Cut, Green screen, Collab, templates), how long can a sampled segment be, and how do I opt out?
  Problem: knowing what rights your Shorts carry once published, and what happens to derivatives when you restrict or delete. Conditions: YouTube Shorts remix tools on mobile; Studio for opt-out; Content Manager partners have separate controls. Method (documented): other creators can remix audio from Shorts and long-form videos ('Use this sound'), make a Cut, use a video as a Green screen background, Collab, or use a Short as a template; remixes are credited back to the source. Music-video limits: Cut samples a 1-5 second segment (audio and video); Sound samples up to 90 seconds of audio, and some partner agreements limit this to 30 seconds. Default: Shorts are automatically opted in to remixing; a creator can opt Shorts out of video remixing in Studio (Content > video > Show more > Shorts remixing), also in bulk and at upload; only Content Manager partners can opt out of both audio and video. Effects of restricting or deleting: existing audio remixes are muted, set to Unlisted and sc...
• articleHow do I measure and fix a constant audio offset in an edit with FFmpeg (-itsoffset, adelay, aresample async), and what does each tool actually change?
  Problem: separately generated or dubbed audio lands early or late against picture. Conditions: a CONSTANT offset has been measured (clap/flash marker, or a transient in both streams); drift is a different problem. Method (all statements from the FFmpeg docs unless marked): -itsoffset is an input option; the offset is added to the input's timestamps and a positive value delays that input's streams, so place it before the -i of the audio file to delay audio (a negative value to advance it is my inference from 'added to the timestamps'; test it). The adelay filter delays selected channels and fills the gap with silence; delays are in milliseconds per channel separated by '|', with an S suffix for exact samples and 'all=1' to apply the last delay to all remaining channels, e.g. adelay=delays=64S:all=1. aresample with async can stretch/squeeze samples to follow timestamps (docs example async=1000, maximum 1000 samples per second of compensation), which is a drift-handling tool, not an of...
• articleWhat lip-sync (sound/picture) timing tolerance does EBU R37 set for a broadcast programme, and what is the stage-by-stage versus end-to-end figure?
  Problem: an edit or AI-dubbed/AI-generated-audio deliverable needs a defensible number for 'is the audio in sync'. Conditions: broadcast or broadcast-style delivery; R37 is a 2007 EBU recommendation measured under EBU R28 viewing conditions. Method: R37 gives two figures. (1) Accuracy at each stage of the chain: audio from 5 ms early (sound before picture) to 15 ms late (sound after picture). (2) At any output intended for emission, the overall end-to-end difference should lie within Table 1: sound before picture up to 40 ms, sound after picture up to 60 ms. It says the values come from subjective tests of when lip/speech asynchrony becomes perceptible to 50% of observers, that perceptibility depends on content and viewing distance, and that HD needs particular care. It also says audio and video should be kept coincident in the file and not advanced or retarded to compensate for downstream delays, and that concurrent flash/blip (1 kHz tone, one frame) header markers are the measurem...
• articleWhat exact numbers does Netflix set for subtitle in-times, out-times, shot changes, minimum duration and gaps (at 24 fps and other frame rates)?
  Problem: timing rules for subtitles in frames, not just characters per second. Conditions: Netflix timed text at any frame rate; the page writes rules for 24 fps and scales the half-second rule (12 frames at 24 fps, 15 at 30 fps, 30 at 60 fps) while the minimum gap stays 2 frames. Method (source statements): in-time on the first frame of audio, within 1-2 frames acceptable; out-time ideally at least half a second after audio ends when no subtitle follows; shot-change rules: dialogue starting on or within half a second past the cut sets the in-time to the first frame of the shot; an out-time within half a second of the last frame before a cut extends to the cut, respecting a 2-frame gap; subtitles may cross a shot change only if the dialogue does; minimum gap between subtitles 2 frames, and gaps of 3-11 frames at 24 fps must be closed to 2 frames ('chaining'), so gaps are either 2 frames or at least half a second. Minimum duration is 20 frames (stated as 4/5 s on this page, which doe...
• articleWhat do ITU-R BT.1359-1 detectability and acceptability thresholds say about audio leading versus lagging picture, and which sign convention does it use?
  Problem: viewers tolerate audio lag and audio lead very differently, so a single symmetric +/- figure misleads. Conditions: broadcast television; thresholds are averages from subjective tests, original (1998) Recommendation. Method: BT.1359-1 states detectability thresholds of about +45 ms to -125 ms and acceptability thresholds of about +90 ms to -185 ms on average, where a POSITIVE value means sound is advanced (early) relative to vision. It recommends an overall sound/picture tolerance of +90 / -185 ms, +25 / -100 ms between image source and the zero reference, and +22.5 / -30 ms from final source selection to the transmitter input, with no downstream segment outside the broadcaster's control adding more than +/-2 ms. Its appendix explains the 22.5/30 ms limits as half a grade point above the detectability threshold on the five-point scale (one grade is about 60 ms for sound delay, about 45 ms for sound lead). Practical reading (inference): audio that lags picture is detected lat...
• articleWhat does YouTube document for creating Shorts (length, resolution, title limit) and how did Shorts view counting change on 31 March 2025?
  Problem: knowing the platform constraints and metric definitions before cutting or measuring a Short. Conditions: YouTube app Shorts camera or uploading a vertical video. Method (documented): Shorts can be up to 3 minutes long; maximum upload resolution is 1080p; the title field allows up to 100 characters; privacy defaults to private for creators aged 13-17 and public for adults; drafts can be saved. From 3/31/2025 a Short view counts every start or replay with no minimum watch time; the older metric is kept as 'Engaged views' so creators can compare Shorts, and Partner Program eligibility and Shorts revenue share stay based on engaged Shorts views. Example/contrast: a later notice on the content-performance page (see C3-B573-05) says views are counted at play start in all formats from 24 August 2026. Failure modes: comparing raw Shorts views before and after March 2025 as if they measured the same thing; assuming a high view count means viewers stayed. Limitations: the fetched pag...
• articleHow do Veo 3.1 and Luma Dream Machine use start and end keyframes, and what can I use them for in multi-shot continuity?
  Problem. Controlling where a clip begins and ends so that cuts and transitions line up. Conditions. Veo 3.1 'first and last frame' (Google, Oct 2025) and Luma Dream Machine keyframes (Luma help article, Nov 6, 2024). Method. Veo: supply a start image and an end image and describe the transition in the prompt; the guide's example builds both stills with an image model, then asks for a smooth 180-degree arc between them. Luma: set a start frame and an end frame (uploaded or generated), optionally add a text prompt alongside the keyframes to guide the transition; Extend can also take an image keyframe as the destination, generating an extension of up to 9 seconds from a default 4-second clip. The Luma API field names (frame0, frame1, loop) are in C3-B571-11. Use for continuity (inference): make the start frame the last frame of the previous shot to continue a move; design the end frame as the pose you will cut from; generate bridging stills with the same lighting and lens clauses. Fail...
• articleShould I write camera motion in a prompt as degrees and percentages or as comparative language, and how do I match motion across a cut (Hailuo guidance)?
  Problem. Two generated clips may not match in motion direction or speed at the cut. Conditions. I2V clips of about 4-6 s; vendor knowledge page (July 2026). Vendor guidance. (1) Do not use numeric camera commands such as 'Pan 30 degrees left' or 'Zoom 15%'; the page says these typically give inconsistent outputs and that the model interprets visual relationships and 'feel'. (2) Treat shot A as the master motion reference and prompt shot B comparatively: 'Continue the slow, deliberate dolly-in from the previous shot, maintaining the same forward momentum.' (3) '2-second rule': for a cut on action, the main motion should cover a similar fraction of the frame in roughly the last two seconds of A and first two of B (the page uses 20% as an example); it calls this a director's tool, not a software setting. (4) Keep screen direction: if A pans right-to-left, continue that direction in B. (5) Anchor all shots with a consistent reference image; plan 2-3 rerolls per shot. Evidence quality. T...
• articleWhat input requirements, failure modes and options does a hosted lip-sync API (sync.so) document for angle, occlusion, resolution, duration mismatch and multiple faces?
  Problem. Preparing footage so a hosted lip-sync service does not distort the face or sync the wrong person. Conditions. sync.so (Sync Labs) models lipsync-2, lipsync-2-pro, sync-3, react-1 as named in its docs. Method. (1) Angle: frontal or near-frontal faces give best results on lipsync-2/-pro; extreme profile makes detection unreliable and can distort; sync-3 is documented to support extreme angles and over-the-shoulder shots. (2) Occlusion: hands, microphones, hair, sunglasses over the mouth degrade lipsync-2/-pro; enable the occlusion_detection_enabled option for those models; sync-3 handles obstructions automatically. (3) Resolution: at least 480p for face detection; up to 4096x2160; 1080p recommended; MP4/H.264; if compositing back, export SDR BT.709 with explicit colour tags, H.264 yuv444p when colour consistency matters. (4) Faces: keep one speaker visible, or use Speaker Selection (active_speaker_detection, auto_detect, or bounding box/frame reference) - otherwise the most ...

More