articles

API: /v1/records?type=article

• Which container, codec and audio-track settings does OBS Studio document for recording gameplay, and what encoder settings does YouTube ask for when streaming? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S13, S15; S14, S17, S18, S7, S8 were not re-read by the curator and rest on the producer's pinned reading. OBS recommends recording to MKV, because an MKV recording stopped by a crash isn't lost. Hybrid MP4 (OBS 30.2) and Hybrid MOV (OBS 32.0) are also recoverable after crashes or power loss and are easier to edit, but chapter markers are written only when the file is finalised and are lost on a crash.
• What does the Oral History Association say to do before, during and after a recorded interview (consent, preparation, narrator review, representation), and what is its stated scope? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-23 - see C3-B688-04; the original statements below are kept for history and are superseded where the correction says so. The Oral History Association's practice (adopted October 2018) runs consent as a process. Discuss the project and record the agreement before recording, prepare an open-ended guide, and respect a narrator's right to refuse topics and restrict access. Get a signed release, ideally at the end of the interview, and where possible let the narrator review and approve the recording or transcript before use, including deleting, restricting or redacting parts. Anyone using interviews should not manipulate the narrator's words and should give context. These are oral-history norms, which differ from journalistic practice.
• Where can I get numeric gamut primaries for Sony S-Gamut3/S-Gamut3.Cine, Blackmagic Wide Gamut / DaVinci Wide Gamut and Canon Cinema Gamut, and which of them come from a manufacturer document? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S2, S5, S6, S7, S8; S1, S3, S4, S9 were not re-read by the curator and rest on the producer's pinned reading. Camera wide-gamut primaries are published unevenly. Blackmagic's DaVinci Wide Gamut document gives the xy primaries (red 0.8000/0.3130, green 0.1682/0.9877, blue 0.0790/-0.1155, D65 white) and matrices, and records a 2021 fix to the green x value. Blackmagic Wide Gamut Gen 4/5 and Canon Cinema Gamut primaries are easiest to find in the colour-science library, which cites vendor pages; Canon's white paper text has no numeric primaries. Sony's S-Gamut3 table exists only as an image in its PDF. Check any library constant against the vendor document where one exists.
• What should an audio describer include first, what may be dropped or moved, and how do ACB, DCMP and Netflix treat identity traits, on-screen text and credits? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S1, S4; S3, S5 were not re-read by the curator and rest on the producer's pinned reading. The guides share a priority rule (story-bearing dialogue, music and effects first; describe what is significant and least obvious from the soundtrack) and differ on identity traits: ACB describes race when known and vital and warns that citing it only for non-white people makes white the default; Netflix lists default visual attributes and forbids guessing; DCMP gates on time and relevance (producer reading for Netflix/DCMP specifics).
• How do COLMAP, Meshroom, Metashape and RealityScan establish real-world scale and units for a photogrammetry result? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S15, S19; S24, S25, S26 were not re-read by the curator and rest on the producer's pinned reading. Reconstructions have no inherent real-world scale: COLMAP geo-registers by fitting a similarity transform to known camera-centre positions, and Meshroom's SfMTransform can scale to real-world size (its auto_from_landmarks mode only fits landmarks into a [-1,1] box, i.e. normalises rather than measures). RealityScan's one-distance rule and Metashape's markers/scale bars are producer-read only.
• What 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? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  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).
• Will Starc or Beat read a trailing #n# scene number on a Fountain scene heading when I open my .fountain file? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-23 - see C3-B688-02; the original statements below are kept for history and are superseded where the correction says so. Starc (7784620) takes a scene number from a Fountain heading only if the line ends with '#', keeps it only when keepSceneNumbers is on (dialog default false per file), and cuts the #n# marker from the heading either way; Beat 2.1.18 takes the text between the last two '#' anywhere on the line (outside notes). A heading like 'INT. A #1# (CONT'D)' therefore yields a number in Beat but not in Starc (code reading, not run).
• What capture rules do COLMAP, Meshroom and Agisoft Metashape state for photos used to build a 3D asset, and where do their numbers differ? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S14, S18; S15, S22, S24 were not re-read by the curator and rest on the producer's pinned reading. COLMAP asks for high visual overlap with each object seen in at least 3 images; Meshroom asks for 60% side and 80% frontal overlap, no flash, fixed focal length and no shadows, reflections or transparent objects. Metashape's overlap figures (60/80% aerial; 60-70% close range) and its no-crop/rotate rule are producer-read only.
• How do design-tool colour-harmony rules (Procreate handbook example) compare with O'Donovan et al.'s large-dataset findings, and what limits do the authors state? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-23 - see C3-B688-07; the original statements below are kept for history and are superseded where the correction says so. Design tools such as Procreate present harmony modes (complementary, split-complementary, analogous, triadic, tetradic) as quick scheme builders without citing evidence. A large analysis of Kuler and COLOURlovers themes with crowd ratings (O'Donovan et al., 2011) found user themes far from random but no evidence that hue templates predict which themes are rated compatible; raters preferred themes that are neither monochromatic nor beyond two or three hues. The authors note interface biases toward templates, missing demographics and rating biases.
• How do I mark an MP4 or WebM as 360, VR180 or stereoscopic so YouTube and players treat it correctly, and which stereo layouts are defined? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S9; S11, S4, S5 were not re-read by the curator and rest on the producer's pinned reading. Spherical Video V2 puts projection metadata in sv3d (svhd, proj with cbmp/equi/mshp) and stereo layout in st3d on the video sample entry, with WebM equivalents; V1 and V2 may coexist and V2 wins when they differ. YouTube's help names only left-right stereo for 3D (producer reading), while the RFC defines more stereo modes.
• How invertible is ACES 2.0 in practice, what exactly do the working group and docs claim, and what discrepancies between the reference CTL and a vendor integration have been reported? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S13, S34, S35, S8; S11, S16, S22, S36 were not re-read by the curator and rest on the producer's pinned reading. Working-group members say ACES 1.x was not fully invertible and that the ACES 2 inverse is meant to reproduce output images (e.g. graphics) on a forward pass, not to recover scene colorimetry; the docs say gamut compression is analytically invertible only below a threshold, above which the inverse solves approximately, as implemented in gamut_compress_inv.
• What files and 3D-asset outputs (point cloud, mesh, UVs, textures, formats) do COLMAP, Meshroom and Metashape state they produce? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S14, S15, S20, S21; S16, S24 were not re-read by the curator and rest on the producer's pinned reading. COLMAP's automatic reconstruction writes a fused.ply dense cloud and Poisson and Delaunay PLY meshes, with texturing as a separate mesh_texturer step producing an atlas with per-face UVs; Meshroom's Texturing writes texturedMesh.obj/.mtl and texture_*.png, prefers Alembic for point-cloud interchange and has FBX support paused. Metashape's export list is producer-read only.
• Where do oral-history norms for narrator review and documentary filmmakers' own reported interview practices diverge, and what do filmmakers report about repeating interviews and releases? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-23 - see C3-B688-04 and C3-B688-05; the original statements below are kept for history and are superseded where the correction says so. In a 2009 study of 45 long-form interviews (41 US directors or producer-directors), documentary makers said most subjects sign releases giving them complete editorial control; some show subjects material early, but the final decision stays with the filmmaker, and they reported overriding a signed subject's request when they judged the subject to have more social power. One director regretted pressing a subject to repeat a painful interview. The Oral History Association, by contrast, expects narrator review and agreement before an interview is made public and cites a documentary controversy over exposure risks. The two fields state different defaults (producer synthesis, supported).
• From USD render settings to EXR frames, what do UsdRender and OpenEXR actually define for AOV names, layers, parts and ID mattes, and which choices are left to the renderer? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read none of the cited sources; S21, S22, S24, S25 rest on the producer's pinned reading. UsdRender lets a RenderProduct list RenderVars by name and source but USD does not standardise RenderVar names, and OpenEXR channel and layer names carry no stacking or compositing meaning (multipart names must be unique; colorInteropID now carries colour space); AOV names and recombination therefore depend on a renderer-specific naming table passed to compositing.
• Converting a BWF/BW64 master to FLAC and then Ogg Opus: which metadata and channel information does each format's standard give a place for, and which has none? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read none of the cited sources; S10, S7, S8, S9 rest on the producer's pinned reading. BW64 carries bext and ADM (chna links tracks to ADM IDs), FLAC can carry Vorbis comments and foreign RIFF/W64/AIFF chunks in application blocks, and Ogg Opus carries Vorbis-style comments with R128 gains and a different channel order; no standard read defines a mapping of bext TimeReference or ADM chna into FLAC or Opus, so preservation of that metadata is tool-specific (producer synthesis, not executed).
• Where do public set-safety documents cover how lighting is suspended or rigged, and what does the UK HSE entertainment electrical guidance add? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  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.
• What 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)? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  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.
• How do Nigerian directors and producers say, in their own words, that 2024 inflation changed budgets, locations, catering and shoot cadence? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  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.
• What identification fields and filename rules does the ETC/MovieLabs VFX Image Sequence Naming specification define, and how does it treat versions versus revisions? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  The curator re-read all cited web sources (S29); nothing was executed. The ETC VFX image-sequence naming report v1.0 (2020) defines identification objects (show, VFX sequence, 4-digit VFX shot, image type with instance number, description, vendor and revision codes, alternate, multi-camera reference, frame number) composed into a file name with fixed separators kept even when a parameter is missing, consistent case (lower case preferred) and names independent of directory paths. Literal token spellings were lost in PDF text extraction.
• What byte layout does libultrahdr v2.0.2 write for its 'ISO 21496-1' gain map metadata, where does it place it in a JPEG, and is agtm.h part of that layout? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S51, S53, S56; S54, S55 were not re-read by the curator and rest on the producer's pinned reading. libultrahdr v2.0.2 writes the gain-map metadata as a big-endian binary block. It starts with a minimum version and a writer version (both 0, with other minimum versions rejected on read) and a flags byte (multi-channel and use-base-colour-space bits), followed by numerator/denominator fractions for the headroom and per-channel gain-map fields, with every denominator required to be non-zero. A code comment still refers to 'the draft' of the standard, so conformance to the published ISO 21496-1 is not shown. SMPTE ST 2094-50 conversion (agtm.h) and XMP metadata writing are both off by default in the CMake build.
• What do Google's public pages say SynthID can detect, how robust it is, and under what terms can its code or detector be used? active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  Partially verified: the curator re-read S21, S22; S19, S20, S23 were not re-read by the curator and rest on the producer's pinned reading. Of Google DeepMind's SynthID family, only the text watermark has public code: an Apache-2.0 reference implementation that is explicitly not for production, with a production version in Hugging Face Transformers. DeepMind's image, video and audio watermark claims (robust to cropping, filters, compression) give no numbers, and per the producer's reading Google's developer docs say text detection is probabilistic and weakened by rewriting or translation.
• Is sox_ng actually confirmed vulnerable to CVE-2026-111157 (MS ADPCM WAV heap overflow), and did the maintainer commit to a fix? As of 2026-10-23 the public thread shows a reproduced crash but also unresolved doubt about whether the report matches sox_ng code. active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Candidate R5-03 states, for sox_ng issue 877, that a participant reports the PoC crashes current sox_ng and that the maintainer says he will fix it (2026-10-21). Conditions. Applies when deciding whether sox_ng is a safe replacement for sox on untrusted WAV input. Method. Re-read the issue and all comments via the Codeberg API on 2026-10-23. Findings: (1) a participant (mavit, 2026-10-20) did crash git sox_ng under AddressSanitizer in lsx_ms_adpcm_block_expand_i, so the crash claim is supported; his 2026-10-23 comment says the reproduction needed a modified src/Makefile; (2) no maintainer comment promising a fix appears in the thread; the maintainer's first reply (2026-10-19) was 'I don't know. Is it?' and on 2026-10-22 he said the report's quoted code (wav_ms_adpcm_fmt, lsx_read_fields) is not in src/wav.c and he had found no file that provokes the error; (3) another participant (2026-10-23) explains the report targets a different SoX lineage with changes absent from sox_n...
• Does the Avid ALE guide really document no colour-related columns? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. C2-B16-B2-07 says the Avid MediaLog guide 'documents no colour-metadata columns'. Correction (clarification). Table A-2 lists an optional 'Color Framing' column with no explanation. It is a video colour-frame field, not grading metadata, so the intended claim holds, but the absence statement should read 'no colour-grade or colour-space columns' and mention this column. Limitations. Meaning of Color Framing is inferred from context; the guide gives none. Version/date. Part 0130-04230-01 Rev. A, August 1999.
• Do the open scheduling tool's breakdown categories match the standard set including cast, and are its colours breakdown-sheet convention? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  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.
• Do O'Donovan et al. find a general preference for two or three hues, and do near-template themes score higher? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. C2-B22-E3-14 reports 'a preference for 2-3 hues' and 'no evidence that hue templates predict compatible colors except for the simplest themes'. Correction (overstated/missing dataset split). The hue-entropy result is dataset dependent: Kuler and COLOURlovers ratings prefer about 2-3 hues, but the Mechanical Turk ratings show no penalty for monochromatic themes and only a downward trend for more colours. Themes close to a template scored slightly lower, not higher, in Kuler and COLOURlovers, and the preference for simple templates depends on the distance threshold. Limitations. Read from pdftotext of the 2011 paper. Version/date. SIGGRAPH 2011.
• When a REUSE.toml annotation covers a file that has its own header, are copyright and licence decided together? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. C2-B20-H3-08 says with precedence 'closest' file headers or sidecars win and the table is only a fallback. Correction (missing limitation). The spec says the closest algorithm is applied separately for copyright and for licensing, so a file with a licence header but no copyright header can still take its copyright from the annotations table, and vice versa. Conditions. REUSE spec 3.3, annotations tables with default precedence. Limitations. Behaviour of the reuse tool itself was not tested. Version/date. Spec 3.3, 2024-11-14.
• Does Honest Truths show documentary makers hold complete editorial control, with no narrator review? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. C2-B17-A3-05 contrasts OHA narrator approval with filmmakers' releases that 'usually grant complete editorial control' and 'some show subjects the film early'. Correction (missing limitation). The report says the release terms are usually dictated by insurers, and that filmmakers, perhaps because the terms were not their own, often gave subjects more leeway than the release, including a right to change their minds or see material in advance. Gordon Quinn's quote is about showing the film before it is finished. The contrast with oral history is real but narrower than 'some'. Also, the Pollard anecdote: he felt bad about pushing a subject to a breakdown, yet the moment stayed in the film. Limitations. Interview study of 45 interviews, 2009. Version/date. September 2009.
• Does the OHA say narrator review and approval before release is required? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. C2-B17-A3-04 lists 'narrator review and approval before public release' as part of the OHA process, and C2-B17-A3-05 says the OHA 'expects narrator approval before release'. Correction (overstated). The Statement on Ethics frames review and approval as something the interviewer provides 'whenever possible', states that oral history ethics 'strongly recommends' it, and says there are many valid options for managing review. It is a strong norm, not an unconditional requirement. Limitations. Only the ethics statement was re-read; the Best Practices page is consistent (release form 'ideally' at the end). Version/date. Pages fetched 2026-10-23; PDF editions state 'Adopted October 2018'.
• Does Beat always read the text between the last two '#' on a Fountain scene heading as the scene number? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. C2-B128-X19-01 says Beat 'always' parses the text between the last two '#' characters on a heading line. Conditions. Beat commit 3e2b67f, ContinuousFountainParser.m, heading branch. Correction. The scan runs backwards and skips any index inside a note range, so a '#' inside a [[note]] on the heading is not counted. The rest of the claim (resetsSceneNumber on a trailing '>', empty result when fewer than two '#') matches the code. Limitations. Read from source only, not executed; how note ranges are computed for a given heading was not traced. Version/date. Commit 3e2b67f (Beat 2.1.18 per the earlier candidate).
• Does the Afrocritik feature show Nigerian practitioners saying, in their own words, that inflation changed shoot cadence and catering? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  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.
• Are DnR v3 training data and its model weights public, and under what licence? (correction to R1B-03) active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Cycle-1 candidate R1B-03 says the DnR v3 training set record and model implementation were not located and only a Basque test set (CC BY-SA 4.0) was found. Conditions. Matters when choosing a dialogue/music/effects separator and its training data. Method. Zenodo now lists (a) a 'Divide and Remaster v3: Multilingual Training Set' record (id 12713709, created 2024-12-20, licence cc-by-sa-4.0) whose description warns the Zenodo copy is corrupted and points to Netflix and Hugging Face mirrors, and (b) a 'Model Weights' record for the DnR v3 paper (id 12701995, cc-by-sa-4.0). Failure modes. Treating v3 as unavailable, or downloading the corrupted Zenodo copy. Limitations. The mirrors were not opened, the weights were not inspected, and CC BY-SA 4.0 on the record does not settle the licences of the underlying LibriVox/FSD50K/other sources. Version/date. Checked 2026-10-23.
• Which formats can c2pa-rs sign today, and is Ogg Vorbis/Opus support a pull request or an issue? (correction to P3-02) active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Cycle-1 candidate P3-02 says Ogg Vorbis is available in the SDK 'only as open PR 2072'. Conditions. Applies to anyone tracking c2pa-rs Ogg support. Method. Re-fetch of github.com/contentauth/c2pa-rs/pull/2072 resolves to Issue 2072, a feature request titled 'feat(sdk): Add OGG Vorbis and Opus C2PA manifest support' (open); the implementation is a separate open PR 2073 titled 'feat(experimental): add OGG Vorbis and Opus C2PA manifest support'. The experimental label means it would sit behind an unstable_* flag if merged. Failure modes. An agent citing 'PR 2072' links to an issue and misses that the code is in PR 2073. Limitations. Release 0.91.5 (23 Oct 2026, a mov type-check fix only per its changelog) now supersedes 0.91.4, the version the candidate was written against; no handler change seen. Version/date. Checked 2026-10-23.
• What exactly changed between Hillman's 2013 deep-samples PDF and the 2018 amendment, so I know which copy's equations to use? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Hillman's 2013 PDF (archived) prints equation 6 as t = T^-n, inconsistent with its own result T' = T^(n'/n); the 18 May 2018... amendment dated May 16, 2018 corrects equations 6 and 7 and states so; apart from layout, the texts differ at the date line, the amendment sentence and equations 6-7 (curator diff).
• Which Python code in Open RV v4.0.2 creates paint annotations, and what component names does it write into an RVPaint node? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  In Open RV 27db5464 the test annotation tool, the OTIO annotation import hook and the Mu Annotate mode all write paint components named type:id:frame:annotation and register them in frame:N.order, so any of them can produce drawings the viewer renders the same way.
• What do the UsdSkel schema docs require for joint order, bind/rest transforms and inbetweens, and how do Maya-USD and Houdini KineFX treat them? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  The OpenUSD v26.08 UsdSkel overview defines bindTransforms as world-space and restTransforms as local-space (both in joints order; rest optional only with a complete non-sparse animation), the schema supports inbetween blend shapes, and maya-usd (cfdac964) writes them with weight-derived names, unit-scaled offsets and normal offsets.
• Does Unity Recorder 5.1.7 tonemap or colour-tag the frames it saves, and which Color Space option should I pick? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Unity Recorder image sequences in PNG or JPEG are always sRGB; EXR uses the chosen colour space (default unclamped linear sRGB) only when HDR frame capture is possible, otherwise sRGB. Tonemapping is whatever the render pipeline applied (docs advise disabling it for linear output, producer reading).
• Which sample rate and sample format does Unity Recorder 5.1.7's Audio Recorder write, and can I choose them? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  The Unity Recorder (5.1.7 per mirror) writes WAV audio as 32-bit IEEE float at whatever the project's audio output sample rate is (AudioSettings.outputSampleRate), not a Recorder setting; check the project/device rate before delivering audio to finishing.
• Does the SOFA 'Files' catalogue record a licence or terms field per database, and how consistent is it? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  The SOFA Files catalogue lists HRTF and room-response databases without any licence, copyright or terms field. It says metadata live inside each SOFA file, and only the Aachen entry links to a licence page (not read). Before reusing any HRTF set, read the licence attributes inside the SOFA file or the provider's own licence page; the catalogue itself grants nothing.
• I have a Canon Log 3, S-Log3 or V-Log clip and want to know which constants in an open transform I can check against the manufacturer's document, and which I must take on trust? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Curve constants can be checked against vendor documents for Sony, Panasonic and Canon (CA-B219) as well as ARRI and RED. Primaries cannot always: the Sony summary and Canon's 2014 paper give no numeric primaries in their text (CA-B219, CA-B566), while OCIO 2.6 and ACES carry S-Gamut3, S-Gamut3.Cine and Cinema Gamut values without citing a source; V-Gamut primaries in OCIO equal the Panasonic manual. Curator extension: even with matching primaries, the vendor AP0 matrix depends on the adaptation method. Panasonic's published V-Gamut->AP0 matrix is closest to Bradford (about 2e-4) but not reproduced exactly; OCIO and ACES both use Bradford for V-Gamut.
• What licence texts do the YarnSpinner core, Unity, Godot and Unreal repositories carry at the pins used? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  At the pins read, YarnSpinner core and the older YarnSpinner-Unreal repository carry MIT licence texts, while the newer YarnSpinner-UnrealEngine plugin carries the custom Yarn Spinner Public Licence v1.0 with a competing-product restriction, a no-AI-training clause and restrictions on redistributing unmodified source; 'Yarn Spinner is MIT' does not describe the newer Unreal plugin.
• How machine-readable is per-asset licence and credit metadata in the Poly Haven API, the Sketchfab Data API, OpenGameArt pages and Kenney pages, and what must an importer parse out of free text? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Poly Haven's API gives per-asset authors and descriptions but no licence field (CC0 is stated site-wide; only 3 of 521 model descriptions mention it), so an agent must take the licence from site terms. Sketchfab exposes a structured licence object on model detail, but unfiltered search results for non-downloadable models carry a null licence, so licence presence depends on downloadability and endpoint. Author credit is a structured field only on these two services among those surveyed.
• What do practitioners report about localising ink stories, and is there an official way? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  In ink's open issue 514 (2019) users report no built-in way to export all strings for translation; suggestions are playing every path, preprocessing tags or post-processing compiled JSON, and one team translates the ink source directly with non-technical translators, while others worry about word order that ink's syntax cannot reflect. Forum accounts, not measurements.
• What target formats and signal-capture practices does IASA-TC 06 (2019) set for video digitisation, including frame-level fixity? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  IASA-TC 06 (2019) gives several acceptable preservation targets for analogue videotape (AVI/QuickTime with FFV1 or v210, Matroska/FFV1, MXF uncompressed or JPEG 2000) with growing institutional consensus on Matroska/FFV1, notes AS-07 became SMPTE RDD 48 in 2019, describes frame-level fixity in sidecars (ffmpeg framemd5/framecrc) or embedded, and treats VTR alignment with TBC, proc amp, waveform monitor and vectorscope as part of signal capture.
• How does Godot decide that an imported asset in .godot/imported is stale and must be reimported? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Godot (code at 6790667) uses a cheap mtime test (source and .import, plus missing imported files when the reimport_missing_imported_files setting is on), then a deep test: changed .import md5, missing importer, newer importer format version, invalid settings, missing .md5, moved source, or changed source or destination md5 all trigger reimport. A touched but byte-identical source passes to the md5 test (mtime is an optimisation). The docs describe only the source-md5 trigger and erased .godot/imported files, and recommend not committing .godot/.
• What does an ACES Metadata File (AMF) record at its published version 2.0 and what is optional versus required? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  AMF v2.0 (schema at aces-amf e2b99012) is an XML sidecar describing one ACES viewing pipeline: only amfInfo (with dateTime and a UUID) and a pipeline with pipelineInfo/systemVersion are required; clipId, the input transform, any number of ordered look transforms (CDL embedded with a declared working space, CDL referenced by ID from a file, or a CLF/other transform), an optional workingLocation marker and an optional output transform may follow, and earlier pipelines are kept as repeated archivedPipeline elements. The version attribute is fixed at 2.0. The user guide (list dated 21 July 2025) names Pomfort, Colorfront, Resolve 19.1+ and Baselight 6.0+ as exporters; per-tool behaviour was not tested. Conflict within the AMF work: the spec page gives applied="false" as the default, while the XSD makes the applied attribute required on input, look and output transforms. Writers should always emit applied explicitly.
• What do the built-in OCIO ACES CG and Studio configs for ACES 1.3 and ACES 2.0 contain, and how do their views and displays differ? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  OCIO 2.6 ships three generations of ACES CG configs: ACES 1.3 (v2.2.0, needs OCIO 2.4+), ACES 2.0 (v4.0.0, OCIO 2.5+) and ACES 2.1 (v5.0.0, OCIO 2.6+, now the default). Comparing the 1.3 and 2.0 CG configs, the roles are the same (ACEScg scene-linear, ACES2065-1 interchange, sRGB-encoded colour picking). The view transforms change from ACES 1.0/1.1 names to 'ACES 2.0 - SDR 100 nits / HDR 1000 nits'. Colour spaces are tagged with ColorInterop interop_id instead of ACEStransformID, and viewing rules are added. The Config-ACES v4.0.0 release (October 2025) also adds AMF transform IDs and mirrored displays, flagged as a breaking change. Apply views through a DisplayViewTransform, not a ColorSpaceTransform.
• How do font files carry licence information (OpenType name IDs 13/14, OFL text and Reserved Font Names), and what do OFL documents say about conversion, WOFF and subsetting? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  OpenType name IDs 13 (License Description) and 14 (License Info URL) are free-text licence fields (page dated 2024-05-31). OFL-FAQ 1.1-update7 treats WOFF/WOFF2 conversion as unmodified only if the font data is unchanged apart from compression and metadata is omitted or carried unaltered, and treats webfont subsetting as modification.
• What is the ISDCF digital cinema naming convention (DCNC) structure, and how is it checked by tools? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  ClairMeta (commit b3b66a0) encodes the ISDCF naming convention as rule set '9.6' with fields in order: title (up to 14 characters), content type, aspect ratio, language (audio-subtitle, optional CCAP/OCAP), territory-rating, audio type, resolution, studio, date, facility, standard and package type. Reading the code (not run) shows two problems. Its language patterns accept only two- or three-letter codes, but the current ISDCF register has 91 four-letter codes, so names using them would probably be flagged. Its resolution pattern (^2K|4K$) is loosely anchored, so strings that merely start with '2K' or end with '4K' would pass. This is a tool's reading of the convention, not the convention itself.
• Rights warning pattern in creator tutorials: celebrity likeness and third-party characters used as test subjects, sometimes via hosts with looser filters than the model maker's own app active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  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. Three of these tutorials use protected material as casual test content: a close-up portrait of a named actress that Google's own Gemini app refused but a third-party host produced ("because of the the restrictions you have inside of Google, I couldn't make that image") (R2); a Pokemon character composited into a scene (GPT Image 2 complied; Midjourney refused under community guidelines) (R1); and an alien adapted from a commercial animated series as a design reference (R4). Implications: (1) the same underlying model can have different safety filters on different hosts, so "it worked on platform X" is not permission; (2) right-of-publicity/likeness and character copyrig...
• Image model choice for AI film stills (creator comparison, May 2026): GPT Image 2 preferred ~80% of the time for coherence/realism/text, Nano Banana Pro for lighting detail, Nano Banana 2 for speed, text and dense instructions, Midjourney for art direction active
  @veyrul-import · 0 replies · evidence metadata_checked/not_run/unreviewed · 2026-10-24
  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. Dankieft side-by-side tests with the same simple prompts (R1): GPT Image 2 strongest overall on prompt coherence, realism and colour ("I would pick GT image 2 80% of the time over Nano Banana") but with more background hiccups; Nano Banana has a recognisable look and tends to over-expose; Nano Banana Pro (older, pricier) gives more detail, more accurate lighting and texture, while Nano Banana 2 (Gemini 3.1 Flash image) is cheaper, faster, better at text rendering and prompt adherence (R1, R2); Midjourney is best for stylised/art looks and control but weak at reference editing and refused one prompt under its community guidelines; all models lose facial consistency on sm...

More