articles

API: /v1/records?type=article

• How does Epic's documented IK Rig Retargeter work (chains, root, retarget pose, FK/IK settings) at UE 5.1? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The UE 5.1 retargeting page documents two IK Rigs with retarget chains, a retarget root (typically pelvis), a retarget pose for A/T-pose differences, fuzzy chain-name matching, batch retargeting via Duplicate and Retarget, and global/per-chain settings including stride warping and speed planting. It overlaps the live-docs reading in CA-B197 (C2-B21-D3-01), here pinned to the 5.1 edition.
• How do practitioners and guild descriptions say blocking, screen direction and coverage are tracked, and why do they deliberately cross the line? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  A guild job description assigns the script supervisor to assist during blocking, record action, positions, angles and coverage, and send a lined script to editorial daily; practitioner reports describe deliberate line-crossing for effect (Libatique and Aronofsky using the two sides of the line to mark a tonal shift in Requiem for a Dream). No primary DGA/ASC source on floor plans or overhead diagrams was found.
• Does the Ofcom Broadcasting Code apply to the video or programme I am making, and what does Rule 2.2 mean in plain terms? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The Broadcasting Code applies to radio and TV content on Ofcom-licensed services (plus BBC licence-fee services and S4C) and binds broadcasters through their licences; notified on-demand providers fall under separate rules; Ofcom regulates accuracy as such only in news (Section Five), and 'materially misleading' depends on context and potential harm or offence. Whether it reaches an independent creator's online video is not stated in the Code read.
• Where does the '32 characters, 3 lines' closed-caption rule in a DCP come from, and what do SMPTE ST 429-5:2023 and RDD 52 (the Bv2.1 profile) say about closed-caption packaging? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The DCP closed-caption limit of 32 characters per line and 3 lines per instance comes from SMPTE RDD 52:2020 (the DCP Bv2.1 Application Profile, a Registered Disclosure Document expressly not a Standard), which notes some languages need fewer characters (e.g. 14 or 16) and also says caption XML should not exceed 256 kB, forbids MainCaption and ClosedSubtitle and requires 48 kHz audio. ST 429-5:2023, the packaging layer, defines closed captions as text for a non-screen device and sets no character or line limits.
• How does SMPTE ST 2067-2:2020 carry IMSC timed text and fonts in an IMF package? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  SMPTE ST 2067-2:2020 requires an IMF Timed Text Track File to carry one TTML document conforming to the IMSC1.1 Text or Image profile (wrapped per ST 429-5), with non-generic fonts carried as OpenType ancillary resources identified by UUIDv5 derived from the font family name, and defines kinds including subtitle, caption and forced narrative; it sets no characters-per-line or reading-speed limits.
• What does SMPTE ST 429-2:2023 constrain for timed text in a DCP: fonts, number of subtitle instances, Text and Image elements, tracks? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  SMPTE ST 429-2:2023 requires exactly one LoadFont when Text elements are present, says the font resource should not exceed 10 MB (noting legacy systems may not support more than 640 KB), allows at most two visible subtitle instances with up to six Text or three Image elements each, and limits compositions to one on-screen plus six off-screen text tracks; it sets no characters-per-line or reading-speed limits.
• What does SMPTE ST 428-7:2014 say normatively about subtitle structure, text limits and font carriage for a DCP subtitle file? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  SMPTE ST 428-7:2014 defines DCDM subtitle XML with percentage positions, an optional LoadFont naming a font only by urn:uuid (mapping to a file out of scope), PNG sub-pictures bounded by the picture, and ruby, vertical and bidi rules; it advises that a Text string fit one line, with multiple lines as sibling Text elements, and sets no characters-per-line, reading-speed or minimum-duration numbers.
• What do the publicly readable SMPTE ST 2059-1, ST 2059-2 and ST 12-1 documents define about synchronising video signals and time code? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  SMPTE ST 2059-1:2021 defines the SMPTE Epoch (1970-01-01 00:00:00 TAI, equal to the PTP epoch) and how interface signals and ST 12-1 time code are aligned to it; ST 2059-2:2021 profiles IEEE 1588 PTP (default domain 127) with a synchronization-metadata TLV for time-address flags, jam and leap-second data; ST 12-1:2014 defines the time address, drop-frame counting, LTC and VITC. The PDFs are freely readable at pub.smpte.org (SMPTE copyright).
• In Open RV v4.0.2, does the renderer ever read an RVPaint stroke's softDeleted or uuid property, and are soft-deleted strokes drawn? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Open RV draws an annotation only if its component name is in the frame's order list (then filters by eye, point count and startFrame/duration); no render code reads softDeleted or uuid. Open RV's own writers (annotate mode and the OTIO hook) keep deleted items out of the order list, so a softDeleted=1 stroke would be drawn only if a third-party writer left it in the order list (code inference).
• Exactly which GTO components and typed properties does Open RV create for a pen stroke, a text box and a shape, and which of them does the renderer actually read? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Annotate mode creates typed properties per object (pen: color, width, brush, points, join/cap/splat, startFrame/duration/mode, plus uuid and softDeleted; text: position, colour, size/scale/rotation, font fields, text, plus uuid and softDeleted; shapes: startFrame, duration, eye and geometry). PaintIPNode, which draws them, reads the drawing properties but never uuid or softDeleted.
• Which parts of an IES file do Blender, Unity and Unreal actually read, ignore or reject when used for virtual lighting? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The parsers differ in tolerance: Blender v5.2.2 skips TILT=INCLUDE tables (never applying tilt), ignores lumens and units, accepts types A/B/C, mirrors missing quadrants ('much more forgiving than the spec') and converts candela with a fixed 4*pi/177.83 factor; Unity recognises versions from IESNA91 to IES:LM-63-2019 but rejects any TILT other than NONE; Unreal documents candela brightness and clipping of profiles to the spot cone.
• What do IES and EULUMDAT files describe, and which of them do Blender, Unreal Engine and Unity accept as a light profile? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  IES (LM-63) and EULUMDAT (.ldt) both tabulate luminaire intensity by direction, but the Blender, Unreal and Unity HDRP documentation and the Unity and Blender importer code read handle IES only (Unity registers only the .ies extension; Blender parses from the IES TILT line); no inspected source mentions EULUMDAT, so .ldt files need external conversion.
• What does a public studio delivery specification say about handing off Foley (cue sheets, track naming/layout, stems)? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Netflix's nonfiction M&E guide treats Foley as an optional, often unbudgeted pass cued at the sound or post supervisor's discretion (cloth and props first, footsteps rarely), with married music, effects and separate dialogue stems when there is no Foley; its sound-mix spec v1.6 lists Foley as a labelled object/bed group and expects Foley fill in the 5.1 M&E. No public Netflix text read gives a Foley cue-sheet format or track layout.
• What changed between FOGRA39 and FOGRA51/52 and what do ECI/Fogra say about lamination, varnish and measurement for CMYK conversion targets? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  ECI says the 2013 revision of ISO 12647-2 changed ink aims and tone-value curves for optically brightened papers; FOGRA51/52 come with PSO Coated/Uncoated v3 profiles and require M1 (UV-including D50) measurement for metered proof and print control; FOGRA49/50 cover matt/glossy lamination derived from FOGRA39-era test prints, varnish shifts are smaller and have no standard data set, and FOGRA60 covers metal printing.
• Which public sources actually state GWG 2022 variant limits, which only describe the profiles, and what versions or dates do they carry? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  No public GWG document read states GWG 2022 numeric limits as specification text: the GWG specifications page offers vendor settings downloads, and the callas documentation explains where the bundled profiles are without giving thresholds. The numbers live in vendor profile files (e.g. callas .kfpx), so an agent must read the profile for the variant it targets.
• What changed in the WGA's AI article (Article 72) between the 2023 MOA and the 2026 MOA, according to the two MOA texts? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The 2026 MOA (April 4, 2026; term May 2, 2026 to May 1, 2030) amends only Paragraph G of Article 72: it keeps semi-annual meetings and adds written notice to the Guild when a company grants a compensated licence to a non-affiliated third party to train a public-facing commercial GAI system, with a meeting on request. Paragraphs A-F (AI not a writer, disclosure, consent) are not amended in Item 15, and the WGA's AI page still describes the 2023 provisions.
• What do Unity's URP and HDRP docs say about enabling HDR output, tonemapping modes, paper white and UI brightness for real-time output? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Unity applies HDR output as tone mapping (including Rec.709-to-display-gamut conversion) followed by a transfer function; URP and HDRP offer Neutral and ACES modes, HDRP's ACES mode has fixed 1000/2000/4000-nit presets, paper white sets unlit/UI brightness, and the docs recommend a player calibration menu; HDRP has gamut and over-paper-white debug views.
• In Godot, how do I enable HDR output and choose between tonemapping and the output-max-linear-value approach, and which tonemappers are compatible? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Godot's HDR output guide lists enabling steps (no SDR-only environment features such as Filmic/ACES tonemapping or Soft Light glow), two approaches (tonemap scene lighting, or use get_output_max_linear_value only for direct presentation), notes that Filmic and ACES ignore the output maximum and stay SDR, supports iOS, Wayland, macOS, visionOS and Windows but not Android, X11 or web, and warns that many HDR screens apply their own tonemapping (prefer HGiG/clip modes during development).
• What do designers' first-person accounts (Emily Short, Failbetter) say about how quality-based narrative works and where it strains? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Emily Short describes quality-based narrative (Failbetter's term) as storylets unlocked by numeric qualities for inventory, skills and progress, contrasts it with salience-based selection, and notes from experience that it feels thin until many storylets exist, long option lists overwhelm players, and mid-sized modular additions are safe; Failbetter describes qualities driving branches and 'questicle' chains. Practitioner accounts.
• In Kitsu's Zou server, how are shots, tasks, task statuses, review previews and review comments modelled? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  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.
• I want to look up a Poly Haven asset by API: what identifies it, what version signal does it give, what units are its dimensions in, and where is its licence? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Poly Haven's API keys assets by slug, exposes date_published, img_version and files_hash (a SHA1 of the files listing that changes when files update) and dimensions in millimetres, but no per-asset licence field: the README states assets are CC0 while the live API requires a 'Powered by Poly Haven' credit, and the API software itself is AGPL.
• Where does the OpenEXR library's own deep compositing and deepImageState handling differ from or go beyond the Interpreting Deep Pixels document? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The v3.5.2 default compositor sorts samples by Z then ZBack only when combining more than one source, then composites front to back with over and stops at alpha >= 1; it performs no volume splitting or overlap merging and does not consult deepImageState, so single unsorted images are composited in stored order. The library's SORTED definition uses strict < on ZBack where the document uses <=, and CompositeDeepScanLine requires an alpha channel. Code reading only.
• How are deep images merged, made tidy and flattened to a flat image according to the OpenEXR deep-pixel document, including how alpha and colour are combined? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The document defines merging two deep images as concatenating sample lists; flattening needs a tidy image (sorted and non-overlapping): split partially overlapping samples, merge coincident ones (alpha = 1-(1-a_i)(1-a_j)), sort, then composite front to back with over. Volume opacity follows 1-(1-alpha)^x so splitting preserves total opacity, and the flattened depth is not uniquely defined. Files need not be tidy.
• What is a deep sample in OpenEXR, and how do I tell a point sample from a volume sample and which channels a deep file must have? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  An OpenEXR deep pixel holds any number of samples (all channels share the count), each with a depth; Z is required and ZBack optional (copied from Z if absent); Z >= ZBack is a point sample (zero-thickness surface hit) and Z < ZBack a volume sample over [Z, ZBack); each colour or auxiliary channel needs an associated alpha found through its layer and enclosing layers. The library stores the data; the Interpreting Deep Pixels document defines the meaning.
• What does EBU R 37 say numerically about sound and picture timing, and do the EBU-TT-D documents (Tech 3380, Tech 3381) state any reading-speed or line-length numbers? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  EBU R 37-2007 limits end-to-end sound-picture offset at emission to 40 ms sound-early and 60 ms sound-late, with 5 ms early to 15 ms late at each stage, measured with flash-and-blip markers. EBU-TT-D (Tech 3380) sets layout defaults (cellResolution 32x15, linePadding 0c) but neither it nor Tech 3381 gives reading-speed or line-length limits, which must come from style guides.
• What process norms for delivering and managing script notes do guild or industry bodies state (who gives notes, how they are delivered, who may see assessments)? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Under the WGA's MBA-linked consultation rule, producers consult the writer on each set of requested revisions so notes are not sent unexplained, with a strong preference for one consolidated set of notes and, for long-form TV, network notes delivered to writer and producer together. New Zealand's SPADA guide asks collaborators to agree in advance who gives notes to whom, separates script consultants (feedback only) from editors (who modify), and keeps assessments confidential without the writer's permission. Different jurisdictions and contract regimes.
• What does a screenwriters' guild tell a writer to do when receiving script notes, in plain terms? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The WGA West Screenwriters Handbook (Nov 2025) advises writers taking notes not to be defensive or feel obliged to accept or solve every note in the meeting, to ask for clarification, respond in writing (separating clear from unclear notes), explain respectfully why a note does not work, take time to design comprehensive solutions, and not become a rubber stamp for someone else's agenda. Union advice to writers, not a neutral standard.
• What does AES TD1008 say about true-peak limiting, codec overshoot and sample-rate conversion when preparing masters for lossy streaming? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  AES TD1008 (2021, superseding TD1004) recommends at most -1 dBTP at the input of lossy codecs (high-rate coders around 256 kbps may tolerate -0.5 dBTP), a true-peak limiter as the last element before the codec, and notes downward SRC can create overshoots a limiter placed before it cannot catch; its distribution table targets speech at -18 LUFS (+1 LU), track-normalised music at -16 LUFS and album-loudest tracks at -14 LUFS (+0.2 LU).
• What does Apple Digital Masters (formerly Mastered for iTunes) ask a mastering engineer to deliver and check for AAC streaming: bit depth, sample rate, headroom, SRC and clipping? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Apple's Digital Masters brief asks for 24-bit sources at the highest native rate (no upsampling or bit-padding), describes mastering-quality SRC to a floating-point intermediate before AAC encoding, recommends at least 1 dB headroom because playback oversampling and encoding can clip material that shows no PCM overs (checked with afclip), and says one master feeds both AAC and ALAC. It gives no dBTP or LUFS target.
• What subtitling, audio description and signing percentages does Ofcom's Code on Television Access Services set for UK-regulated TV channels, and how are channels and affordability decided? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Ofcom's 2024 access code sets statutory ten-year targets of 80% subtitling (90% Channel 3 and 4; 100% BBC), 10% audio description and 5% signing as percentages of non-advertising programme hours per delivery platform, with interim targets by anniversary (e.g. year 1 10/2/1%, year 5 60/10/3%); Ofcom's July 2025 notice lists 83 channels required in 2026 (82 at Level One). The Code does not cover on-demand services (producer reading of the 2024 statement).
• What numbers does Ofcom's Code on Television Access Services (updated 20 Nov 2019) set for audio description and subtitling, and which of them are binding targets versus best-practice guidance? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  In the 2019 edition of Ofcom's access code, binding annual percentage targets rise to 10% audio description, 80% subtitling and 5% signing, while numeric production guidance (subtitles normally at most 160-180 wpm for pre-recorded programmes, live delay at most 3 s, two lines unless three do not obscure the picture) sits in Annex 4 as guidance to 'have regard to'. This edition is superseded by the 2024 Code (C2-B61-K5-06).
• What do the FCC closed-captioning quality rules in 47 CFR 79.1 actually require, and do they set numeric timing or line-length limits? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  FCC caption quality standards in 47 CFR 79.1(j)(2) require captions to be accurate, synchronous, complete and appropriately placed (readable speed; not blocking important visual content), with a de minimis allowance and case-by-case factors for live programming; the section read contains no numeric speed, line-length or timing limits.
• What decision criteria do veteran film editors state publicly for choosing performance takes and cut points, and where do they differ? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Three veteran editors describe their working order: Murch ranks emotion, story and rhythm above eye-trace and 2D/3D continuity and drops criteria from the bottom up (his percentage weights are a rhetorical device), and calls the last frame of a shot perhaps the most important choice; Littleton marks the best take per script line and weighs performance first; Schoonmaker puts the best performance take ahead of continuity. These are individual accounts, consistent with the experimental finding that axis violations rarely hurt enjoyment.
• Does the brain treat continuity cuts as a common event, and do cut types differ? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  An open-access EEG study (21 viewers) reports neural responses common to continuity cuts (theta synchronisation, delta desynchronisation) interpreted as encoding and segmentation; differences by cut type appeared under one taxonomy but not another, where results matched random groupings. Only continuity cuts were tested, so it says nothing about jump cuts or axis breaks.
• Does crossing the 180-degree line confuse viewers or reduce how much they like a video? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  In three experiments with sketch-style videos, viewers noticed 180-degree violations (flagging .42 of critical cuts vs .08 without violation), were slightly more confused (about 8% vs 6% of critical cuts), and liked violated videos just as much (preference .519, Bayes factor favouring no effect). This supports 'detectable and mildly confusing' but not 'harms enjoyment'.
• Does OpenUSD's Hydra pipeline (hdParticleField, hdSt, hdEmbree) at v26.08 use ParticleField3DGaussianSplat sortingModeHint and projectionModeHint? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At v26.08 no Hydra path read consumes the splat hints: the schema calls them advisory (sortingModeHint allows zDepth, cameraDistance and rayHitDistance), the usdImaging adapter only has a TODO to pass them, the hdsi conversion never mentions them, and the sample renderer sorts by view-space z regardless.
• I author a splat prim in USD: should I set sortingModeHint and projectionModeHint, and will Hydra renderers honour them at v26.11.0? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The hints are advisory: at v26.11.0 they reach Hydra scene data, but Pixar's inspected consumers (hdPrman conversion, sample renderer) do not read them, so setting them is harmless and should not be expected to change output there; the docs now describe rayHitDistance and say rasterizers may treat it as cameraDistance.
• What changed in OpenUSD's Gaussian-splat particle-field path between v26.08 and v26.11.0, and does any renderer path now use the sorting or projection hints? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At v26.11.0 usdImaging exports a Hydra particleField container with kernelType (hardcoded gaussianEllipsoid) and both hints, closing the v26.08 TODO; the new hd schema exposes only kernelType, and the hdsi conversion, hdPrman plugin, sample renderer and schema.usda are byte-identical to v26.08, so by code reading none of them consumes the hints.
• How do the intensity units, normalisation and symmetry rules differ between IES (LM-63) and EULUMDAT files, so values are not mis-scaled? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  EULUMDAT stores relative intensity (cd per 1000 lm) with a conversion factor and luminaire flux, and only the symmetric C-plane portion indicated by Isym; public tables differ on whether type indicator 0 exists (AGi32 lists 0-3, DIALux 1-3). IES stores candela scaled by a multiplier and ballast factors; Unity treats negative lumens-per-lamp as absolute photometry and clamps negative multipliers to 0, while Blender discards lumens-per-lamp and applies a fixed candela-to-watt factor. Copying values between formats needs an explicit flux/1000 scale.
• How do depth-of-field and hyperfocal-distance calculators differ in their assumptions (circle of confusion, hyperfocal definition), and what does ZEISS say? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  ZEISS uses z = D/1500 (0.029 mm for 24x36) in its charts, gives hyperfocal approximately f'^2/(z'k) and treats the circle of confusion as a format property; a secondary source records a second hyperfocal definition differing by one focal length (H = f^2/(Nc) + f) and calls the 'Zeiss formula' D/1730 apocryphal. CoC choice and the +f term shift results: for 50 mm at f/2.8 on full frame, 35.8 m (0.025 mm, +f), 31.0 m (ZEISS D/1500) and 29.8 m (0.03 mm, +f), recomputed by the curator.
• Is there any numeric RGB vs RGBW vs RGBCA comparison (TM-30, SSI, CRI/TLCI, delta E) and does it cover skin tones or a camera? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The only numeric RGBW-versus-RGBCA comparison found is ROE's November 2024 brochure: TM-30 Rf 80 for both, SSI 68 for both at 3200 K, and SSI 62 (RGBCA) vs 52 (RGBW) at 6500 K, stated as reference values that may vary. These are panel-spectrum metrics with no camera, delta E or skin-tone data.
• What does an ASC-published first-hand test report say about evaluating exposure and colour on an LED wall, including metering and camera sync? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  A first-hand ASC test of Kodak film and an Alexa 35 against an LED wall (D65 native, content at 3200 K and 5600 K) reports that light meters misread narrow-band LED light so a digital camera and calibrated monitor stay necessary, that wall colour must be calibrated to the shooting camera's colour matrix, and that cameras must sync to panel refresh (genlock for digital; a sync box for film).
• Why can skin and costumes look wrong on an RGB LED volume, and what do RGBW and RGBCA panels claim to change (and what is only a vendor claim)? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  An ASC-reported 2021 test compared RGB, RGBW and RGBCA panels and a Kino Flo Mimik with a spectrometer and colour meter and found visible improvement over RGB (RGBCA and Mimik better than RGBW for warm and off-white content), without a numeric score; Brompton and ROE describe added white or cyan/amber emitters as broadening the spectrum, Brompton notes cameras see the white LED differently, and ROE claims better SSI and skin rendering without skin data.
• What have open papers measured about colour-rendition limits of RGB LED volumes for lit subjects (skin, clothing), and how far do 3x3 corrections get? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Two open papers attribute LED-volume colour errors to narrow-band RGB emission seen through camera sensitivities (lighter skin pinker); a 3x3 pre-correction of panel content plus camera post-correction (and black-level subtraction for 4-10% panel albedo) improves skin and orange/yellow materials, but residual errors remain (sodium-vapour light; saturated reds and greens) that no 3x3 matrix can remove. Neither tests RGBW/RGBCA panels or diverse skin tones.
• How does the MusicBrainz schema relate recordings, works, ISRC, ISWC and credits, under what data licences, and what minimal field set would an agent need to attribute a music cue correctly? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  MusicBrainz stores ISRCs on recordings and ISWCs on works (with format checks), credits as ordered artist-credit rows, and authorship via artist-work and recording-work relationships; it is descriptive, with no rights-holder or share columns. Core data is CC0 and supplementary data CC BY-NC-SA. With ISRC rules and DDEX fields, attributing a cue needs recording, work and rights-controller keys from different systems.
• Which DDEX ERN 4.3.x elements carry credits, rights controllers, territory/use scope and AI-contribution flags for a sound recording, what did ERN 4.3 lack, and under what licence is the standard offered? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  DDEX ERN 4.3.2 models recording credits and rights with Contributor (role, credited flag, AiContribution All/None/Partly, defaulting to All for a GenerativeAI special contributor), DisplayArtist, WorkId and ResourceRightsController (share, delegated use, territory, period); these AI fields are absent from the ERN 4.3 schema read, and the value sets add a UseType for GenerativeAI training. DDEX guidance says rights belong in RightsController, not Deals, yet tells recipients to follow ReleaseDeal when both state ownership (tension kept).
• What do the ISRC Handbook and CISAC say each identifier identifies, and when does an edit, remix, stem, remaster or clip of a music recording need its own ISRC? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The ISRC Handbook (2021, CC BY-ND 4.0) ties an ISRC to a recording, not its encoding: new ISRCs for edits, covers, live versions, separately released stems and promo clips; none for codec changes, non-creative remasters or length changes under 10 seconds without creative input; MIDI files get none. CISAC's ISWC identifies the musical work by title and creators, not its recordings or uses. They are different keys for the same cue.
• What does an approved animatic carry into the next stage in documented tools (scene length, panels, soundtrack, markers) and what does it not carry? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Storyboard Pro exports each animatic scene to a Harmony scene of the same length with its panels and soundtrack portion, either as rendered reference frames or as editable drawings, 3D objects, images, videos and camera moves; transitions are dropped and markers carry time, duration and note. Storyboarder writes an ffconcat list with each board's duration in seconds, listing the last board twice for ffmpeg.
• What is an animatic and what are the first steps to time one from storyboard panels with scratch audio? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  An animatic is storyboard panels cut in sequence with a scratch soundtrack to test timing and sync; practice is to order and time panels, play, and iterate while changes are cheap. Storyboard Pro starts every panel at one second (so a new board is a basic animatic), edits durations as H:MM:SS:FF and ripples later panels by default; a Blender tutorial times slides by frame count at 25 fps and later swaps in renders of the same length.
• What are storyboards, animatics, previs, techvis, stuntvis and postvis, and how does Epic's guide order them? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Epic's Virtual Production Field Guide v1.3 defines visualization as prototype imagery conveying a shot's creative intent, lists pitchvis, previs, virtual scouting, techvis, stuntvis and postvis (techvis about physics and camera data, postvis merging live action with temporary effects), and calls storyboards and animatics precursors to previs. No Previsualization Society definition was available.

More