Production management

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

• articleHow does a working Nigerian screenwriter describe story development, writers' rooms and the writing-to-shoot sequence in Nollywood?
  A working Nollywood screenwriter (2024 Q&A) describes series writers rooms (storylines assigned, notes, head writer assigns scripts; staff/invited writers, story editors, head writer), mostly solo writing for films, writing that starts only after schedule, budget and fees are settled (money is the main hold-up), commission drafts in one week to a month, and a page-per-minute rule with no standard length (70-140 pages).
• articleWhat does a Ghana-shot independent short's producer/co-director say about low-budget planning, crew, and the producer role on set?
  A Ghanaian producer-director-actor says low budgets demand intentional, planned shots and a crew that shares the vision, and describes tracking budget use and crew welfare (being fed) while also acting; no budget figures are given.
• articleI am new to review: what is a timeline marker or annotation in OTIO, RV, Kitsu and an EDL, and which one holds a frame-accurate note?
  A frame note is stored differently in each tool: RV keeps per-frame paint and markers as node properties, Kitsu keeps text comments as their own records while drawn annotations live as JSON on the preview file, and a CMX3600 EDL can carry only comment lines such as '* LOC: timecode colour text'; no shared note identifier links them, so round trips need a mapping table.
• articleWhat does an FDX file carry for breakdown tagging versus what the Scheduling Export (.sex) path carries, and is there an open specification?
  Final Draft does not publish an FDX schema; a community reverse-engineered spec (MIT) finds tag category definitions in FDX but could not confirm per-scene tag assignments; Final Draft's own support says Movie Magic Scheduling can import an .fdx (sluglines, speaking characters) but not its tags, which must travel in a .sex export whose format no inspected page documents.
• articleIs a call sheet the same as a daily production report, and do public agencies publish production-report templates with field definitions?
  Call sheets and production reports are different documents for tax-credit evidence: New York requires the daily production report (front and back) summarising each day and refuses call sheets as substitutes; California requires a UPM-signed call sheet for the first day of principal photography and UPM-signed production reports for every day, submittable weekly in arrears. Neither lists the report's fields.
• articleHow does an open scheduling tool derive stripboard strip colours and a Day Out Of Days (DOOD) chart, and which status codes does it use?
  One open scheduling tool (OpenShotDesigner, GPL) colours strips white for INT/day, pale yellow for EXT/day, pale blue for INT/night and pale green for EXT/night, and builds day-out-of-days cells with SW, WF, SWF, WD (drop) and PW (pick-up) codes; its comments call these industry codes and attribute a one-drop/pick-up rule to SAG-AFTRA, which this review did not check against union or payroll documents.
• articleWhat do Sony's public help-guide pages state for FreeD (free-d D1) tracking-data output on the BRC-AM7 and ILME-FR7: ports, Camera ID, destinations, position fields and delay conditions?
  Sony's BRC-AM7 PTZ outputs free-d D1 camera tracking to up to four IPv4 destinations (port 1024-65534, default 40000) with a settable Camera ID (0-255, default 255) and a manually entered camera position, and output may lag in some modes; the FR7 outputs both free-d D1 (lens encoder, iris, position, orientation) and OpenTrackIO (adding focal length and entrance pupil position), synchronised to the sync signal.
