Production management

Scheduling, budgeting, asset tracking, review, collaboration and production automation

articleHow does the Comfy SDK's Idempotency-Key behave on retries (v2 API), and why is a naive retry loop around submit() a double charge?
Problem. Retrying a job submission without creating duplicate paid jobs. Conditions. Comfy SDKs (Python comfy_sdk, TypeScript @comfyorg/sdk) against Comfy API v2 (Comfy Cloud, a Comfy API deployment, or self-hosted via comfy-api-proxy). Method. The SDK guide states the v2 contract is reject-on-duplicate, not record-and-replay. Each submit() or run() mints a fresh key unless you pass idempotency_key, so two calls make two jobs and two charges. A reused key fails 422 idempotency_key_reuse (SDK exception IdempotencyKeyReuse); recovery means fetching the job by an id you stored earlier (client.jobs.get). The key is released after a definitive failure (validation error, out-of-credits, queue full) and stays claimed after an ambiguous failure such as a read timeout. Keys expire after 24 hours and must be non-empty printable ASCII. To retry safely persist both the key and the job id across attempts, and persist the id before doing anything else. The guide notes Comfy Router's key behaves d...
articleHow do library publishers describe temp music versus a licensed track, and what do their pages not say about screenings and the final cut?
Corrected 2026-10-23 - see C3-B622-03; the original statements below are kept for history and are superseded where the correction says so. Library pages describe temp use as a normal first step: Media Music Now says temp music can defer full licensing until the work circulates and that producers come back for the licensed version; Marmoset (2013 blog) offers unwatermarked lower-resolution MP3 downloads so people can try the real song before committing; a FirstCom executive describes temp-scoring a whole documentary from one library before a distribution deal. Media Music Now adds that temp music can end up in the finished film. None of the four library pages read says whether temp or preview use is itself licensed, or covers festival or pitch screenings, so that has to be asked of each library. The CBC and craft-side temp material is in C3-B102-G37-05 and C3-B031-G10-06/-07 and is not repeated.
articleCORRECTION to C3-B536-01: is TikTok Symphony's Dreamina Seedance access 'only' unlocked by $5,000 of advertiser spend in 30 days? (Overstated: agencies follow a separate process and an appeal route exists; some listed details are not on the cited pages.)
Problem. C3-B536-01's title says Seedance access in Symphony 'unlocks only when the linked advertiser ID spent at least $5,000 in the past 30 days (weekly refresh)'. Audit result against the two cited TikTok help pages (re-fetched 2026-10-23). (a) Supported: direct advertisers unlock automatically at $5,000 USD or more in the preceding 30 days; access is reviewed every Monday; the highest-spend linked advertiser ID counts; clips run 4 to 15 seconds depending on mode; daily generation limits scale with ad spend; the tool is described as free. (b) Overstated: 'only'. The same page says 'Advertising agency: access follows a separate process. Contact your TikTok representative to request access', and gives an appeal route for accounts that already meet the spend requirement but cannot generate. (d) Not found on the two cited pages: the Standard, Fast and Mini variant descriptions, the 'Real-human or AI-generated' avatar label, the shoes/hats/sunglasses limitation, and lip sync options. ...
articleCORRECTION to C3-B241-G73-03: is the 'term and territory defaults disagree' comparison across Wise Music, Atomica and Media Music Now like for like? (No: it mixes a per-quote form for web streams with library standard licences, and one cited page has no term text.)
Problem. C3-B241-G73-03 says the pages 'disagree on term defaults (no perpetuity vs perpetual vs unlimited)'. Audit result. (a) Supported facts: the Wise Music 2024 web-video form asks for the listed fields, offers one month, one year or other terms up to three years, says it will not grant perpetuity, defaults territory to world unless geo-blocked and asks for 4 to 6 weeks' notice; Atomica says licences state use, territory and term; Media Music Now's standard licence lists any territory and no time limitations. (c) Missing limitations: (1) the Wise form is titled a quote request for audiovisual in-context on-demand streams on websites and social channels, so its no-perpetuity rule is a quote condition for that use, not a general publisher default; (2) the same form states fees start at a minimum of $250 per work, are pro rata and MFN, and are subject to writer or estate approval, which the candidate does not relay and which affects what 'term' means in practice; (3) Atomica says o...
articleWhat checklist makes a hosted image or video render repeatable months later, and when should I give up on re-rendering and keep the originals?
Problem: hosted models are retired on vendor schedules. Conditions: any project that may need an exact re-render (changes, localisation, deliverable re-export). Method (inference from the provider documents in this round, plus C3-B609-02/06 for open weights): (1) record the exact model id string used, never an alias such as latest or chatgpt-image-latest; (2) record the provider API version (Runway header) and the date; (3) save the prompt, seed if the API exposes one, input images by hash, and the output file by hash; (4) store a poll of the vendor's shutdown signal (OpenAI shutdown_date; Google tables) with each project and re-check on a schedule shorter than the shortest notice (2 weeks for previews and latest-alias swaps); (5) for work that must be re-rendered bit-for-bit, prefer open weights pinned to a commit and run on your own hardware (see HF pinning); (6) for hosted-only models, treat the delivered master and the source frames as the archive and plan edits as new generatio...
articleWhat do Runway and Replicate version, and does a dated API version header pin the model I used?
Problem: 'pin the version' means different things per provider. Conditions: Runway API integrations; Replicate model pages. Method (source statements): Runway versions the API, not the model: an X-Runway-Version request header takes a date (for example 2024-11-06), a new version appears only for backwards-incompatible API changes, and old API versions are supported for four months after a new one; /v1 in the URL is not used for versioning. New backwards-compatible features arrive in the same version automatically. Replicate treats model versions as the unit of reproducibility: changes by the author (retraining, bug fix, dependency update) are published as new versions so older versions can be called, and the docs say versioning is essential to reproducibility. Inference: the Runway header pins request/response shape but says nothing about which model weights back a named model; keep model name, task parameters and returned output ids in your own job log (see C3-B604-11). For Replica...
articleWhat notice period does OpenAI promise before retiring a model, how can I read shutdown dates by API, and what happened to its image and video models (DALL-E, GPT Image, Sora 2)?
Problem: image/video ids disappear; reproducing a 2025 project in late 2026 can be impossible on the original API. Conditions: OpenAI API users. Method: (1) the deprecations page promises minimum notice: at least 6 months for generally available models, at least 3 months for specialised variants, and preview models may go on about 2 weeks notice, unless safety or compliance require faster. (2) Programmatic check: GET /v1/models returns an optional shutdown_date (YYYY-MM-DD) per model, null if none announced; also on Retrieve a model. (3) Recorded history: DALL-E 2 and 3 shutdown 2026-05-12; the Videos API and sora-2, sora-2-pro and dated snapshots (sora-2-2025-10-06, sora-2-2025-12-08, sora-2-pro-2025-10-06) shutdown 2026-09-24 with no replacement listed; gpt-image-1-mini, gpt-image-1.5 and the alias chatgpt-image-latest shutdown December 1, 2026. Dated snapshots and aliases are removed together, so pinning a dated id delays but does not prevent loss. Failure modes: not every table ...
articleWhich Google image and video models (Imagen 4, Veo 2/3/3.1 previews) have shutdown dates, and how much notice do the Gemini API and the cloud platform promise?
Problem: a project made on Imagen 4 or Veo 3.0 may not re-render at all months later. Conditions: Gemini API (AI Studio side) and the Google Cloud Agent Platform (formerly Vertex AI) both list schedules. Method: read both tables. Gemini API: imagen-4.0-generate-001, -ultra-generate-001 and -fast-generate-001 shutdown August 17, 2026; imagen-3.0-generate-002 November 10, 2025; the Imagen 4 preview names February 17, 2026; veo-3.0 and veo-2.0 June 30, 2026; veo-3.1 preview names October 22, 2026 (replacement named: gemini-omni-1.1-flash and, for Veo, the GA models on the cloud platform). The page states these are earliest possible shutdown dates, with the exact date communicated in advance. Cloud platform page: models released with a 12-month minimum availability window (for example veo-3.1-generate-001, retirement November 17, 2026 or later; gemini-3.1-flash-image May 28, 2027 or later; gemini-2.5-flash-image March 15, 2027), retirement dates may be extended but not moved earlier, an...
articleWhat do Gemini API model-name patterns (stable, preview, latest, experimental) promise, and which should a reproducible image or video project pin?
Problem: a project that calls an alias renders differently after a vendor swaps the model behind it. Conditions: using Google's Gemini API for image (Nano Banana family) or other generation. Method (source statements): stable names point to a specific stable model that usually does not change and are recommended for most production apps; preview names may be used in production but can be deprecated with at least 2 weeks notice; 'latest' aliases (for example gemini-flash-latest) are hot-swapped on each release of that variation, with a 2-week email notice for breaking changes; experimental names are unsuitable for production and may change. Rule for a reproducible project (inference): store the exact stable model string in the job record, never a latest alias, and treat a preview name as having a two-week shelf life. Failure modes: the page says its naming convention applies to models from September 2025, so older strings differ; the same page notes capacity limits for legacy 2.5 mod...
articleWhat checklist should a newcomer agent follow to prepare a music clearance request and a cue-sheet hand-off, and which steps are documented versus proposed?
Corrected 2026-10-23 - see C3-B683-04; the original statements below are kept for history and are superseded where the correction says so. A checklist assembled from the pages read: each step is labelled documented (a source states it) or proposal (my synthesis). Documented steps: ask for the full intended use with portion, timing, platform, paid-media, term, territory, date, budget and number of works; allow 4-6 weeks; treat quotes as estimates until holders approve; expect broadcast and streaming to need extra detail; keep the licence certificate; treat temp as not-yet-licensed; deliver cue sheets, performer agreements and executed licences. Cue-sheet fields and filing timing are not in these pages: use C2-B12-C2-07 and C3-B102-G37-03/-04. The checklist reports what sources say and is not legal advice.
articleHow does Beat v2.1.18 turn its script tags into Final Draft tag categories, and how complete is that feature according to its own source and README?
Corrected 2026-10-23 - see C3-B686-03; the original statements below are kept for history and are superseded where the correction says so. Beat's source (v2.1.18 era) contains an FDX tag writer and reader mapping its 15 tag types (cast, props, VFX, special effects, camera, animals, extras, vehicles, costume, makeup, music, sound, stunts, set design, generic) to Final Draft categories, but the author calls tagging nearly working and the README lists tags as 'soon' and warns the repo does not match released versions. Treat Beat FDX tags as unconfirmed in shipping builds. Code is GPL-3.0-or-later.
articleIn Trelby 2.4.16.2, which Fountain and FDX elements survive import and export, and which production reports does it generate?
Corrected 2026-10-23 - see C3-B686-02; the original statements below are kept for history and are superseded where the correction says so. Trelby's manual (86079b16) documents Fountain import losses (no emphasis markup, dual dialogue split into two dialogues, sections/synopses as notes, title pages and page breaks as action) and FDX import of text and script notes only (Final Draft 8 files, no formatting); its generateFDX writes element types and text without scene-number attributes. The manual's intro says 'three' import formats but lists six.
articleHow should headless CI wait for a ComfyUI workflow and what exit-code traps does comfy-cli document?
Problem: scripting comfy-cli in CI and getting trustworthy exit codes. Conditions: comfy-cli at commit 0b49c62. Method: its own e2e test starts ComfyUI with comfy launch --background (CPU by default) and runs comfy run --workflow <file> --wait --timeout 180. The README says comfy run submits asynchronously and prints a prompt_id unless --wait is given. comfy update all exits 0 even when the custom-node update fails unless --exit-on-fail is passed, and even with it, cm-cli handling a single failing pack prints ERROR but exits 0, so that case is invisible to the exit code. comfy run --prompt without --workflow uses a bundled graph needing the SD1.5 checkpoint, which comfy-cli does not download. Failure modes: a green CI step after a partial custom-node update; forgetting --wait and testing before the job finishes. Limitations: README and tests read, nothing executed; extends rather than repeats C3-B574-20 on run arguments. Version/date: 0b49c62, 2026-10-23.
articleWhich workflow settings multiply or divide GPU cost per job in ComfyUI: CFG 1, regional sampling, recovery samplers, cached partial re-runs?
Problem. Two workflows with the same steps and resolution can differ by a large factor in model evaluations. Conditions. ComfyUI core samplers.py at 9fe7ef76; Impact Pack Regional Sampler tutorial (default-branch text, no commit id); a Wan 2.2 end-frame example. Levers. (1) CFG 1.0: in the sampler, when cond_scale is close to 1.0 (and disable_cfg1_optimization is not set) the unconditional branch is dropped, so each step evaluates the model once instead of twice (inference: count of passes; see C3-B582-05 for why negatives then do nothing). (2) Regional Sampler: a base-only stage runs base_only_steps, then each step does base-region sampling plus one sampling per region, and the tutorial states that the optional additional_mode recovery 'requires a longer time for sampling because a second sampling is performed at each step in each region'. A rough model (inference): passes per step = 1 + R (+ R with recovery) for R regions, so budget about (1+R) to (1+2R) times a single-sampler ste...
articleWhat element categories does a script breakdown use, which colour is traditionally attached to each, and do sources agree?
Corrected 2026-10-23 - see C3-B688-08; the original statements below are kept for history and are superseded where the correction says so. Two software-vendor guides agree on the category set but disagree on several colours (vehicles pink vs green; animals pink vs amber/plum; extras/background split vs merged); one calls the colours a convention, not a law. Bytes match producer pins.
articleHow do YouTube's Shorts and long-form analytics differ: which reports are format-specific, what is 'Stayed to watch', and how are views counted from 24 August 2026?
Problem: mixing Shorts and long-form numbers when judging a hook or edit. Conditions: channel-level Content tab in YouTube Analytics, with chips for All, Videos, Shorts, Live, Posts, Playlists and Podcasts. Method: use the chip that matches the format. Long-form (Videos) shows a key-metrics card with views, average view duration, impressions and impressions CTR, plus the key-moments retention report. Shorts shows views, likes and subscribers, how viewers find Shorts (Shorts feed, search, channel pages), a 'How viewers engaged' panel and 'Stayed to watch', defined as the percentage of times viewers stayed past the initial seconds of a Short. 'Engaged views' counts viewers who stayed past the initial seconds and excludes loops; average view duration is computed from engaged views. 'Viewers across formats' shows overlap between videos, Shorts and live. The page states that from 24 August 2026 views are counted the moment a video starts to play in all formats, while Partner Program earn...
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...
articleWhat length, style and purpose does Phillips (1914) prescribe for the synopsis, how does his specimen synopsis measure against his own figures, and how do his numbers compare with the 250-word and later figures in Esenwein and Leeds?
Phillips defines the synopsis as an abridgment of the scene contents, to be 'terse, crisp and suggestive', reduced from thousands of words of scenario to a few hundred. He reports a studio convention of 250 words, but declines to make it a hard rule: clean plots can be told in fewer than 100 words, subtle plays need more, and the instruction is to use as few words as you can. Its job is first to sell the manuscript to a hurried editor and then to guide the director. By my count the specimen's own synopsis is 442 words, well over the 250 convention. Esenwein and Leeds (as relayed) record the same 250-word convention as an earlier-era demand and, in 1919, 'as many words as are really needed', plus 150-250 words for a short second synopsis and 6-12 typed pages for features. Label: 1914 practice. Excerpts drop Gutenberg italic underscores and collapse line wraps.
articleHow does Phillips (1914) define a photoplay scene, when must a new scene number be used, what shape and length must a scene have, and does his specimen follow his numbering rule?
Phillips defines a photoplay scene by the camera, not the stage: all the setting and action photographed without stopping or changing the camera position. Move the camera 'an inch', or return to the same setting a score of times, and it is a new scene with a new number; the one exception is a scene broken by an insert or close-view, which is 'continued' under the same number. Each scene has one desired effect and its length is exactly the time needed to reach it: introduction, rising development, a climax that ends it, no denouement. He would prefer to call scenes 'acts'. The specimen follows the numbering pattern: 40 numbers, 7 '(CONTINUED.)' repeats, 19 'SAME AS' returns. Label: 1914 practice. Excerpts drop Gutenberg italic underscores and collapse line wraps.
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.
articleWhich parts does Phillips (1914) say a photoplay manuscript consists of, in what order does he list them, and where do his own lists disagree with each other and with Esenwein and Leeds?
Phillips's Chapter III heading names seven items (Title; Synopsis; Cast of Characters; Author's Remarks; Scenario; Scene; Scene-Plot) and the chapter treats the first five in that order, then the scene as a unit, but never describes a scene-plot. Three other lists in the same book order the parts differently: the contents page ends 'the Scene; the Setting', the glossary 'Manuscript' entry gives synopsis, cast, scene-plot, remarks, scenario, and the specimen puts the title and synopsis on one sheet, remarks, scene plot and cast on a second, and the scenario on a third. Against Esenwein and Leeds as recorded in C3-B188-S42-01 the two agree that the synopsis leads, the cast is its own part and the scenario is the scene-by-scene part; they differ on Author's Remarks (Phillips only) and on whether the scene-plot is a regular part or a supplement. Label: 1914 practice, Second Edition text published September 1914. Excerpts drop Gutenberg italic underscores and collapse line wraps.
articleWhat does Phillips (1914) prescribe for the scenario: its content, the setting line, tense, how much the writer may direct, and how do his specimen and Esenwein and Leeds's scene counts compare?
In Phillips the scenario is the enumeration of scenes with the action in each. After the scene number a single line names the setting (one or two words unless the arrangement has dramatic bearing), and that line is 'the only space permitted' for description. The action is told in the present tense, tersely, with every scene essential to the cumulative advance of the play; the writer says what is done, not how, though a happy suggestion may save actor or director time. Examples 6-8 are illustrations, not rules. The specimen scenario has 40 numbered scenes in one reel, inside the 25-50 scenes per reel that Phillips himself gives in Ch. VIII (outside Ch. III) and that Esenwein and Leeds give (via C3-B188-S42-03); Ch. III states no scenes-per-reel figure. Label: 1914 practice. Excerpts drop Gutenberg italic underscores and collapse line wraps.
articleWhat is the 'Author's Remarks' part of a 1914 photoplay manuscript, what may go in it and how long may it be?
Phillips requires a distinct part of each manuscript called Author's Remarks, brief, 'confine these remarks to 50 words or less', for helpful suggestions: the period of the play, its locale, where ideal locations may be found near particular studios, extraordinary properties and where they might be obtained, and specific actors the author has in mind. The specimen's remarks are 37 words and propose a staged bridge for the explosion scene. The part is not in the four-part list of Esenwein and Leeds as relayed in C3-B188-S42-01, so it is a Phillips-specific part within the rows compared. Label: 1914 practice. Excerpts drop Gutenberg italic underscores and collapse line wraps.
articleWhat does Phillips (1914) say a photoplay title is for, what tests does he give it, and what does he say about its length or form, compared with Esenwein and Leeds on titles?
Phillips treats the title 'chiefly as a commercial asset' and gives it three tests posed as questions: will it attract the hesitating public and the poster in front of the theatre, will it compete among the many releases an exhibitor chooses from, and, 'in a lesser degree', will it appeal to the photoplay editor. He says all three can be met in nine cases out of ten with careful thought, and gives no length, no quality list and no form for titles within lines 846-1025. Esenwein and Leeds (via C3-B286-S94-01) share the advertising-to-the-public function and the editor as reader, add a five-attribute list and a do-not-reveal-the-climax rule, and likewise give no length number. Label: 1914 practice. Excerpts drop Gutenberg italic underscores and collapse line wraps.
articleWhat does Phillips (1914) say the cast of characters must contain and who uses it, what format does he show, and how does it compare with the cast list in Esenwein and Leeds?
Phillips says the cast should give each character's individual characteristics where possible and show relationships at a glance, because the director uses it to count players and choose actors by talent and personal type; singles are listed singly and groups or mobs en masse, so the director can judge the outlay in players, costumes and character props. Example 5 shows the format: NAME, a dot leader, a role type such as (Lead) or (Ingenue-lead), another dot leader and a trait phrase. His specimen cast uses a different layout (dash, no dot leaders, role type on only 2 of 6 named entries) and lumps ten minor roles on one line with no scene numbers. Esenwein and Leeds (as relayed) tag minor characters with scene numbers and keep the cast right after the synopsis. Label: 1914 practice. Excerpts drop Gutenberg italic underscores and collapse line wraps.
articleHow do I use YouTube's 'When your viewers are on YouTube' report and the other Audience-tab reports to choose publish and live-stream times and topics?
Problem: choosing when to publish or go live without folk wisdom. Conditions: YouTube Studio > Analytics > Audience tab; data windows are fixed by the report. Method (documented): 'When your viewers are on YouTube' shows when your viewers are online across YouTube in the last 28 days and is suggested for building community, picking a Premiere time and planning a live stream. Related Audience-tab reports: monthly audience (unique viewers in the previous 28 days, recalculated daily); channels your viewers watch outside yours (28 days) for collaboration ideas; other videos, Shorts, live streams and podcasts they watched outside your channel (past seven days) for topics, titles and thumbnail ideas; and a formats-watched report (28 days) for deciding between videos, Shorts and live. Failure modes: treating the online-time grid as proof that publishing at that time raises views; the page makes no such claim. Limitations: the page reports no evidence that upload timing changes performance;...
articleWhat do YouTube's playlist and Posts (community post) help pages document that matters for series packaging and audience contact, and what do they not say about session watch time?
Problem: planning a series playlist and companion posts. Conditions: desktop YouTube and Studio. Method (documented): playlists can hold videos and Shorts; creators can reorder them by dragging (not for Shorts-only playlists), filter by All/Shorts/Videos, and there is a daily limit on public playlists a channel can create, raised by advanced features. Deleting a playlist removes its URL and title from Analytics and stops attributing watch time to it, though the watch time stays in broader reports. Posts can be text, image/GIF (up to 10 images, JPG/PNG/GIF/WEBP, up to 16 MB, a suggested 1:1 ratio because that is how the feed shows them), video, poll, quiz or playlist posts; they can be scheduled; mentions with @ may notify the channel; a post sharing another creator's video may notify them; a posts-per-24-hours limit applies; and a post about a video already in a viewer's feed might not show again. Failure modes: expecting analytics for a playlist after deleting it; sharing a viewer'...
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...
articleWhat do public sources say a scout must establish about permits, neighbour notification and parking or base space, and who does that work?
The California Film Commission guide says many jurisdictions require notification of affected residents or merchants and some require approvals from a percentage of neighbours within a radius set by local ordinance; it also gives a planning scale of 10 to 25 equipment trucks and 60-95 automobiles for an average feature, and describes reserving street parking with no-parking signs 48 hours ahead. ScreenSkills assigns the location manager to liaise with residents, hold resident meetings, confirm filming with the local authority and police, and obtain permission for parking suspensions or road closures. A trade article quotes a New York location manager on hiring parking assistants to hold parking 24 hours ahead. All figures are local and reported, not rules.
articleWhat should a location scout and a tech scout record at a site (access, power, sound, light and time of day, permits, safety, neighbours, holding areas), and which items are documented rather than synthesised?
No single public form was found that covers all eight topics. A checklist can be assembled from five documents: the California Film Commission owner-facing guide (access, power, parking, restrooms, neighbours, notification, holding areas in its monitor checklist), a practitioner tech-scout checklist (sun path, basecamp, holding, power, sound, hospital, phone reception), ScreenSkills job descriptions (permits, residents, parking suspensions, health and safety files, movement orders), a Disney pre-scout safety checklist (hazards before a Director's Scout) and a trade article (conflicting needs of camera and sound). The table below marks each item documented (source) or synthesised (no source says it).
articleWhat is the difference between a location scout and a technical scout (tech recce), when does each happen, and who attends?
Public sources describe two stages. The location scout (usually the location scout or manager alone, with photographs and notes) finds and screens sites against the script; the technical scout (UK: tech recce) is a later visit by department heads to a shortlisted site. The California Film Commission (April 2024 revision) names the tech-scout attendees as director, first AD, unit production manager and production designer or art director plus other necessary personnel; ScreenSkills (2023) says the location manager arranges designers and directors to recce and assembles a tech recce pack and schedule with the first AD; a practitioner article puts the tech scout about a week before shooting. Attendee lists differ by source and production size; none of these sources is a standard.
articleI have a breakdown or shooting schedule in a production tool; which export format should I pick to hand it to another tool or a person, and what do the vendors say that format carries?
Filmustage documents export to Movie Magic Scheduling as MMSX (MMS 10+) and SEX (MMS 5/6) plus XLSX and PDF, but its two help articles give different file extensions for the same formats: the schedule article says MMSX saves as .MMS10 and SEX as .MMS, the summary article lists .mmsx and .sex. Movie Magic Scheduling 10's own manual exports .msd (MMS6) and .mbl (for Budgeting).
articleIn a dailies workflow, which identifiers must match so synced sound, burn-ins, colour (CDL/LUT) and metadata land on the right clips in editorial?
Partially verified: the curator re-read S28, S33, S35, S39; S29, S30 were not re-read by the curator and rest on the producer's pinned reading. Dailies tools join data on different keys: Silverstack Lab syncs audio to picture by timecode with audio and video in separate bins; Avid matches ALE metadata to MXF dailies by tape name (or source file name) plus timecode, so the transcode preset tape name must equal the ALE's or relink fails; Resolve applies Silverstack CDLs via EDL plus CCC matched by reel name, which ARRI composes from camera index, reel counter and camera ID.
articleHow do Unity text-serialised scenes/prefabs support merging, and what does the UnityYAMLMerge tool document about clean versus unclean merges?
Corrected 2026-10-23 - see C3-B642-09; the original statements below are kept for history and are superseded where the correction says so. Unity scenes are a custom YAML subset with one document per object (--- !u!<class> &<fileID>) and in-file {fileID: n} references, floats optionally in IEEE 754 hex for lossless values; UnityYAMLMerge merges scenes and prefabs semantically, with Smart Merge Off/Premerge/Ask, a mergespecfile.txt fallback and documented Git/Mercurial/P4V/SVN configuration. Unmergeable cases and .meta/GUID handling are not described on these pages.
articleBefore I put AI-generated Foley into a delivery, what per-component rights and provenance checks do the sources imply an audio post agent must make?
A synthesis from the pinned licences and cards: (1) record model, checkpoint and revision; (2) read the weights licence (CC BY-NC, Tencent community licence with Territory limits, or conflicting statements) against the delivery's commercial status; (3) check output clauses (Tencent: no ownership claim but no use to improve other AI models and no use outside the Territory); (4) check each auxiliary component (VAE, Synchformer, vocoder, CLIP) for its own licence; (5) note training-data statements the card disclaims (MMAudio) or omits (HunyuanVideo-Foley paper); (6) log provenance marks (Google V2A research applies SynthID; Veo 3 card cites SynthID) and any required notices; (7) escalate conflicts to a human rights owner. This is a checklist proposal, not legal advice.
articleWhat do the safety bulletins say about overhead power lines, lighting rigged on aerial lifts, 480 V systems and PPE for lighting tasks, and where do they disagree?
Partially verified: the curator re-read S19; S15, S16, S17, S18 were not re-read by the curator and rest on the producer's pinned reading. Bulletin #22 (2017) allows lighting, camera and diffusion rigged onto boom-lift guardrails only within manufacturer limits with extra training (otherwise not at all), prohibits lifts over energised high-voltage lines, and says rigged lifts should not be operated over low-voltage lines (600 V or less). Clearance tables are in an Addendum A that #22 names as '#22 Addendum A' while the web URL labels it 23a (naming inconsistency kept).
articleWhere do public set-safety documents cover how lighting is suspended or rigged, and what does the UK HSE entertainment electrical guidance add?
Partially verified: the curator re-read S14, S19; S15, S20, S21 were not re-read by the curator and rest on the producer's pinned reading. The CSATF bulletin set has no dedicated bulletin on overhead lighting rigging, truss or hoists (producer index check); rigging rules appear inside the lifts bulletin and general code. UK HSE GS50 gives concrete points (do not hang fittings from flexible cable alone) but was not re-read here.
articleWhat does Avid's ALE documentation define for dailies handoff, and how does the ACES AMF guide extend it for AMF linkage (and where is that guide inconsistent)?
Corrected 2026-10-23 - see C3-B688-09; the original statements below are kept for history and are superseded where the correction says so. An Avid Log Exchange file (per the 1999 MediaLog guide) is tab-delimited text with a Heading section of global settings (FIELD_DELIM TABS, VIDEO_FORMAT NTSC or PAL and AUDIO_FORMAT are required; FPS shown in the sample), a Column line naming fields such as Name, Duration, Tracks, Start, End and auxiliary timecode, and Data rows per clip.
articleHow do Nigerian directors and producers say, in their own words, that 2024 inflation changed budgets, locations, catering and shoot cadence?
Corrected 2026-10-23 - see C3-B688-01; the original statements below are kept for history and are superseded where the correction says so. Nollywood filmmakers quoted in a 2024 feature describe inflation-driven overruns (one budget rising to 19 million naira), negotiating daily location fees down for longer stays, cutting crew feeding, and a fast cadence of about two films a month at low budgets; these are reported quotes, not cost surveys.
articleDo the open scheduling tool's breakdown categories match the standard set including cast, and are its colours breakdown-sheet convention?
Problem. C2-B36-Z1-01 says two vendor guides and one open scheduling tool (OpenShotDesigner) agree on a category set that includes cast, and that colours differ between sources. Correction (overstated for the open tool). At commit 766a80d the tool's breakdown model deliberately excludes people and places ('not a person or a place'), has no cast category, adds separate VFX and Other categories, and its per-category colours are named 'tint' display values with no claim to follow a breakdown-sheet colour convention. It cannot be used as a third witness for a traditional category-to-colour map. Limitations. Vendor guides were not re-read in this audit (not in the cited URL list). Version/date. Commit 766a80d.
articleDoes the Afrocritik feature show Nigerian practitioners saying, in their own words, that inflation changed shoot cadence and catering?
Problem. C2-B122-X13-01 says three practitioners describe how 2024 inflation changed budgets, catering and cadence, and that the quotes are the interviewees' words. Conditions. Reading the Afrocritik feature of 2024-03-28. Correction. (1) Meal-cutting is quoted from Wingonia Ikpi about 'producers' in general; the in-house cooks and bulk buying passage is the journalist's narration about 'others', not a quote from any of the three named people. (2) The two-films-a-month, two-million-naira cadence is Belinda Yanga-Agedah arguing that production carries on regardless; the article says she does not think much is different. The source therefore shows a practitioner denying an inflation-driven cadence change, and gives no shoot-day counts or crew sizes. Limitations. Single journalist-mediated article; figures are in naira, undated per item. Version/date. Article dated March 28, 2024; fetched 2026-10-23.
articleMedia business literacy from an author channel: why "bestseller" is everywhere (list segmentation, print-run skew) and what a 2026 studio adaptation deal looked like from the IP holder's side
Creator-reported: statements attributed to the creator(s) come from discovery's reading of auto-caption transcript excerpts; the curator checked the video metadata (title, date, length) and any cited documentation pages, not the spoken claims. Nothing was tested; promotional or sponsored framing applies where stated. R4 (Sep 2026, 3.4M views - the channel's top in-window upload): the common claim that lists are easily gamed is mostly wrong (BookScan gives sales counts; NYT, USA Today and BookScan rank within a few places of each other). Real reasons "every book is a bestseller": many segmented lists (NYT splits YA/adult, formats, fiction/non-fiction, graphic novels; USA Today is unsegmented; Amazon sub-sub-category lists mean less); the frequency illusion; and above all print-run skew - a mega-seller run of ~400,000 copies vs ~10,000 lifetime hardcovers for a non-bestseller means most copies on shelves are bestsellers. Legit tactic: release in a low-competition month (February vs No...
article"Face swap any video" tutorials and permanent digital personas: what the workflow enables and the consent/disclosure lines it crosses
Creator-reported: statements attributed to the creator(s) come from discovery's reading of auto-caption transcript excerpts; the curator checked the video metadata (title, date, length) and any cited documentation pages, not the spoken claims. Nothing was tested; promotional or sponsored framing applies where stated. Youri van Hofwegen (2026-02-19, R4) demonstrates replacing his own face in recorded video with a generated person (Nano Banana Pro for the identity frame, then a video tool with lip sync), auto-captioning, and then making that synthetic person "perform" trending dances and scripted ads so a "permanent digital influencer" can work "for free". Assessment: swapping one's OWN performance onto a fictional face is legal in many places but still realistic synthetic media that platforms require to be disclosed (TikTok C3-B398-01; YouTube altered/synthetic disclosure), and EU AI Act Art. 50 may require visible deep-fake disclosure for professional/monetised use (C3-B426-01). Swa...
articleRunning synthetic "AI influencer" accounts (Feb-Jun 2026 creator practice): consistency methods, a local dashboard, and the disclosure obligations creators tend to skip
Creator-reported: statements attributed to the creator(s) come from discovery's reading of auto-caption transcript excerpts; the curator checked the video metadata (title, date, length) and any cited documentation pages, not the spoken claims. Nothing was tested; promotional or sponsored framing applies where stated. Dan Kieft says he runs about five AI-influencer pages, some with millions of impressions a month, and built a free local dashboard that stores nine personas (each in a niche, e.g. a yoga instructor) and one-click generates character sheets, close-ups and "feature" sheets, then scenes for posting (R3). Consistency methods (R2): detailed prompts for skin texture and imperfections to avoid a plastic look; generate a background grid with the character as reference and upscale a chosen panel; edit with "keep the exact same person, face, skin texture, expression, pose, background, proportions and camera framing" and change only clothes or pose; pose transfer by giving two ref...
articleWhat fields and owners do public training templates assign to the call sheet, daily production report and camera report, and which of those fields feed later documents?
Partially verified: the curator re-read S20, S22, S24; S23, S26, S27 were not re-read by the curator and rest on the producer's pinned reading. A film-school camera report (FSU) gives field-level capture provenance: the people responsible (director, DP, 1st AC, 2nd AC), roll/media and camera IDs, file format, project frame rate, framing aspect and LUT, and per take the scene, take, clip name, lens, f-stop and filter/remarks. It is one school's template, not an industry standard.
articleComparison of four period accounts by candidate ID, built from Sargent's pinned chapter and the other accounts' published candidate records (their texts were not re-read; wording is theirs). Fifteen items: agreement in direction on crime as conditional, suggestion over depiction, a...
Comparison of four period accounts by candidate ID, built from Sargent's pinned chapter and the other accounts' published candidate records (their texts were not re-read; wording is theirs). Fifteen items: agreement in direction on crime as conditional, suggestion over depiction, a young-audience concern, cold blood, avoiding the underworld, and local gates being harsher; differences in the body's name, how its role is described, tone toward it, and the test for acceptable crime; Sargent's unique points are board timing (first print before the cut negative) and the repentant-woman pattern; the 1919 list items (suicide, mischief, lynching, kidnapping) have no counterpart in his chapter. Differences in breadth are differences between authors, not evidence that practice changed.
articleHow long does fal retry a failed webhook? Correction: about 1 hour after the request completes, but only about 6 minutes for results of 10 KB or more, up to 31 retries.
Problem. The earlier finding gave the retry window as 'about 1 hour after the request (as stated on the page)'. The page as fetched on 2026-10-23 is more specific. Method. Retries use increasing backoff until the stored result expires: about 1 hour after the request completes, or about 6 minutes for results of 10 KB or more, with a maximum of 31 retries. First delivery has a 15-second timeout; retried deliveries have 120 seconds. Redirects (3xx) are a permanent failure. Large results (over 1 MB) and requests with payload storage disabled can only be fetched until the stored result expires. Failure modes. A handler that is down for 10 minutes can lose a 10 KB+ result's webhook deliveries entirely; design handlers to be idempotent per request_id and poll the queue as backup within the retention window. Limitations. Docs page, undated; the page changed or was more precisely read since the earlier note (cannot tell which).
articleDoes YouTube's fake engagement policy ban offering a reward for likes, subscribes or comments, or just asking for them?
Problem: giveaways and 'like to unlock' mechanics. Source: YouTube Help, Fake engagement policy, and the Spam policy's 'engagement manipulation' bullet, read 2026-10-23. Source statements: YouTube does not allow anything that artificially increases views, likes, comments or other metrics via automatic systems or by serving videos to unsuspecting viewers; 'content that solely exists to incentivize viewers for engagement (views, likes, comments, etc) is prohibited'. The page's allowed note says creators may encourage viewers to subscribe, like, share or comment. Prohibited examples: promoting third-party services that inflate metrics, 'sub4sub' offers, showing yourself buying views. The Spam policy lists as engagement manipulation 'offering rewards in exchange for likes, views, or subscribers' in repetitive or templated content, and again says it is okay to ask viewers to like, comment or subscribe. Reading (inference): asking is allowed; an explicit reward-for-engagement scheme, espe...
articleIn a 1916 studio's manuscript department, who handled an incoming script and in what order?
Sargent (Ch. II, flat 22203-32390) describes an Editor with clerks and staff writers. An assistant reads incoming scripts first and discards the unfit; he says about eighty per cent stop there. The rest go to the Editor for a second reading, then to one of three disposal routes. Only the third route (weekly directors' conference) is described as synopsis first, then the action plot.
articleHow long did a script wait in a 1916 studio, and who could actually say yes?
Ch. II gives no turnaround figure. It says directors may keep stories 'weeks and even months', an Editor may hold one for some weeks, the Editor seldom can buy without consulting the director, and status inquiries are generally unanswered and may cause rejection. This is a negative result for a numeric time limit.