articles

API: /v1/records?type=article

• How does WorldMem store and retrieve earlier frames so a generated Minecraft or RealEstate10K world stays consistent after the camera leaves and returns, what revisit numbers does it report, and what does it cost? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  WorldMem keeps every generated frame as a token-level memory unit with a 5-number pose and a timestamp, picks up to a handful of units per step by field-of-view overlap and time difference (greedy, with a similarity filter), and lets the generating tokens cross-attend to them with pose/time embeddings. Its revisit tests compare regenerated frames against ground-truth frames with PSNR, LPIPS and reconstruction FID: 100 frames generated after a 600-frame memory bank on a custom Minecraft set, and five start=end trajectories over 100 RealEstate10K scenes. These are paper_result numbers on simulator poses; the paper's own tables disagree with each other and with the repository's expected-results block on some cells.
• What does WorldMemBench's fixed-reference multi-revisit protocol measure, what did it find about decay across returns, axis switches and off-screen events, and how reliable are its checks? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  WorldMemBench (260 cases: 200 static with human, object and environment targets, 60 dynamic with off-screen events) compares every prescribed return with the same first-visit reference over translation loops and yaw/pitch cycles, giving a score per revisit and counting a missing target as zero. On nine open video world models, the static leader (HY-WorldPlay) initiates only 31.7% of prescribed events, scores decay from the first to the third return on all eight metrics, and switching from a yaw cycle to a pitch cycle costs more. The paper adds pose-qualified subsets to separate memory from bad camera execution, and a context-policy study on LingBot World v2. Human agreement is 78.5-92.5% for static metrics but model-level correlation varies from 0.301 to 0.988.
• Which of the explicit-memory world-model papers and revisit benchmarks can I actually download or run, and what do their licence texts, metadata and gates say per component? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Observed on 2026-10-22: WorldMem has code (non-commercial licence text) and public ungated checkpoints with no licence field; SPMem has Apache-2.0 code and Apache-labelled checkpoints; VMem has MIT-labelled code that vendors a CC BY-NC-SA component and weights behind a Hugging Face access gate; Context-as-Memory has a released dataset but no code I could find; WorldTrace has no code I could find. The two newest benchmarks (R2M-Bench, WorldMemBench) release MIT code and data, but WorldMemBench's dataset card says its third-party images and the generated videos keep their original rights, and its examples set is labelled CC BY-NC by metadata. Nothing here was run, so 'released' means files are listed, not that they work.
• How does VMem index past views with surfels, what is its cycle-trajectory revisit test, and which parts of its release are open, gated or conflicting? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  VMem keeps the past views as images but indexes them through a coarse surfel model: each surfel stores which views saw it, new target cameras render the surfels to vote for the top-K most relevant past views, and an image-set generator (Stable Virtual Camera, SEVA) generates the next views from those. Its main contribution to evaluation is a cycle-trajectory protocol (go out, return along the same path, score every 10 frames of the return) with LPIPS/PSNR/SSIM plus rotation and translation distance of camera poses re-estimated from the generated frames. The tables contain rows that are identical across methods, which should be checked before reuse. Code is MIT-labelled but vendors a CC BY-NC-SA component, and the weights sit behind a Hugging Face access gate.
• What must a custom character satisfy to be used in Flow Studio, which terms govern its outputs, and how have the documented capabilities changed over recent dated releases? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The character requirements page (stamped Oct 19, 2026) sets file, polygon, hair-strand and DCC-version limits, T-pose and add-on validation requirements. The release notes show the platform broadening in 2026 from live-action replacement into a 3D Editor and a Canvas that hosts third-party generative video/audio models, so "Flow Studio" now covers more than the original tool. Output ownership is not stated on the pages read: the only terms linked from the help site are Autodesk's General Terms (Internet Archive snapshot 2026-10-16), which say users keep ownership of what they submit, define "Output", and disclaim responsibility for it; product-specific Special Terms were not read, so Flow Studio output rights remain unresolved.
• If I run the open Oasis 500M code, what resolution, frame rate, context length and action vector does it actually use, and which of those does the project text state? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At commit f59deef2c019c212bd0c5a3a5b986a51f3701847 the open-oasis README states keyboard-conditioned autoregressive generation but no resolution, frame rate or context length; those come from the code. The code resizes prompts to 360x640, encodes with a ViT-VAE (patch 20) to an 18x32 latent grid, conditions on a 25-entry action vector (VPT-style keys plus two camera values), and slides a window of at most 32 frames (max_frames=32). The only '20' is a default for the saved video's fps, and the 20 fps real-time claim is on the joint blog about the full model (Decart's inference stack), not the open 500M weights. The weights repo is gated and was not opened.
• Where do the licence layers of an open V2A model disagree or stack (ThinkSound's Apache vs non-commercial text, Stability's VAE licence, VGGSound/AudioSet/BBC training data)? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  ThinkSound publishes four incompatible-looking statements: HF weights card Apache-2.0 (S15, S16), GitHub README Apache-2.0 headline but research-only/no commercial use (S17), a bundled Stability AI Community License for the fine-tuned VAE (S18; commercial use needs registration and a revenue condition), and a paper statement that the dataset is strictly academic/non-commercial (S14). Its training sources include VGGSound (page: CC BY 4.0, copyright remains with video owners), AudioSet (CC BY 4.0 annotations for YouTube-linked data), Freesound and BBC Sound Effects (site: personal/educational use or license). A permissive label on one file does not resolve the others.
• When a model's GitHub LICENSE, Hugging Face licence metadata and model-card prose disagree, does Hugging Face or the vendor say which governs, and what does the HF licence field officially mean? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At the pinned revisions I found no Hugging Face page and no vendor text (Whisper, VibeVoice, AudioSeal) that ranks the GitHub LICENSE, the HF front-matter licence and the card prose against each other. HF's docs describe the licence field as the owner's way to 'let other users know' the permissions, shown on the model page and used for filtering; custom terms belong in a LICENSE file in the repo. HF's Terms of Service say content carrying a licence notice is intended to stay under that licence and that downloaded content is subject to the Terms 'and/or' the terms accompanying it. So the safe agent reading is: record each channel separately with its revision, call the HF field 'metadata says', and do not pick a winner.
• Do the Cosmos repositories, model cards and docs restate the NVIDIA Open Model License accurately, and do the dated versions that appear in model-card front matter differ from the current text? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Three dated agreement texts are readable without accepting anything: the current page (October 24, 2025), the text embedded in the Cosmos-Predict2.5-14B card (September 23, 2025, an abridged rewording), and the text embedded in the Cosmos-Tokenize1 card (January 6, 2025). The January text uses 'Model Derivatives', has no Special-Purpose Model clause, no 'Guardrail' definition and no Separate Components section, and its guardrail sentence has no 'substantially similar Guardrail' exception. GitHub READMEs and the docs licence page restate the licence only by name and link. One Cosmos 3 model repository ships a LICENSE file that matches the October 2025 text. Model-card 'Important Note' paraphrases of the guardrail clause differ between cards.
• Before I use, host, fine-tune or redistribute a Cosmos model that is under the NVIDIA Open Model License, what does each clause of the current agreement text say, and which of my questions does it not answer? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At the dated text 'Last Modified / Version Release Date: October 24, 2025' the agreement has 11 numbered sections. It grants a perpetual, worldwide, no-charge, revocable licence to use, modify, make derivatives of, sell and distribute the Model; allows redistribution with a copy of the agreement and a Notice line; requires 'Built on NVIDIA Cosmos' for Cosmos Models in several uses (including training another AI model with them or their outputs); states NVIDIA claims no ownership of outputs; and ends your rights automatically on litigation or on bypassing a Guardrail without a substantially similar one. It has no clause on hosting as a service by that name, no express patent licence (the word 'patent' appears only in the litigation-termination sentence) and no operative commercial-use clause beyond the preamble statement. This is a reading of text, not legal advice.
• The agreement ends my rights if I bypass a Guardrail without a substantially similar one. What do the agreement text, the Cosmos docs and the Cosmos code at a pin say about whether the guardrails can be turned off? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Three source kinds disagree on tone, not necessarily on fact: the agreement (October 2025) ends rights if you bypass a Guardrail without a substantially similar one; the Cosmos docs state the Cosmos-1.0-Guardrail model 'cannot be disabled' in the diffusion and autoregressive pipelines; and cosmos-predict1 at one commit defines a --disable_guardrail command-line argument and forwards it to the pipeline. The docs sentence and the code are about overlapping but not proven-identical pipelines; the code path was not traced or run. 'Substantially similar Guardrail appropriate for your use case' is not defined in the text.
• Did the AudioSeal vendor ever publish a separate weights licence file, what do the GitHub and Hugging Face histories show, and how can an agent check release-scoped weights terms? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Yes, in an earlier revision. At git 785b3b11 the AudioSeal repo has a LICENSE_weights file carrying Creative Commons Attribution-NonCommercial 4.0 text and a README that says code is MIT and weights CC-BY-NC 4.0. Commit 29565154 ('Re-update of license (#28)', committer date 2024-04-02) removes LICENSE_weights and edits the README; at HEAD e63a8a0e the only LICENSE is MIT and the weights are covered only by a README news line, while the README License section still names only code. The Hugging Face repo has no licence file in its tree, and its README gained license: mit in a later commit than its first two README versions.
• How does Physics-IQ test physical understanding in video models, which models and versions were scored, what were the results, and what do the authors say they do and do not show? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Physics-IQ (Motamed et al., Google DeepMind) gives a model the first 3 seconds (or the last frame) of a real, static-camera physics event and asks it to continue for 5 seconds, then compares to the real continuation with four motion-based metrics, combined and normalised so two real takes of the same scene score 100. At v3 the best of eight configurations (VideoPoet, multiframe) scores 29.5 and Sora (image-to-video) 10.0; visual realism judged by Gemini 1.5 Pro was not significantly correlated with physics score (r = -0.46, p = .249). The authors call the metrics proxies, say they are on the conservative side (they penalise camera moves and shot cuts), and say results do not show that future models cannot learn physics.
• Can the Meta open speech-translation toolchain (SeamlessM4T v2, SeamlessStreaming, SeamlessExpressive, NLLB-200) be used in a commercial dubbing pipeline, and which licence applies to which component? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Seamless code (and the W2v-BERT 2.0 encoder, UnitY2 aligner, toxicity tools and the text-only part of mExpresso) is MIT; SeamlessM4T v1/v2 and SeamlessStreaming weights are CC BY-NC 4.0 (the HF v2 card agrees); Seamless and SeamlessExpressive weights fall under a separate Seamless Licensing Agreement limited to noncommercial research that also bars commercial use of outputs, terminates on IP litigation against Meta and requires indemnity; NLLB-200 models are CC BY-NC 4.0 while fairseq code is MIT. Commercial dubbing with these weights is not permitted by these texts.
• How do open-source film-emulation tools encode manufacturer datasheet curves, and what unit and provenance traps does that introduce? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  In spectral_film_lut at 6307a98, film records store datasheet curves with an explicit exposure base (default 10): the Fuji Eterna 500 record uses base 2 and an x range of about -6.2 to +6.3 (consistent with stops), the Kodak 5219 record base 10 and -3.9 to +0.9 (consistent with log exposure), so mixing records without the base would misplace exposure. Provenance gaps: the Fuji grain curve is copied from Kodak 5207 and the Kodak rms is a computed value. MIT covers the code but says nothing about the datasheet-derived numbers. Fujifilm describes its digital Film Simulation as not merely replicating film.
• How do you turn a traditional blue-pencil sketch plus pencil 'inking' into clean digital line art in Krita, step by step? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Revoy's 2014 tutorial turns a blue-pencil sketch into clean line art in Krita 2.8.5 (Pentel 0.5 mm blue lead, 300 dpi scan, channel curves so blue drops out, Desaturate Max, Levels, manual cleaning); the page now carries the same 'AI derivation prohibited' footer, in tension with the author's statement that pre-October-2026 material stayed plain CC.
• What sketch, ink and colour pipelines did Revoy try for episodes 21 and 22 (2017), and why did he keep or drop each? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  David Revoy's 2017 production reports describe testing an inked, auto-coloured cel style on page one of episode 21, dropping it as too industrial, moving to charcoal-pencil crosshatching and then a grey-violet (#b8a2a6) paint-over, and for episode 22 a blue Polychromos pencil pass and a 9-shade flat palette; both pages are now served with 'CC-BY 4.0, AI derivation prohibited' footers, while his licence update says material before 8 October 2026 remained plain CC.
• Where does a Hugging Face model repository tagged creativeml-openrail-m keep its licence text, and how do I check what it contains? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The CompVis stable-diffusion-v1-4 card (133a221b) declares creativeml-openrail-m, allows redistribution and commercial use only with the same use restrictions passed on, and points to a Hugging Face Space for the full text, with no LICENSE-named file at the repository root; under the same metadata value one derived repo ships the CreativeML Open RAIL-M text (dated 22 Aug 2022) as LICENSE.md, while pt-sk/stable-diffusion-1.5 ships an unfilled MIT licence template as license.txt.
• Under what terms may an agent use AudioSeal code and checkpoints, and how does the repo's open detector sit with its own paper's advice? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At audioseal e63a8a0e the LICENSE is MIT (Meta Platforms) and a dated README news line (2024-04-02) says the MIT licence now includes the model weights and allows commercial use, while the README License section names only the code; the Hugging Face card front matter says license: mit. The AudioSeal paper (arXiv v2) advises that detector weights be kept confidential because a white-box attack raised detection error by around 80% (author-reported), which sits uneasily with publicly released detector checkpoints.
• What do the model cards of four open TTS releases say about voice consent, impersonation, provenance marking and licence, and where do card statements and licence metadata disagree? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At the pinned revisions, the VibeVoice-1.5B card declares MIT in its front matter while also limiting the model to research use and listing voice impersonation without explicit, recorded consent as out of scope, and claims an audible disclaimer and watermark in outputs (vendor statements); the XTTS-v2 card (Coqui Public Model License) advertises cloning from a 6-second clip with no consent text; the F5-TTS card declares CC BY-NC 4.0 with no use-policy text.
• What do the Llama 3.3 and Llama 4 Acceptable Use Policies prohibit, and how do the community licences they are incorporated into treat redistribution, modification, training on outputs and hosting? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At llama-models 0e0b8c51, the Llama 3.3 and Llama 4 terms permit redistribution and derivative models on conditions (copy of the agreement, 'Built with Llama' display, Notice file, 'Llama' at the start of the name of any distributed model trained or improved with the materials or their outputs; separate licence above 700 million MAU), and both AUPs prohibit representing the model's use or outputs as human-generated. For multimodal models, the Section 1(a) grant is withheld from EU-domiciled individuals and EU-based companies, but this does not apply to end users of products incorporating those models.
• What do the Gemma Prohibited Use Policy and Gemma Terms of Use (April 2026) say about hosting, redistribution, modification, training on outputs and output use, and how does the Gemma 4 licence differ? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The Gemma Terms of Use (last modified 1 April 2026) treat offering Gemma or a Model Derivative as a hosted service as Distribution, count models trained on Gemma's synthetic outputs as Model Derivatives (outputs themselves are not), allow reproduction and distribution only with the use restrictions passed on as enforceable terms and other conditions, and state Google claims no rights in outputs; the incorporated Prohibited Use Policy (21 Feb 2024) bars passing generated content off as human-made to deceive. The terms page points Gemma 4 to separate terms, and the linked page is an Apache License 2.0 page.
• What does the W3C imsc-tests suite contain for bidi, ruby and vertical IMSC features, and does any public source give per-engine results for it? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The imsc-tests suite publishes stimuli and reference PNGs but no engine results (producer reading); per-engine evidence exists only as implementer-reported processor results in the TTML2 report.
• What does Epic's public documentation say about how the Derived Data Cache decides an entry is invalid or must be regenerated? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The UE DDC documentation page is readable by plain GET (HTTP 200 on 2026-10-22) and describes cache hierarchy lookup/fill and disposability, not key composition or invalidation rules; the negative is about this page's content, not site readability.
• Which engine docs claim, deny or condition deterministic simulation, and what do they say about fixed timesteps? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Godot's docs (0914a4d4) state that physics in Godot, regardless of which physics engine Godot uses, is not deterministic.
• What is lens metadata, which values do Cooke /i lenses and ARRI cameras give per frame, and should I rely on the 'focal length' value as a camera solve input? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  In the ARRI SDI Metadata white paper dated 25 July 2023, ALEXA 35 SUP 1.2 changes add Lens Effective Focal Length (LDI26) and Lens Entrance Pupil Position (LDI27) alongside the existing Lens Focal Length (LDI04, 1/1000 mm).
• My stereo or immersive video file is going to Apple Vision Pro: which Apple movie profile (3D, Spatial Video, APMP for delivery, APMP for production) applies, and what does each allow? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Apple's Movie Profiles for Spatial and Immersive Media (v0.9 Beta, 9 June 2025) distinguishes 3D/Spatial Video (rectilinear MV-HEVC) from APMP delivery and production; APMP for production permits other codecs and frame-packed video while delivery is MV-HEVC, with vexu boxes signalling projection, packing and disparity adjustment.
• What does Apple publish about MV-HEVC stereo video files and the spatial metadata that turns a stereo MV-HEVC video into 'spatial video'? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Apple's HEVC Stereo Video Interoperability Profile is Version 0.9 (Beta) dated 21 June 2023; it is one of two Apple profile documents, the other being the 2025 Movie Profiles (CA-B068 V2-01).
• For a newcomer: which of GIMP, Krita and Inkscape handle more than 8 bits per channel and colour-managed (ICC) work, and which version should I assume? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  As observed on the project listings on 2026-10-21/22, GIMP 3.2.6 (released 2026-09-10) and Krita 5.3.4 / 6.0.4 (released 2026-09-15) were the newest listed releases; Krita's manual states 8 bit per channel is the lowest depth it handles, with 16-bit (and float) depths above.
• At the mix-to-delivery handoff, which stem, M&E and track-layout rules do Netflix v1.4, EBU R 123 and AS-11 state, and what does the receiver still not get? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  P2-04's statement that role labelling is positional (track number) holds for AS-11 UK DPP HD; for X-series files MCA labels carry roles (CA-B066 C2-03 reading).
• What does the public AS-11 UK DPP HD specification require for audio channels and track layout, and where does loudness appear? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  AMWA AS-11 UK DPP HD requires one mono channel per track, 24-bit/48 kHz PCM and exactly 4 or 16 channels, and its text contains no loudness requirement; AS-11 X9 instead describes audio layout through MCA labelling (Audio Layout Mode 0).
• Which Kodak documents say Status M densitometry is used for ECN-2 materials and LAD, and do they define how it relates to other density encodings or to a specific datasheet edition? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Kodak H-61A gives the camera-negative LAD standard patch nominal Status M densities of 0.80 R, 1.20 G, 1.60 B; this lab-control LAD is a different context from H-387's digital-recorder printing-density LAD (CV 685), and neither document converts between the two.
• What do Kodak's Cineon/DPX documents and the ACES ADX transforms define for printing-density encoding (0.002 density per code value, D-min 95, LAD 685), and which number comes from which document? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Kodak H-387 (Digital LAD, 2011) defines printing density as 0.002 x 10-bit code value with the digital LAD patch at code value 685 = printing density 1.370, states those are printing (not Status M) densities, and also tabulates the corresponding Status M values for the recorded intermediate stock.
• What reading-speed, line-length and duration limits do Netflix, BBC and EBU-TT-D state, per language, and where do they disagree? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Line and speed limits are scoped by document and platform: Netflix English (USA) sets 42 characters per line with 20/17 cps adult/children; BBC sets 37 characters for broadcast (Teletext) and a percentage-of-width rule online, with a 160-180 wpm live word rate. These must be presented per source, not merged into one caption limit.
• When a model repository ships code, weights, data references and generated output, what do the licence texts themselves say about each component, and where do the records disagree? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Under the OpenRAIL-M text, code/model/derivatives, outputs and training data are addressed by different clauses, and training Data is carved out of the licence; a single "licence: openrail" field cannot stand for all components.
• Can I reuse govuk-frontend, USWDS or Carbon source, and what do the licence files at the pinned tags actually say? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At the pins read, govuk-frontend is MIT (Crown Copyright GDS 2017) and Carbon's root LICENSE is Apache-2.0, while USWDS's LICENSE.md is a mixed notice: GSA modifications are public domain/waived, but bundled fonts (SIL OFL 1.1), Material Icons (Apache 2.0) and the sprite carry their own terms, so reuse rights depend on which paths are copied.
• Do the S-Log3, V-Log and Canon Log 2/Log 3 constants in the manufacturers' documents match those in OpenColorIO's built-in camera transforms and the ACES CTL colourspace transforms, and where do the implementations add something the documents do not say? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  At OCIO 10a43ec1 and ACES aces-input-and-colorspaces 29b722bc, the S-Log3 (261.5, 420, 0.01125, 171.2102946929), V-Log (0.01, 0.00873, 0.241514, 0.598206) and Canon Log 2 (0.24136077, 0.092864125, 87.099375, x0.9 scaling) literals are present as reported; the ACES V-Log CTL carries the explicit linear segment (5.6, 0.125, cut 0.181) that the OCIO Panasonic parameter list read does not spell out.
• What does the VRM Public License 1.0 text itself state, and how does it hand control to the per-model "License Settings"? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  The VRM Public License 1.0 (English page at vrm.dev/en/licenses/1.0/) grants Model Use and makes other rights depend on the License Settings stored in each VRM file; the alternative URL form vrm.dev/licenses/1.0/en/ returned 404 to curator GET, consistent with the producer observation.
• Which machine-readable licence and usage fields does VRM 1.0 (VRMC_vrm.meta) define, and how do they differ from VRM 0.x meta? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  VRM 1.0 meta requires name, authors and licenseUrl and defaults to restrictive values (onlyAuthor, personalNonProfit, credit required, modification prohibited, redistribution false), so an absent field is not a permission; VRM 0.x field names keep the misspelling "Ussage", which parsers must match literally.
• What does cinematographer Ava Berkofsky say about exposure level, light quality and rules of thumb for lighting dark skin on Insecure? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  In a 2017 Mic interview, cinematographer Ava Berkofsky (Insecure) describes the conventional ~70 IRE skin-tone target and says raising dark skin to 50-70 IRE makes the rest of the image look wrong; she says film school did not teach lighting nonwhite people.
• What was the Kodak Shirley card and why is it said to matter for how skin tones are exposed and printed? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  A 2014 NPR report (WNYC copy) describes Shirley cards as print-lab reference images for setting skin tone, quotes a lab technician on their use, relays Lorna Roth's view that film dynamic range was biased toward white skin, and reports later multiracial reference cards.
• What do the D-Cinema audio channel symbols VIN and HI (and the other common channel symbols) mean in SMPTE ST 428-12, and is the document public? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  SMPTE ST 428-12:2013 Table 1 defines HI (UL byte 0Eh) as a dedicated hearing-impaired dialog-intelligibility channel and VIN (0Fh) as a dedicated visually-impaired narration channel; the standard labels channels and does not require a soundtrack to carry them (producer reading of scope; Table 1 rows reinspected).
• Is SMPTE ST 429-16 publicly readable at pub.smpte.org, and what does it define for audio channel labels such as VIN and HI? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  ST 429-16:2023-09 gives MainSoundConfiguration a recommended (should) ABNF syntax with 1-8 character tokens and delegates label meanings to ST 428-12 symbols; HI and VIN appear only in an informative Annex B example.
• How does a director use storyboards to plan and to persuade a studio (Ridley Scott's account)? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  In the archived BAFTA transcript, Ridley Scott says he boards every film and now draws boards himself, and attributes a budget rise 'from four point two to eight point five' to a storyboard (as told; units not stated).
• What concrete paper tools (scripted shot lines, overhead sketch, shot list) does a cinematographer describe for turning a script into coverage, and who uses them? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Jay Holben's ASC-published guide (2021) describes lining the script with lettered coverage lines (e.g. A - Wide Master) and two thumbnail types, a rough storyboard and an overhead sketch (director's plan / bird's eye) for crew communication.
• In Blender's GPU compositor what does texture_load do for out-of-range reads, and what does that mean for the Keying node's edge test at image borders? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Blender's GPU compositor texture_load(sampler2D, int2) clamps to the edge texel (replicate), only the fallback overload returns a chosen value and texture_load_unbound does not guard; the Keying tweak-matte shader uses the clamping form for every read, so border windows see replicated border values (static reading at f46990f5).
• I have splat values from a typical training export (log scales, logit opacity): which values must I convert before putting them in a glTF KHR_gaussian_splatting file or a USD ParticleField3DGaussianSplat prim? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Both glTF KHR_gaussian_splatting and OpenUSD ParticleField3DGaussianSplat store linear scale and linear 0..1 opacity; the OpenUSD example converter applies exp() to PLY log scales and a logistic sigmoid to PLY logit opacity and treats rot_0 as the quaternion real part; glTF marks out-of-range opacity invalid and defines diffuse colour from SH0 with a +0.5 bias at render time.
• How do animatic durations stored in milliseconds, seconds or H:MM:SS:FF convert to frame-exact exposures, and where can rounding drift occur on export? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Storyboarder (8b81a25c) stores board durations in milliseconds and its FCP XML exporter rounds each board to whole frames before accumulating, with timebase = ceil(fps) and an NTSC flag for non-integer rates (static reading).
• How does the Japanese-method digital timesheet workflow (24-frame seconds, 3-frame holds, empty cells, .xdts exchange) work, as described by a studio-method tutorial? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  A CELSYS tutorial describing Nippon Animation's digital drawing method sets the timeline to 24 frames per second, reads it horizontally (unlike paper sheets) and exchanges timesheet data as .xdts between the digital timesheet editor and CLIP STUDIO PAINT (Japanese original reinspected).
• Do measured studies support 'bigger text and looser line spacing are always more readable', and does a specialised dyslexia font help? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-23
  Katzir et al. (2013, PLoS ONE) report 100 children in the abstract but 45 second graders and 45 fifth graders in the experiment methods; for second graders smaller font and longer lines lowered comprehension, line spacing showed no effect, and fifth graders comprehended better with smaller font (authors frame as desirable difficulty).

More