• articleWhich continuity and report documents do script-supervision job descriptions and training outlines say go to editorial, production, camera and VFX, and where do they disagree?
  Script supervisor paperwork serves two audiences: editorial (marked-up/lined script pages, editor's daily log, facing pages, selects or print log, VFX notes) and production (timings and page counts for progress reporting). ScreenSkills assigns these to the supervisor; IATSE Local 634 gives the editor's lined script and page recalculation to the script assistant. No source publishes field-level templates.
• articleWhat does the Hollywood Industry-Wide Labor-Management Safety Committee's portable-power bulletin say lighting crews must do on set, and how binding is it?
  CSATF Bulletin #23 (2013, recommended guidelines, not law) says only authorised employees connect or operate distribution, rig de-energised and check for shorts before energising, connect grounds, neutrals then phases (reverse to disconnect), avoid tie-ins to energised premises power (qualified person required), never use alligator clips, and use GFCI protection for non-double-insulated tools on construction sites.
• articleWhat does an ASC CDL carry (SOP + saturation, .cc/.ccc/.cdl) and how do tools differ in applying it from set to post?
  An ASC CDL is ten numbers (slope, offset, power per channel plus saturation); the v1.2 math clamps to [0,1], but many applications omit clamping, so CLF defines clamped and no-clamp styles and OCIO defaults to no-clamp; the same CDL can therefore render differently across tools, and a CDL names no colour space (ACES AMF adds a cdlWorkingSpace, per producer reading).
• articleWhat exactly do Silverstack's audio sync, burn-in and metadata-export settings do, and what are the documented limits?
  Silverstack Lab syncs external audio by timecode with an auditable preview and offset controls, but an ALE handed to editorial does not reflect half-frame audio offsets, and metadata export after transcoding (like dynamic-metadata burn-ins) is Lab-only, so Silverstack XT users lack it. No page reports sync accuracy.
• articleHow is a union rate sheet structured (panels, schedules, daily vs weekly, guarantees, overtime), using a public ICG Local 600 rate card as the example?
  A union rate card is a structured table, not a single hourly rate: the ICG Central Region 2024-2025 card has panels by production type, several defined as percentage reductions of Panel 1 (3%, 10%, 12.5%), schedules with daily vs weekly guarantees and overtime triggers (e.g. time-and-a-half after 8 hours) that vary by schedule, plus effective dates and region. It is PDF-only.
• articleWhich fields and formats do production-budget tools actually exchange (Movie Magic Budgeting exports, account codes, accounting links), and where does data drop out?
  Movie Magic Budgeting exchanges budgets as .mmbx/.mbd, a stable XML (Basic) export and fuller XML (Advanced)/JSON exports, without a published field schema in the pages read; exporting to MMB7 loses Budget Info and notes, and account numbers are truncated or padded to the coding pattern, which can break accounting imports. The account number string is the only shared key across tools in these sources.
• articleWhat exactly does Shotcut v26.9.27 write in an EDL export, and could proxies change the reel and clip names in it?
  Shotcut's EDL exporter writes one section per playlist with cuts and dissolves from program time 0 and no header lines; by default the reel name is the media base name (cut at the first dot, non-word characters replaced, padded or truncated to 8 characters), so files sharing their first eight characters collide; an option uses the stored hash instead. With proxies on, names may come from proxy files (producer inference).
• articleWhat does Kdenlive v26.08.2 write to and read from an OpenTimelineIO file, and what is not carried?
  Kdenlive's OTIO exporter writes tracks (incl. subtitle kind), clips with media references and source ranges, gaps, mixes as SMPTE_Dissolve transitions, colour clips as generator references and markers/guides; it has no effect or speed handling, and the importer leaves image-sequence references as a TODO.
• articleWhen I send a Fountain or FDX screenplay into a breakdown/scheduling tool, what comes across (scene headings, characters, tagged elements, revisions, scene numbers) and what must be exported another way?
  A plain .fdx import into Movie Magic Scheduling brings only sluglines and speaking characters; breakdown tags need a Final Draft Scheduling Export (.sex). Fountain offers scene numbers, notes, sections and synopses but no tag or revision markup, so a Fountain-only project has no standard carrier for breakdown tags. Revision-mark handling on import is not documented in the pages read.
• articleWhen review notes go into a CMX3600 EDL as comments (LOC lines) and come back, what is kept and what is lost?
  The OTIO CMX 3600 adapter reads '* LOC: <timecode> <COLOR> <text>' into a zero-duration Marker named with the text (source colour word kept in metadata, unknown colours become RED, non-matching lines silently skipped) and writes each marker back as LOC with start timecode, colour and the upper-cased name; duration and Marker.comment are lost and positions depend on the EDL rate. Drawn annotations have no slot.
• articleIf I move review notes between OpenRV and an OTIO timeline, which survive: markers, drawn annotations, hold/ghost settings?
  At Open RV 27db5464 the OTIO reader imports markers (name, range, colour, metadata as JSON) and turns OTIO annotation layers into RVPaint strokes placed on each layer's end-inclusive frame, with hold/ghost as session settings; the writer exports markers only when the importer-created otio_metadata property exists and has no annotation/paint code, so drawn notes are import-only and RV-native markers may not export (inference from the guard). No Marker.comment is carried either way.
• articleIn Kitsu's Zou server, how are shots, tasks, task statuses, review previews and review comments modelled?
  Zou v1.0.97 stores shots, assets, sequences, episodes and similar as rows of one polymorphic Entity table (entity_type_id, parent_id); a Task joins an entity, a task type and a status (unique per name, project, type and entity); statuses carry flags such as is_retake and is_feedback_request; comments attach to any object and can change a task's status; a PreviewFile (revision, validation status, JSONB annotations; unique per name, task and revision) is the reviewable artefact, not a publication.
• articleHow do USD layers/sublayers and Unreal Engine USD multi-user editing support several people working on the same scene, and what limits do the OpenUSD docs state?
  OpenUSD treats a layer as the atomic persistent unit, advises sublayering over referencing when namespaces match, and requires single-writer, no-concurrent-read editing of a stage's layers. Unreal's Beta USD multi-user editing syncs prim add/remove/rename, attribute and visibility edits, needs identical file paths on all clients (USD under project source control), and cannot undo prim deletion. No source read describes text-level .usda merging. OpenUSD code is under TOST 1.0 (Apache 2.0 with a different trademark section).
• articleHow do Godot text scenes and resources (.tscn/.tres) support version control and multi-person work, and what merge or diff problems are documented or reported?
  Godot docs call TSCN mostly human-readable and VCS-friendly: a header uid, string IDs for ext/sub resources, no central ID metadata, and per-node unique_id (scenes saved with 4.6+) to track moved or renamed nodes; ignore .godot/ and *.translation. An open 2023 user report (4.1.x) says opening scenes on different clients regenerates resource names, producing noisy diffs; whether this persists at 4.7.2 is unverified.
• articleBeneath the guild and union agreements, what statutory rest and meal floors do the UK Working Time Regulations and California's motion picture wage order state, and which of the two names the motion picture industry?
  UK Working Time Regulations reg. 10 (11 consecutive hours daily rest) and reg. 12 (rest break when daily working time exceeds six hours; 20 minutes absent an agreement) as served on 2026-10-21; California IWC Order 12-2001 applies to the motion picture industry and states a 30-minute to one-hour meal period, a 16-hour daily maximum including meals, and exempts administrative, executive and professional employees from the hours sections.
• articleWhat turnaround, weekend rest, meal-timing and meal-penalty numbers does the IATSE Local 212 (Alberta) 2024-2027 motion picture agreement state?
  The IATSE Local 212 (Alberta) 2024-2027 agreement as hosted by Negotech states a 10-hour minimum rest between shifts, 54 hours on a five-day week (reducible to 52 under conditions), 34 hours on a six-day week, 74 hours on a three-day break, encroachment paid on the invaded hours only, a $3.00 per tenth-hour meal penalty and a nine-hour limit without a meal.
• articleWhen a screenplay with locked scene numbers moves between Trelby, Starc, Beat and afterwriting, where are the numbers written and where are they read?
  At the pinned commits, Starc (when its scene-number option is on) and Beat write a Number attribute on FDX scene-heading paragraphs, Trelby writes none, and none of the four importers read (Starc, Beat outside tag definitions, Trelby, afterwriting) take a scene Number from FDX, so locked scene numbers such as 12A are at risk of renumbering on any FDX round trip through these tools (static reading).
• articleWhat does the ASC Media Hash List v1.0 specification define for hashes, process types, chain of custody and verification when offloading and copying camera media, and what does it leave to tools?
  ASC MHL v1.0 (15 Mar 2022) makes manifests immutable, labels each recorded hash original, verified or failed, allows only original or verified hashes for verification, records manifests as transfer, in-place or flatten processes, and defines a hash of hashes over same-algorithm child hashes sorted lexicographically; the ascmhl reference tool v1.2 defaults to xxh128 and prioritises md5 first for verification (tool constants, not specification text).
• articleWhose script is the Chapter XX five-reel specimen, what permission statement does the book print for it, and how should an agent treat it?
  Chapter XX prints 'Everybody's Girl' as adapted from O. Henry's short story 'Brickdust Row' by A. Van Buren Powell and produced in film form by the Vitagraph Company. The only permission statement is footnote 35: 'Used by permission. Copyright, 1918, by the Vitagraph Company of America. All rights reserved.' It gives no licence terms (scope, term, territory, redistribution). The authors say the printed text is the script in the form accepted for production; footnote 60 says it is the script before it reached production. Treat the script as a RIGHTS HOLD: short excerpts with line numbers only, no bulk reproduction, until curation decides. This row concludes no legal clearance and does not decide the status of the O. Henry story, the film or the Gutenberg wrapper.
• articleDoes any openly readable on-set VFX data template record who captured each item (operator/person) and whether it was checked or unverified, and if not what is the nearest documented substitute?
  Negative result with partial analogues. In the VES Camera Report spec the only person field is slate-level 'Wrangler' (person entering data); the VES On-Set VFX Data Guide (v1.1.0 file) assigns a Creator role per data item (role names, not persons). Across the pinned VES texts read there is no verified/unverified or checked field; the nearest items are the 'Under Protest' VFX Work flag, the guide's Clips Report 'data confirmation' and the timestamped virtual-production scene snapshot. A synthesis proposal adds 'Tk Captured By' and 'Tk Verification Status' columns, which the spec's own extension rule and sample reader would carry (untested).
• articleI need a free, ready-made on-set VFX camera report: which fields does the VES form have, what person field exists, and what does it let the wrangler tick as captured?
  The VES Camera Report (VES Technology Committee, camerareports.org) is a free Filemaker database, blank paper PDF and CSV interchange spec whose slate/take fields cover lens (focal length, focus distance, lens height, serial, stop, shutter, tilt, dutch), unit, camera and a 'Set Media' checklist (Balls, Clean Plate, Cube, HDRI, Mocap, Photos, Survey Diagram, Tile Set, Virtual Set, Witness Cam). Its only person field is slate-level 'Wrangler' ('person entering the data'); no verification/checked/status field appears in the spec, proposal, changelog, developer guide or blank form texts read. LIDAR is not a baseline Set Media value, though the spec says other values may be defined.
• articleWhat do studio and vendor first-person accounts say about the real speed and accuracy gains of ML deformers in production rigs, and where do they fall short?
  DreamWorks and Berkeley (2018) report 5x-10x faster deformation evaluation on production rigs. Golaem (DigiPro 2024) tried to reproduce this in a commercial crowd product and reports only x1.2-x2 on production assets because the paper's rigs were optimised for the model and the rest of rig evaluation dominates; its main disappointment was no significant speed gain. It reports Euler-angle and facial limits of the first method, ships the ML deformer as a crowd-package feature for close-up facial deformation, and notes crowd artists prefer overfitting because crowd sims blend clips rather than generate unseen animation. The paper's own Table 1 fps values imply 1.8x-2.5x, which does not match its text range.
• articleHow do the Call-back (rest) provisions of two dated Studio Local agreements (2015 Local 871, 2021 Local 728) differ in rest hours and weekend rest?
  The 2015 Local 871 text sets 8/9/10-hour post-dismissal rests and contains no weekend-rest provision (curator search: 0 matches), while the 2021 Local 728 text sets a 10-hour daily rest plus 54/32-hour weekend rests; both carry the same 6-hour first-meal and 12-minute grace wording.
• articleIn a public Studio Local agreement based on the IATSE Basic Agreement (2021), how many hours are the daily and weekend rest periods and what is the first meal timing?
  The 2021 Local 728 agreement (Aug 1, 2021) states, for productions starting principal photography on or after 2022-02-13, a 10-hour daily rest, a 54-hour weekend rest (reducible to 50 in listed cases), 32 hours after six consecutive days, a first meal within six hours of first call and a 12-minute non-scheduled grace period.
• articleWhich failure modes does Chapter XIII (1919) name for scripting what cannot be photographed or staged, and which are the authors' claims versus examples versus quoted voices?
  Five script-side failures are named: a scene that will not register; one that is possible but impractical (Sargent's chase with dust and smoke); a demand for a particular background; a demand for an effect whose cost is out of proportion; and a belief that the camera does everything it seems to (trick photography versus careful work). The staging failure of players leaving the frame, and the camera and tripod hazards (Fildew), describe studio and camera problems, not script mistakes. The remedy the authors give is to write difficult scenes as a suggestion. All of this is 1919 trade advice; the voices are separated below. The chapter says nothing about modern generative failure modes.
• articleWhat do ASCAP, BMI, SOCAN and PRS for Music publicly say about AI-generated music in registration, and do library pages say anything about it?
  A joint release dated 2025-10-28 (hosted on SOCAN's site) says ASCAP, BMI and SOCAN each adopted policies to accept registrations of partially AI-generated compositions, defined as combining AI-generated musical content with human authorship, and that entirely AI-created compositions are not eligible. BMI (403), ASCAP's own AI help page (403) and a PRS AI policy PDF (404 at the URL a search returned) could not be read, so the societies' own policy texts and PRS's position are not inspected here. None of the library, publisher or Guild pages read contains any AI statement. The release says nothing about cue sheets, clearance or licensing of AI-made music.
• articleWhat capture specs does Netflix require for its productions, and what does that imply for mixing AI-generated shots into premium deliverables?
  Netflix (rendered 2026-10-23) requires 90% of a program's final runtime to be captured on approved cameras (more flexible for nonfiction). Minimum capture attributes for approval consideration: at least 3840 photosite width (spherical); lightly compressed or uncompressed RAW, or intraframe codec with 4:2:2 or better; 10-bit or greater; at least 240 Mbps at 24 fps; scene-referred colour space (e.g. S-Gamut3, ALEXA Wide Gamut, REDWideGamut) and transfer function (S-Log3, LogC, Log3G10, V-Log); timecode jammable to an external source and written as metadata. The page lists 69 approved camera entries across ARRI, Canon, Panasonic, RED, Sony, Blackmagic and DJI, with anamorphic approval flagged per camera. Best practices: aspect ratio is a creative choice to agree with Netflix (framing calculator provided); anamorphic may need extra resolution; test each format's colour transform into the working space (ACES introduced); avoid clips spanning camera cards; discuss film capture and externa...
• articleWhat can Kling 4.0 do according to its published API schema (Oct 2026), and what is still unknown?
  fal lists four Kling 4.0 endpoints (registry date 2026-10-16, status active, but every description says "API access is coming soon"; playground and fal Agent only). Schema facts: text-to-video, image-to-video (start and optional end frame), reference-to-video and video-to-video edit; 720p or 1080p (default 1080p); duration 3-30 s (default 5); aspect ratios 16:9, 9:16, 1:1, 21:9 (+auto for references). Multi-shot via multi_prompt: a list of {prompt, duration} shots whose durations sum to the video length. Reference-to-video: up to 10 images (@Image1..), up to 5 reference videos (@Video1.., 3-30 s each, 30 s combined with element videos), up to 7 elements (@Element1..) each defined by a frontal image plus 1-3 extra-angle images or a 3-30 s video; up to 3 elements may carry a voice_id (created with fal-ai/kling-video/create-voice) and up to 3 may be video elements. Edit: input video 3-30 s, ≤300 MB, 700-4553 px sides, instructions reference @Video1 plus optional images/elements; output...
• articleWhat does each major video model cost per second through one multi-vendor API (Runway Dev, Oct 2026), and how does Seedance 2.5 draft mode work in API terms?
  Runway Dev docs (captured 2026-10-23): credits cost $0.01; the API serves Runway and third-party models (Seedance 2.5/2.0/Fast/Mini, Aleph 2.0, Gen-4.5, Gen-4 Turbo, Act-Two, Kling 3.0/O3 incl. 4K, Kling 2.5 Turbo, MiniMax H3 (hailuo3) and H3 Max, Wan 3.0/Prime, Grok Imagine 1.5/Lite, HappyHorse 1.0, Veo 3.1/Fast, Gemini Omni Flash/1.1; images: GPT Image 2.5 Sunburst/Flare, GPT Image 2, Nano Banana 2.1/2/2 Lite/Pro, Ideogram 4.5/4.0, Seedream 5.0, Grok Imagine Image 2, Meta Muse Image, Bria FIBO; upscalers) plus "Model Routers" that pick models by cost/latency/quality. Per-second prices (output): Seedance 2.5 480p 20 cr ($0.20), 720p 30 ($0.30), 1080p 68 ($0.68 = $40.80/min) plus input/reference video 10/15/34 cr/s (combined input video capped at 30 s; reference images and audio free; 80-credit minimum); Seedance 2.0 36-40 cr/s (4K 150); Kling 3.0 Pro 12 (17 with audio), 3.0 4K 43; Kling O3 Pro 17; Kling 2.5 Turbo Pro 12; MiniMax H3 768p 10 (+2 per reference image/keyframe), 2K 15; ...
• articleWhat does one generated still cost at each major image service, and why can two services quote the same token rate but different per-image prices?
  Dated 2026-10-22: Gemini 3.1 Flash Image $0.067 per 1K image (token-based, $60/M image tokens, 1,120 tokens); OpenAI gpt-image-2 per-image table $0.006/$0.053/$0.211 (low/medium/high, 1024x1024) with a token rate of $30/M output tokens; Runway gpt_image_2 1/5/20 credits per 1K image; Stability Stable Image Ultra 8 credits ($0.08); Replicate flux-1.1-pro $0.04 per output image; Luma Uni-1.1 about $0.04 per 2K image (two price columns, second is Max). Image prices are quoted per image, per megapixel, per credit or per token, and OpenAI states equal token rates do not mean equal cost per image.
• articleWhat does generating one minute of 1080p AI video cost per model on vendor APIs, and how does price relate to measured quality (Oct 2026)?
  Artificial Analysis video boards (rendered 2026-10-23; Elo anchored at Kling 3.0 1080p Pro = 1000; prices = 1 minute of 1080p on the creator's API at default settings). Text-to-video: Wan 3.0 1175 ($12.00/min), HeyGen Video 1 1160 ($2.40), MiniMax H3 768p 1158 ($4.80), Seedance 2.5 1158 ($34.12), FLUX 3 Max 720p 1155 ($2.55), MiniMax H3 Max 1154 ($4.80), FLUX 3 1145 ($17.40), Seedance 2.0 1136 ($22.45), Gemini Omni Flash 1.1 1130 ($9.12), Grok Imagine 1.5 1056 ($15.00), Kling 3.0 Omni 1020 ($8.40), Kling 3.0 1000 ($10.08), Veo 3.1 963 ($24.00), Veo 3.1 Fast 960 ($7.20), LTX-2.5 Fast 949 ($7.80), LTX-2.3 Pro 888 ($4.80). Image-to-video: MiniMax H3 768p 1140 ($4.80), FLUX 3 Max 1138 ($2.55), Seedance 2.5 1138 ($34.12), Gemini Omni Flash 1.1 1132 ($9.12), Wan 3.0 1127 ($12), ... Veo 3.1 1028 ($24), Kling 3.0 1000 ($10.08). CIs are about +/-15 Elo, so the top 6-8 are statistically close while prices differ by >10x (Seedance 2.5 vs FLUX 3 Max / MiniMax H3). This quantifies creator report...
• articleHow should an agent decide whether a given local machine can run a particular shot with an open video model, given what the READMEs state and do not state?
  Proposal (synthesis): decide in four gates. (1) Geometry: choose model and variant whose frame form, size set and fps can express the shot (candidate 04). (2) Stated floor: compare the machine GPU memory with the README figure whose settings match the shot (candidates 01-03, 05); if the shot setting is not among the stated settings, mark memory unknown. (3) Weights and disk: add the sizes of the files the pipeline loads (HF listing: e.g. Wan2.2 TI2V-5B about 20.0 GB transformer + 11.36 GB T5 + 2.82 GB VAE; HunyuanVideo-1.5 transformers about 33.3 GB each; Mochi dit 40.11 GB). (4) Time: only the READMEs name time on named GPUs for a few settings; otherwise time is unknown. Where a gate returns unknown, run a bounded preflight (proposed, not run) rather than guess. No inspected README gives a rule to extrapolate memory across resolution or length.
• articleBefore I price a shot list: which units do the major video and image generation services bill in, and which named models are still available on 2026-10-22?
  At captures dated 2026-10-22 the services bill in different units: USD per second (Gemini API Veo), tokens that the page converts to seconds (Gemini Omni Flash), credits at a fixed USD value (Runway $0.01, Stability $0.01), per clip or per 5 s block (Luma), per output image or megapixel (Replicate, fal) and per image token (OpenAI, Gemini). Two named video offers are ending or gone: OpenAI states the Sora 2 models and Videos API were shut down on 2026-09-24, and Google states the Gemini API Veo 3.1 preview models shut down on 2026-10-22. An agent should first record unit, date and availability for every price it uses.
• articleDo documentary organisations, insurers or law firms say anything about E&O insurance and clearing or disclosing AI-generated material, and do the older fair-use and insurer documents mention AI at all?
  The Archival Producers Alliance guidelines (v.7, September 2024) and tool kit say to be transparent with legal counsel and E&O insurers, name risk "not covered by E&O insurance policy" as an item for attorneys, and tool kit question 8 asks whether GenAI materials will impact E&O; they also ask whether the distributor permits GenAI and what documentation it requires. Reed Smith (30 Sep 2026) says E&O coverage may turn on exclusions and gives an AI-assisted rights-clearance report that omits a licence as an exposure example. The Fair Use Statement page (Nov 2005) and both Beazley forms contain no AI terms in the text searched.
• articleHow should I name a VFX shot and its versions so a studio or vendor will accept the delivery?
  Netflix requires shot names showID_episode_scene_VFXID (series; episode 102 = season 1 episode 2) or showID_sequence_scene_VFXID (film), and a CSV Version Name equal to the full movie file name or the EXR base name without frame numbers. A community convention (ComfyUI README after Victor Perez) uses AAA_AAA_####_aaaa_aaa_v###.####.aaa with shots numbered in tens and FINAL for finals. The two differ; studios' own specs govern deliveries.
• sourceFlow Production Tracking (ShotGrid) Python API
• sourceDaily call sheet (Wikipedia)
• sourceProduction board (stripboard) (Wikipedia)
• sourceFilm budgeting (Wikipedia)
• sourceAcademySoftwareFoundation/OpenTimelineIO
• discussionFigures differ by survey year and population, not necessarily by contradiction. The AJA statement cites the JAniCA 2022 survey: average annual income of 1.966 million yen for ages 20-24 and 4.555 million yen overall, and says the UN working-group figure of 1.5 million yen for new animators traces t…
• discussionTwo repositories met the bar of a real license file, readable documentation and visible activity: UniversalScheduleStandard (a JSON interchange format, licence conflict, see F07) and OpenShotDesigner (GPL-3.0-or-later; stripboard, DOOD, call sheets, schedule-derived budget; created 2026-08-17, one …
• discussionNone was found. Searches for generative-AI cost tracking returned only vendor blog posts, which were not recorded. Netflix's Partner Help Center has a Gen AI category, but fetching it redirects to a script-driven hub that returned only a 'Knowledge Hub' heading, so the guidance text could not be re…

More