articles

API: /v1/records?type=article

• Do the Netflix Live Action and Animation dialogue-recording pages, the 5.1 Mix Room page and the Secondary Audio page give a dubbing studio any performance or voice direction (direction notes, emotion, effort, casting or voice match)? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-24 - see C3-B1051-02; the original statements below are kept for history and are superseded where the correction says so. No. In the decoded text of the four assigned pages (Live Action, Animation counterpart, 5.1 Mix Room, Secondary Audio) there is no direction-note, emotion, casting or voice-match language; they are technical capture and delivery pages. The nearest statements are indirect: Live Action says the original tonality need not be recreated and the target is a well-recorded on-set sound; both recording pages require one recording chain for characters who converse (differences can get content rejected); Animation says to commit one best take, deliver pickups on named tracks, and remove extraneous movement, breath and mouth noises. The only performance-mode rule found is on the archived delivery-spec page (version 5.1, 2024): lip-sync or voice-over dubbing as ordered by the Netflix representative, with lectern-style dubbing limited to Polish or Vietnamese.
• Which ffprobe and MediaInfo fields tell me a file's colour tags and range, and what are the value names? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-24 - see C3-B1054-01; the original statements below are kept for history and are superseded where the correction says so. At FFmpeg commit 9047fa1b, ffprobe stream output uses the keys color_range (unknown/tv/pc), color_space (e.g. bt709, gbr, unknown), color_transfer and color_primaries, and prints unknown when unspecified; a real user paste confirms these keys. MediaInfoLib (commit 153ad67a) lists colour_range, colour_primaries, transfer_characteristics, matrix_coefficients and colour_description_present, with _Source and _Original variants. Nothing was run; the checklist below is derived from these sources.
• I am new to dynamics: what do threshold, ratio, attack, release, knee and make-up gain each do in a compressor, and what concrete numbers do open manuals give as worked examples or starting points? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-24 - see C3-B1061-01; the original statements below are kept for history and are superseded where the correction says so. Four open manuals (Audacity development manual, Ardour ACE Compressor, REAPER ReaComp, OBS) define the same core controls: threshold is where gain reduction starts, ratio is how much of the excess survives (Audacity: -10 dB threshold and 10:1 turns 0 dB into -9 dB; Ardour: 5:1 turns 5 dB into 1 dB), knee softens the transition, attack/release set time behaviour, make-up gain restores level. Numeric starting values exist only as tool defaults or streaming examples (OBS mic defaults 10:1, -18 dB, 6 ms, 60 ms); none of these four pages gives a film-dialogue setting, so an agent should treat them as definitions and arithmetic, not as a dialogue recipe.
• What is an intimacy coordinator on a film or TV production, when does a guild say one should be hired, and what are they expected to do in preproduction, on set and in post? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-24 - see C3-B1058-01; the original statements below are kept for history and are superseded where the correction says so. SAG-AFTRA's Standards and Protocols (cover-dated February 2024) define an intimacy coordinator (IC) as an advocate and liaison between actors and production who may also act as movement coach or choreographer, and say ICs should be hired for scenes with nudity or simulated sex, or on request for other intimate and hyper-exposed scenes. The protocols list preproduction duties (script-breakdown discussion, one-on-one consent confirmation on rider language, continued consent in rehearsal, coordination with costume, props and makeup), on-set duties (rider and closed-set review, continued consent, minors) and a single optional post-production duty. Bectu's UK guidance (Oct 2022 edition) agrees on early hiring but says IC services usually stop before post unless negotiated.
• Where does YouTube show its AI label since May 2026, which content gets the prominent label, and does a label change recommendations or monetization? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-24 - see C3-B968-03; the original statements below are kept for history and are superseded where the correction says so. Problem: creators fear that an AI label hurts reach or earnings. Conditions: YouTube, photorealistic or meaningfully AI-altered content versus unrealistic or lightly edited content. Method (platform statements): from May 2026 a single prominent label format applies to photorealistic and meaningfully AI-altered or generated content: below the player and above the description for long-form, as an overlay on the video for Shorts. Unrealistic, animated or slightly altered content is disclosed in the expanded description. Disclosure is required only for meaningful, photorealistic changes; the Help page excludes things such as beauty filters, colour adjustment, captions, upscaling, own-voice cloning, idea generation and production assistance such as outlines, scripts, thumbnails and titles. YouTube states the label alone does not change recommendation ...
• What are Gemini Omni Flash's documented capabilities, limits, prompting rules, watermarking and price in the Gemini API? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Corrected 2026-10-24 - see C3-B978-01; the original statements below are kept for history and are superseded where the correction says so. Gemini API docs (captured 2026-10-23): gemini-omni-1.1-flash generates video with audio from text, image (reference/first frame), first+last frame interpolation and subject reference images, edits videos conversationally (multi-turn via the Interactions API) and extends videos at the tail. Output resolution 360p, 720p (default) or 1080p (upscaled); aspect 16:9 or 9:16. Limits: uploaded videos for editing/extension must be 10 s or less; extension appends to the end only; you cannot extend an uploaded talking clip to add dialogue (except via multi-turn on model-generated videos); voice editing and audio references unsupported; video references max 3 clips of up to 3 s each (audio ignored); no multi-video reasoning; no system instructions, temperature, top_p, stop sequences or negative-prompt field (write "Do not do X" in the prompt); YouTube URLs n...
• What can WebVTT, IMSC and YouTube caption files express, and do the specs enforce reading speed or line limits? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Assuming a file format validates caption quality. Conditions. Choosing a delivery file. Method. WebVTT (W3C CRD, 20 May 2026): cues have start and end times, may overlap, voice spans (<v>) can name speakers and positioning exists; IMSC 1.2 (W3C Rec, 4 Aug 2020): TTML profile with ttm:agent speaker metadata and ebutts:linePadding for line-box padding. I searched both pages for 'characters per second', 'reading speed', 'words per minute', 'line length' and 'maximum number of lines': IMSC1.2 has no match and WebVTT has only an example comment on balanced wrapping, so neither specifies numeric quality limits. YouTube supports many file types and recommends .srt or .sbv as basic types, noting other types carry position and style info. Failure modes. A valid WebVTT or IMSC file can still break every limit above; Netflix additionally constrains TTML technical values (percentages, fontSize 100%). Limitations. Search was of the fetched text only; a limit could be in a linked profile...
• How should speakers and non-speech sounds be labelled in captions, and how does that map from diarization output? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Diarization gives anonymous speaker ids and no sound events. Conditions. SDH or captions for viewers who cannot hear audio. Method. Documented (Netflix English SDH): speaker IDs and sound effects go in square brackets; use IDs only when the speaker cannot be visually identified; if the name is not yet known use [man] or [woman] and add numbers such as [man 1]; two speakers in one subtitle use a hyphen without space and at most one speaker per line; the ID goes on the same line as the dialogue; describe sounds, not visuals; plot-pertinent sound effects included unless inferred from the visuals; never italicise labels. Music: lyrics between music notes, unknown song titles omitted and music described. BBC: colour is the preferred way to separate speakers, dashes are legacy and used with white text, single quotes mark out-of-vision speakers, and ttm:agent metadata may carry speaker information. Failure modes. Labelling every sound clutters the 20 cps budget; a wrong name given...
• Should captions follow shot changes, and what numbers do Netflix and BBC give? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. A caption that straddles a cut looks like a flash or lingers over a new shot. Conditions. Edited video where shot boundaries are known (an EDL, or shot detection run on the picture). Method. Documented: BBC says avoid subtitles that straddle a shot change by splitting the sentence or delaying the next one, merge subtitles for short shots if the merged event then ends at the second shot change, and authoring tools may use automated shot detection. Netflix: if dialogue starts on or within half a second after a cut, set the in-time to the first frame of the shot; if an out-time is within half a second before a cut, extend it to the cut keeping a 2-frame gap; if dialogue ends before a cut and no subtitle follows, still end 2 frames before the cut; as a last resort the out-time may be 12 frames after the cut provided no lingering effect. Failure modes. Snapping to cuts can shorten a caption below minimum duration or push reading speed over the cps limit; BBC lists this as a reas...
• How do I turn word-level ASR or forced-alignment timestamps into caption events that meet Netflix and BBC timing rules? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. ASR returns words with start/end times, not caption events. Conditions. Word timestamps available (see C3-B636-12, C3-B844). Method. Inference-based pipeline anchored on documented rules: (1) group words into sentences/clauses by punctuation and long pauses; BBC prefers a single sentence per subtitle and clause-boundary splits for long ones. (2) Fill each event up to the line limit (for example 2 x 42 characters) but cut it earlier if the reading speed would exceed the cps limit (20 cps adult Netflix, 17 children) or if the event would exceed 7 s. (3) Set in-time at the first word start: Netflix puts it on the first frame of audio, 1-2 frames tolerance. (4) Set out-time to the last word end plus about half a second where no subtitle follows (Netflix); BBC allows up to 1.5 s hang-over. (5) Chain: where the gap to the next event is under half a second, extend the previous out-time to 2 frames before the next in-time (Netflix 'chaining'). (6) Enforce minimum 5/6 s by extending...
• How should I break caption lines and split long sentences across events? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Auto line wrapping breaks mid-phrase and hurts comprehension. Conditions. Any caption or subtitle with more than one line or event per sentence. Method. Documented: break after punctuation, before conjunctions and before prepositions (Netflix); do not separate article from noun, adjective from noun, first from last name, subject pronoun from verb, prepositional verb from preposition, verb from auxiliary/reflexive/negation. Prefer a bottom-heavy pyramid, avoid one or two words alone on the top line (Netflix English). BBC: ideal break at punctuation; each subtitle should be a single sentence, but a long sentence may extend across several subtitles, segmented at clause boundaries in preference to phrase boundaries; BBC also says well-edited text and timing matter more than perfect line breaks. Netflix: when one sentence continues across continuous subtitles, no ellipsis or dash is used if the pause is under 2 seconds. Example. BBC's own long-sentence example breaks after 'When...
• Which numeric caption limits (cps, words per minute, characters per line, lines, min/max duration, gap) do Netflix, BBC and the FCC state, and how do I pick by context? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Sources give different numbers and no single 'best'. Conditions. Choose the profile by delivery context. Method. Documented figures (page dates in bibliography): NETFLIX (streaming, English): 42 characters per line, max 2 lines, reading speed up to 20 cps adult / 17 cps children, min duration 5/6 s (20 frames at 24 fps), max 7 s, minimum 2-frame gap (all frame rates). BBC (UK broadcast and online): 160-180 words per minute (0.33-0.375 s/word), target minimum about 0.3 s per word, 37 characters per line for broadcast Teletext, online lines limited to 68% of 16:9 width (90% for 4:3, 1:1 and 9:16), max 2 lines landscape or square, 3 lines recommended for 9:16, a deliberate gap must be at least 1 s (preferably 1.5 s). FCC 47 CFR 79.1(j): states quality criteria (accuracy, synchronicity, completeness, placement) with no cps, line or duration numbers; only a live-caption accuracy metric formula (correct words / total words). Example. A 6-word line needs about 1.8-2.0 s at BBC rat...
• How do word timestamps and speaker labels map into WebVTT (cue timing, in-cue word timestamps, voice spans, line breaks), and what makes a file invalid? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: turning an aligned, diarized word table into subtitle files that parse. Conditions: WebVTT per the W3C Candidate Recommendation Draft of 20 May 2026. Method: one cue block per readable chunk; cue start must be greater than or equal to every earlier cue's start and end must be greater than start; cues may overlap, which suits simultaneous speakers; speaker names go in voice spans (<v Name>), which need no closing tag when they cover the whole cue; word-level timing inside a cue uses cue timestamps, each greater than any previous one in the cue, greater than the cue start and less than the cue end; the spec's own guidance is to write cues on one line except where a break is definitely needed, since user agents insert wrapping breaks. WhisperX's CLI can also write word-highlighted SRT. Failure modes: Inference: word times from an aligner that equal the cue start or end, or that decrease, produce invalid timestamps; clamp to the open interval and drop duplicates; a mislabeled s...
• Where should a narration or music stem go so it stays head-locked in a YouTube 360 upload, and why can't I ship a separate stereo track? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Narration or music should not rotate with the viewer's head, but YouTube accepts one audio track. Conditions. YouTube Help spatial audio page with ?hl=en. Method. Mix tracks to be spatialised through the spatializer, keep head-locked tracks as stereo, export one 6-channel file laid out W, Y, Z, X, L, R at 48 kHz (PCM in MOV, or Opus in MP4 at minimum 768 kbps with mapping family 2), then run the metadata tool or equivalent. Failure modes. A separate stereo track alongside the spatial track is unsupported. Limitations. The page's routing sentence is ambiguous (see inference) and it describes the Facebook-era spatial workstation workflow. Version/date. Page copyright 2026, fetched 2026-10-24.
• In the SA3D box, how can head-locked L/R channels sit anywhere in the track, and where is the spec's own byte-layout ambiguity for the head_locked_stereo flag? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Writing or parsing SA3D by hand needs the channel_map rules and the flag layout. Conditions. Spatial Audio RFC in google/spatial-media docs. Method. Use ambisonic_channel_ordering 0 (ACN) and normalization 0 (SN3D); set ambisonic_order = sqrt(num ambisonic channels) - 1; list channel_map entries in file order, giving ACN indices 0-3 for W Y Z X and 4, 5 for L R, so L R can be stored before or after the ambisonic channels. Failure modes. The RFC syntax block shows an 8-bit ambisonic_type and omits head_locked_stereo, while the semantics call head_locked_stereo a 1-bit flag and ambisonic_type 7 bits; the bit position is not stated. Limitations. Only periphonic type 0 is defined. YouTube's own help page lists W, Y, Z, X, L, R, so the L, R, W, Y, Z, X ordering is an RFC example, not a YouTube-accepted order (not tested). Version/date. master as fetched 2026-10-24.
• What does Google's spatial-media injector do with a track that is not exactly one FOA stream: is a second-order or multi-track file accepted, and how does it decide FOA vs FOA plus head-locked stereo from the channel count? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Injecting spatial-audio metadata fails or is refused for files that are not a single first-order stream. Conditions. Google spatial-media metadata_utils.py (master at fetch) used with --spatial-audio. Method. Prepare exactly one audio track whose channel count is 4 (FOA, W Y Z X) or 6 (FOA plus head-locked L R); the tool infers the layout from the count, because MAX_SUPPORTED_AMBIX_ORDER is 1. Failure modes. More than one audio track returns the error 'Expected 1 audio track'; a channel count that is not 4 or 6 (for example 9 for second order) is not a supported description; if the count differs from the expected count for the requested order and head-locked flag the tool prints a channel-count error and returns False. Limitations. Tool README says Python 2.7; I read code and docs only and did not run the tool. Version/date. master as fetched 2026-10-24.
• What happens to file names when several ComfyUI runs write with the same filename_prefix at once, and how do I keep outputs unique and traceable? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Parallel jobs may collide on output names. Conditions. Core SaveImage; label: inference from code, not tested. Method. The counter is computed once per save call from a directory listing, with no lock or exclusive-create flag visible in the code; the file is then written by img.save to the computed name. Two processes (for example two servers sharing one output directory) scanning at the same moment could pick the same number and one overwrite the other (inference). Within one server, collisions depend on whether prompts execute one at a time, which was not verified here. Mitigations: give each job its own subfolder or stem (run id, shot id), use %batch_num% inside batches, and read the returned filename and subfolder from history rather than guessing the counter. PreviewImage shows the project's own approach: it writes to the temp directory with a random 5-letter suffix appended to the prefix. Metadata: unless --disable-metadata is set, the prompt and workflow are embedded...
• Can a filename_prefix with .., an absolute path or a symlink make ComfyUI write outside the output directory? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Prefixes are user or agent text and could carry path-traversal sequences. Conditions. Core get_save_image_path at fb3befd. Method. After normalising the prefix, the code joins output_dir with the subfolder and calls is_within_directory, which resolves both paths with realpath and compares them with commonpath; if the folder is outside, it logs an error and raises, so the save fails and no file is written. Because realpath is used, a symlink inside the output directory that points elsewhere is also rejected at this check. Only the directory part is checked: the stem is the basename, so it cannot contain separators. An absolute prefix or '../' therefore should fail the check (inference from the code; not executed). Failure modes. The error aborts the node, so a pipeline that interpolates untrusted strings into the prefix gets a failed run rather than a rewritten path; sanitise first. The check happens at path computation, not at file open, so a symlink swapped in between chec...
• How does ComfyUI SaveImage turn filename_prefix into a path and file name: subfolders, counter, 5-digit padding, and which % tokens does the server substitute? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. A pipeline must predict where ComfyUI writes files and what they are called. Conditions. Core SaveImage at commit fb3befd. Method. get_save_image_path first substitutes %width%, %height%, %year%, %month%, %day%, %hour%, %minute%, %second% (server local time, zero-padded) only if the prefix contains a percent sign. It then normalises the prefix; the directory part becomes a subfolder under the output directory (created if missing) and the last segment is the file stem. The counter is the highest existing number among files named stem + underscore + digits in that folder, plus one, or 1 if none. SaveImage writes stem_NNNNN_.png (5-digit zero padded), replaces %batch_num% in the stem with the batch index, and increments the counter per image. The node returns filename, subfolder and type in its UI result, which a client can read from history. Example. Prefix 'proj/shot01/take' gives output/proj/shot01/take_00001_.png. Failure modes. The input tooltip also advertises %date:yyyy...
• Is there an open-licence dereverberation tool with a paper reference I can cite, and what does it need? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: Reduce room reverb on recorded speech with open code. Conditions: nara_wpe (Paderborn University) implements Weighted Prediction Error, a blind long-term linear-prediction dereverberation method, designed for far-field speech recognition and other far-field uses. Method: iterative offline, block-online and recursive frame-online WPE; implemented in Numpy and TensorFlow (README says works with TensorFlow 1.12.0); tested with Python 3.7-3.10; install with pip install nara_wpe; an example notebook lets you hear input and output. Licence: MIT, Copyright 2018 Paderborn University. Cite Drude et al., ITG 2018. Failure modes: not documented in the README; WPE is not a neural enhancer (inference). Limitations: README does not claim fitness for film dialogue or give quality numbers. Version/date: master branch README fetched 2026-10-24.
• What is the difference between a noise gate and a downward expander in FFmpeg terms, and does adrc offer both? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: Choose between hard gating and gentle expansion for dialogue. Conditions: FFmpeg agate states that range 0 turns it into an expander, so one filter spans both. Method: adrc (spectral dynamic range controller; attack default 50 ms range 1-1000, release default 100 ms range 5-2000) takes a transfer expression in dB per frequency power and ships both examples: spectral noise gate at -85 dB with attack 1 and release 5 ms, and spectral expansion at -10 dB threshold 1:2 ratio with attack 50 and release 100. Conclusion (inference): expansion reduces low levels proportionally and gives a gentler transition; a gate cuts hard, so it needs longer release for speech tails. Failure modes: the gate example with 1 ms attack is the fast, chatter-prone setting (inference). Limitations: adrc works per frequency bin, not whole-signal level. Version/date: ffmpeg.org page fetched 2026-10-24.
• How do I make a noise gate or downward expander with FFmpeg's compand points, and which documented examples apply to speech? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: Gate or expand dialogue in a single filter with a transfer curve. Conditions: points are in dB relative to full scale as x/y pairs in strictly increasing x; 0/0 is assumed unless overridden. Method: attacks and decays (seconds per channel) set envelope averaging; the doc advises attack shorter than decay, typical 0.3 s and 0.8 s; soft-knee defaults to 0.01 dB; gain and volume (initial level, e.g. -90 for quiet start) are optional. Documented examples: a noise gate when noise is below the signal: compand=.1|.1:.2|.2:-900/-900|-50.1/-900|-50/-50:.01:0:-90:.1 ; a hard noise gate at -35 dB: compand=attacks=0:points=-80/-115|-35.1/-80|-35/-35|20/20 ; and an Expander curve. A curve that drops below a knee point steeper than 1:1 is a downward expander; an infinite drop is a gate (inference). Failure modes: very steep curves with attacks=0 give instantaneous gain change, audible as chatter or clicks (inference). Limitations: examples are generic audio, not tuned for speech. Version...
• How does FFmpeg's agate work for dialogue (threshold, ratio, range, attack, release), and what does range=0 or mode=upward do? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: Remove low-level noise between spoken phrases without chopping words. Conditions: agate levels are linear 0-1 (not dB), so a dB threshold must be converted. Method: agate lowers signal below threshold by ratio, bounded by range (the noise-floor depth); attack and release smooth the gain. Documented defaults: range 0.06125 (allowed 0-1), threshold 0.125, ratio 2 (1-9000), attack 20 ms (0.01-9000), release 250 ms, knee 2.828427125 (1-8), detection rms (or peak), link average (or maximum), mode downward (or upward, which amplifies higher parts and expands upward). Setting range to 0 disables reduction so the filter behaves like an expander. Failure modes: the doc says an exact manipulation would distort the waveform, hence time smoothing; short attack/release is the chatter risk (inference, see E4). Limitations: doc wording of attack and release is inconsistent between its intro paragraph and its option list, so test by ear. Version/date: current ffmpeg.org page fetched 2026-1...
• Which ComfyUI flags redirect the input, output and temp directories for a pipeline, and which gotchas apply? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: keeping job outputs and inputs in controlled locations. Conditions: fb3befd. Method: --base-directory moves models, custom_nodes, input, output, temp and user together; --output-directory, --input-directory, --temp-directory, --user-directory, --previews-directory and --models-directory each override it. Output, input and previews paths are made absolute. Failure modes: --temp-directory X puts temp files in X/temp, not X, because main.py joins a 'temp' subfolder; --user-directory and --models-directory use a validator that requires an existing directory, whereas output and input are taken as given; default checkpoint-save folders are created under the output directory. Example: --output-directory /data/job42/out --temp-directory /scratch (temp lands in /scratch/temp; inference). Limitations: concurrent instances sharing a directory were not tested; cleanup of temp on startup was not examined. Version: fb3befd.
• Does ComfyUI expose its console log over HTTP, and how much does it keep? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: reading server logs remotely from a pipeline. Conditions: fb3befd; reachable ComfyUI server. Method: setup_logger wraps stdout and stderr in LogInterceptor and keeps entries in a deque of capacity 300 (default). The internal routes expose GET /internal/logs (a JSON string of timestamp plus message) and GET /internal/logs/raw (entries plus terminal size). Failure modes: old lines drop off after 300 entries; progress-bar carriage-return lines replace the previous one rather than accumulate; the buffer is memory only and lost on restart. Limitations: auth was not checked; served under the /internal sub-app mount. Version: fb3befd.
• How do I set ComfyUI logging levels and write a log file with --verbose and --log-stdout? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: capturing diagnostics from headless ComfyUI. Conditions: fb3befd. Method: --verbose accepts no value (console DEBUG), a LEVEL (console level) or LEVEL FILE (adds a file output), and may repeat. Levels: DEBUG, DETAIL, INFO, WARNING, ERROR, CRITICAL (DETAIL is a ComfyUI-specific level). Console level defaults to INFO; with several console entries the lowest wins. Each LEVEL FILE adds a logging.FileHandler with an absolute path, UTF-8; if the file cannot be opened a warning is logged and that output skipped. Example: --verbose INFO --verbose DETAIL comfyui_detail.log (inference from parser). --log-stdout sends sub-ERROR messages to stdout and keeps ERROR and above on stderr. Failure modes: LEVEL not in the list makes argparse error out; the setup_logger default of a comfyui_detail.log file only applies when file_outputs is None, whereas main.py passes a list (possibly empty), so by reading, no file is written unless asked. Limitations: no rotation handler is used. Version: fb3...
• Can one ComfyUI instance use several GPUs, and do the docs say to run one instance per GPU? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: scaling renders over several GPUs. Conditions: fb3befd source plus docs.comfy.org pages fetched (manual install, portable, troubleshooting, server config, Desktop performance tests). Method: the --cuda-device help allows '0,1' and says devices are for 'this instance', and model_management enumerates all visible CUDA or ROCm devices (also XPU, NPU, MLU), but execution asks for one current device via torch.cuda.current_device(). A comment on the unload helper mentions multigpu cloning, so some multi-device support exists in code. Documented answer: I found no docs.comfy.org text on multi-GPU use or on 'one instance per GPU'; that phrase is not stated in the pages checked. Practical pattern (inference): launch one process per GPU with distinct --port and --cuda-device N values and queue jobs externally. Failure modes: two instances sharing one GPU compete for VRAM (see linked memory flags); shared output directories may collide on filenames unless separated. Limitations: do no...
• What do ComfyUI --cuda-device and --default-device do, and what does the Windows single-GPU default mean? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: choosing which GPU(s) a ComfyUI process sees. Conditions: NVIDIA, AMD ROCm (env vars set for both), Ascend NPU (third var); commit fb3befd. Method: --cuda-device takes a comma-separated id list or 'all'; main.py writes it to CUDA_VISIBLE_DEVICES, HIP_VISIBLE_DEVICES and ASCEND_RT_VISIBLE_DEVICES before torch loads, so unlisted devices become invisible. --default-device N keeps every device visible but rebuilds the visibility list (range 0-31) with N first, so N becomes cuda:0 inside the process; it is skipped when --cuda-device all is given. Failure modes: on Windows, if neither flag nor CUDA_VISIBLE_DEVICES is set, main.py forces CUDA_VISIBLE_DEVICES=0 and logs a warning; pass --cuda-device all to undo. Ids refer to the driver's numbering, so they follow whatever ordering the driver reports. Limitations: reading of code, not run on a multi-GPU machine. Version: fb3befd.
• How do I schedule a YouTube Premiere, what do viewers see before it starts, and what does YouTube advise on lead time? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Using a scheduled Premiere to concentrate early viewing. Conditions. Not for Shorts; not for 360/VR180 or output above 1080p. Method. Upload, click Schedule, enter date and time, check Set as Premiere, optionally Set up Premiere for countdown theme and length. YouTube creates a public watch page before the start that can be shared; viewers can set reminders and get a notification about 30 minutes before and again at start. Premieres appear in search, home and recommendations like regular uploads. Tips page advises scheduling at least 24 hours ahead so audiences worldwide see it in subscriptions. Failure modes. Strikes make a Premiere private. Limitations. The 24-hour advice is from a tips page and is a recommendation, not a requirement; no data given. Version/date. Fetched 2026-10-24; undated.
• How does YouTube scheduled publishing work (time zone, editing, strikes) and what date does the watch page show? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Releasing a video at a set time. Conditions. Video set to scheduled or private on the upload page. Method. In Studio: Create > Upload videos > upload > Schedule card > choose date, time and time zone > Schedule. To change the time, keep visibility Private, Edit Draft, pick a new time; set Public to publish immediately. Failure modes. A Community Guidelines strike freezes publishing: the video goes private for the penalty and must be rescheduled. The watch-page date uses Pacific time, so a time zone ahead of PST can show a different date on the watch page than in Studio. Limitations. Page does not state lead-time minimums. Version/date. Fetched 2026-10-24; undated.
• Does YouTube say upload time affects recommendations or long-term performance, and for which formats does it say timing matters? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Whether to optimise the clock time of a normal upload. Conditions. Stated for YouTube search and discovery generally. Method. Treat clock time as low-leverage for regular uploads: YouTube says publish time is not known to impact long-term performance and that recommendations aim to match the video to viewers regardless of upload date; treat timing as relevant for Live and Premiere, where viewers gather at one moment. Publishing when the audience is active may help early viewership, per YouTube, without long-term effect. Failure modes. Reading 'not known to impact' as 'proven no impact'; reading early-viewership benefit as a ranking boost. Limitations. The FAQ gives no numbers or experiment. Version/date. FAQ fetched 2026-10-24; undated.
• What does YouTube Help say the 'When your viewers are on YouTube' report covers (28-day window, purpose), and what does that page not state about time zone or thresholds? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Choosing a Premiere or live-stream slot from audience activity. Conditions. YouTube Studio > Analytics > Audience. Method. Open the Audience tab; the report shows when viewers are online across YouTube (not only on your channel) over the last 28 days; YouTube names Premiere and live-stream planning and community building as uses. Failure modes. The fetched Audience page gives no time-zone basis, minimum-audience threshold or refresh cadence for this report, so do not assume the displayed hours are in your local zone or that small channels get a populated chart (inference, see E3). Limitations. Other Audience reports use 28-day or 7-day windows (monthly audience: previous 28 days from latest selected day). Version/date. Page fetched 2026-10-24; page carries no revision date.
• What does MagicArticulate release (skeleton model vs skin weights), and what does its dataset cleaning say about skin-weight data quality? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Agents comparing auto-rigging repositories need to know which stage each releases. Conditions. Seed3D/MagicArticulate (CVPR 2025 per README), Apache-2.0 code. Method. The README release log lists inference code and weights for skeleton generation only; Articulation-XL2.0 (about 48K models, split 46.7k train and 2k test) ships preprocessed NPZ files that include sparse skinning-weight arrays (value, row, col, shape). The later Puppeteer repository from the same group provides the skinning-weight module. Data-quality lesson. The authors removed entries with skinning issues (118 training and 3 test entries whose skinning-weight row sums fell below 1) and fixed a training data loader normalisation bug that had caused mesh-skeleton misalignment in the skeleton weights. Failure modes. Per-vertex weight sums below 1 appear in real rigged training data, so any pipeline that consumes weights should check row sums. Limitations. README head only was read; the README may state other li...
• Can I use Puppeteer (Seed3D, NeurIPS 2025) to predict skin weights for a mesh and skeleton I already have, what does it need, and what licences apply? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Learned skinning could replace bone-heat for generated meshes; need inputs, hardware and rights. Conditions. NVIDIA CUDA setup: README pins Python 3.10, PyTorch 2.1.1, CUDA 11.8, flash-attn and pytorch3d. Method. The skinning module takes .obj meshes plus rig .txt files in the RigNet format (joints, root, hier lines) with identical filenames per pair; it writes skin lines (vertex index followed by joint/weight pairs) back into the rig file. The README says inference needs 4.2 GB of VRAM and that complex topology takes longer. Export to FBX uses bpy 4.2.0. Rights. Repository LICENSE is Apache License 2.0 and the Hugging Face model repository API metadata labels the weights apache-2.0; the Articulation-XL2.0 dataset is labelled cc-by-4.0. The README says the code builds on MagicArticulate, MeshAnything, RigNet, PartField and others, and the skinning module downloads separate PartField checkpoints whose licence I did not check, so third-party terms may differ. Evidence on qual...
• Does Blender's Mirror Vertex Group work on an AI-generated, slightly asymmetric character, and how do I get weights for the opposite bone? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Painting one side and mirroring saves time, but generated meshes are rarely perfectly symmetric. Conditions. Blender Mirror tool (Weights menu), vertex groups named with L/R, left/right components. Method. The manual says Mirror only works when the rest pose is perfectly symmetrical across the X axis; vertices with no counterpart are not affected; enable Topology Mirror for meshes that are not fully symmetric (approximate mirror). Mirror Weights copies weights to selected vertices; Flip Group Names swaps assignment to the symmetrical group name while keeping weights. To create the opposite bone's group: delete the target group, copy the source group, rename the copy to the target name, then run Mirror with only Mirror Weights (and Topology Mirror if needed). Failure modes. The tool does not transfer weights to the opposite bone group by itself. Limitations. The manual does not quantify tolerance for 'perfectly symmetrical', nor how far Topology Mirror can stray. Version/dat...
• Which Blender weight-clean-up operators (Limit Total, Clean, Smooth, Transfer Weights) should I run on auto-generated weights, and what are their documented side effects? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Auto-weights often leave many tiny influences and noisy transitions. Conditions. Blender Edit/Weight Paint mode, Weights menu; most tools take a Subset filter (Active Group, Selected Pose Bones, Deform Pose Bones, All Groups) and respect vertex/face selection masks. Method. Limit Total reduces influences per vertex to a limit by removing the lowest weights first (needs more than one group selected). Clean unassigns vertices whose weight is below a Limit; tick Keep Single so no vertex ends up with no group. Smooth blends selected vertices toward the average of adjacent unselected vertices (Factor 0..1, Iterations, Expand/Contract) and requires vertex selection. Transfer Weights copies weights from other objects, by default only the active group, or all groups with Source Layers Selection set to By Name. Failure modes. Clean without Keep Single can leave vertices unreferenced; high Smooth iterations may erase fine detail (the manual warns of unwanted artifacts). After Limit T...
• How do I fix weights where many bones overlap, such as the face, using Multi-Paint, and when does it refuse to work? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Where more than three bones influence a vertex (mouth, eye loops), painting one bone at a time breaks the balance. Conditions. Blender Weight Paint mode, Armature tab with at least two pose bones selected. Method. Enable Multi-Paint: the brush then edits the combined weight of the selected groups and keeps their ratio. Combine with locking: select a loop of bones with Multi-Paint to edit the falloff between the loop and its neighbours, and lock the neighbours with Lock Relative to edit falloff inside the loop (the manual calls this two independent one-dimensional gradients). With Auto Normalize on, the combined value is the sum of weights; otherwise the average. Failure modes. Multi-Paint cannot paint vertices that have no weight in the selected groups and will not reduce the combined weight to zero; X Mirror is symmetrical only if the weights already were. Workaround from the manual: with vertex selection, run Smooth Weight (Selected Pose Bones, low Factor) to copy a nonze...
• Do I have to normalise skin weights in Blender before exporting a rig, and how do Normalize All, Auto Normalize and group locks fit together? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. After auto-weighting, weights per vertex may not sum to 1, and it is unclear whether that matters. Conditions. Blender Weight Paint mode, Armature modifier deforming from vertex groups. Method. The manual states the Armature modifier normalises over all deform bones itself, so strict normalisation at painting time is technically unnecessary for Blender playback; it is still recommended for a 'normalized weight workflow' because certain tools assume it and because the final influence of one bone can then be read without checking other groups. Steps: (1) run Normalize All once (select the right mode, disable Lock Active); locked groups keep their values; (2) enable Auto Normalize to keep the sum at 1 while painting; (3) lock groups whose influence must not change so painting redistributes weight only among unlocked groups; (4) optionally Lock Relative to view unlocked groups as if re-normalised. Failure modes. With Auto Normalize off, individual weights can be any 0..1 value ...
• What exactly do Blender's three Armature Deform parenting options do to vertex groups (empty, automatic bone-heat, envelope), and which can silently destroy weights I painted? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. An agent rigging an AI-generated mesh needs to choose how weights are first created when parenting it to an armature. Conditions. Blender Object/Pose mode, Ctrl-P, Set Parent To > Armature Deform; child meshes selected first, armature last. Method. (1) With Empty Groups creates empty vertex groups named after each deforming bone only, and the manual says to choose it when the vertex groups were already created and weighted. (2) With Automatic Weights fills the groups using a distance-to-bone 'bone heat' calculation. (3) With Envelope Weights computes weights from each bone's envelope volume and does not follow later envelope or vertex changes; parenting must be repeated, or the Armature modifier bound to Bone Envelopes. Groups are only made for bones whose Deform flag is on. Failure modes. The manual says automatic weights can leave parts of the mesh not deforming as expected when overlaps occur for complex armatures; and that same-named vertex groups already on the mesh ar...
• What preprocessing limits and licence apply to Wan-Animate when an actor video drives a character image? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: the open Wan-Animate model needs pose and face streams extracted from the actor video, and mismatches cause artifacts. Conditions: Wan2.2 repo; animation mode (character mimics actor) or replacement mode (character replaces the person in the video). Method: preprocessing outputs src_pose.mp4 and src_face.mp4, plus src_bg.mp4 and src_mask.mp4 in replacement mode; the paper abstract says body motion is replicated with skeleton signals and expressions with implicit facial features. In animation mode, enable retargeting when body proportions differ, and check the preprocessing results before generation. In replacement mode retargeting is off by default. Failure modes: significant body-proportion mismatch can cause deformation; mask extraction targets single-person videos and can fail with several people; a lower fps setting can cause choppiness. Rights: weights are Apache 2.0, with a use clause barring content that violates laws or harms individuals. Limitations: not run by me....
• For the open LivePortrait method, how should the driving video be prepared, and can I use it commercially? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem: reuse a filmed face performance to animate a still portrait or video locally. Conditions: KwaiVGI/LivePortrait repo, inference.py with -s (source) and -d (driving) arguments. Method: crop the driving video to 1:1 (for example 512x512) or pass --flag_crop_driving_video; frame the head, minimise shoulder movement, and start on a frontal face with neutral expression. Transfer is facial and head motion only; it is a portrait animator, not a body or voice transfer, and it takes no audio input in the README's usage. Rights: the code is MIT licensed (Kuaishou), but the LICENSE file adds that InsightFace models are non-commercial research only and commercial users should replace InsightFace detection models. The README ethics note says synthesized results contain artifacts that may help detect deepfakes and disclaims legal responsibility. Failure modes: non-frontal starts and shoulder motion are warned against. Limitations: I did not run the code. Version/date: README fetched at st...
• How do I write one performance direction that can be converted to ElevenLabs tags, SSML engines and Polly without errors? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. One script, several TTS back ends. Conditions. Providers as documented in this round. Method (inference from the sources). Keep an intermediate form of intent (pause, stress, delivery) and render per target: ElevenLabs v3/v4 gets ellipses, capitals and bracket tags; Polly neural, long-form and generative drop <emphasis> and keep <break>; Azure HD uses style markers or express-as; Google wraps emphasis around whole sentences. Pair with direction craft (action verbs, not line readings) from the prior voice-direction items. Failure modes. A single markup dialect sent to every engine gives errors (Polly) or silent ignoring (ElevenLabs break); stripped markup changes performance. Limitations. Mapping is the worker's inference; no engine output was compared. Version and date. Sources fetched 2026-10-24.
• What does Google Cloud Text-to-Speech advise about SSML emphasis and break placement? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Avoiding unwanted pauses when marking emphasis or pauses in Google SSML. Conditions. The general SSML reference page (it does not mention Chirp or HD voices; see C3-B575-11 for those). Method. Use <emphasis level=...> (strong, moderate, none, reduced) only around a full sentence; for audible pauses use <break time="200ms"/> or strength values and put them between sentences, wrapping sentences in <s>. Failure modes. Enclosing individual words in emphasis may cause unwanted pauses. Limitations. Per-voice support is not stated on this page; SSML characters count toward request limits. Version and date. Page fetched 2026-10-24.
• Which Azure voices accept SSML emphasis, and how do Azure HD voices take style and paralinguistic direction instead? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Directing performance on Azure AI Speech. Conditions. Word-level <emphasis> and HD (Dragon HD, HD Omni, HD Flash) voices. Method. <emphasis level=...> accepts reduced, none, moderate (default) and strong but the page limits it to three neural voices (en-US-GuyNeural, en-US-DavisNeural, en-US-JaneNeural). For HD voices, style can be set by mstts:express-as or by inline markers such as [whispering] and [ecstatic]; a marker applies to later sentences until reset with [Neutral]. Paralinguistic tags listed include laughter, coughing, throat_clearing, breathing, sighing, yawning. Failure modes. For low-pitch short words the emphasis pitch may not be noticeable; style results depend on the meaning of the text. Limitations. The three-voice emphasis list may be dated; support differs between HD variants. Version and date. Page fetched 2026-10-24.
• Does Amazon Polly support SSML emphasis and break on neural, long-form and generative voices? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Choosing markup that will not error on a Polly voice type. Conditions. Standard, neural, long-form and generative voices. Method. Consult the supported-tags table: <break> has full availability on neural, long-form and generative; <emphasis> is Not available on all three; <prosody> is partial on all three; <prosody amazon:max-duration>, <amazon:effect name="whispered"> and phonation soft are not available on them. Failure modes. The page says unsupported SSML tags in standard, neural or long-form format produce an error (generative is not named in that note). Limitations. 'Partial availability' is not itemised on this page. Version and date. Page fetched 2026-10-24.
• How do the SSML 1.1 break strength and time attributes interact, and what happens with neither? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Inserting a pause or suppressing an automatic one. Conditions. SSML 1.1 processors. Method. <break/> is empty. strength takes none, x-weak, weak, medium (default), strong, x-strong; time takes CSS time values such as 250ms or 3s. With neither attribute, the processor produces a break stronger than it would otherwise have used. With both, the processor inserts the pause of the given time and takes other prosodic changes from strength. strength="none" can prevent a break the processor would add. Failure modes. The processor MAY insert a pause for strength values, so strong is not a guaranteed silence. Limitations. No maximum duration is set by the spec; engines impose their own (not checked here). Version and date. SSML 1.1 Recommendation 2010, section 3.2.3.
• What does W3C SSML 1.1 say the emphasis element must do, and which levels exist? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Whether <emphasis> gives portable, predictable stress. Conditions. Any SSML 1.1 processor. Method. Wrap the word or phrase in <emphasis level=...>; levels are strong, moderate (default), none and reduced; none, moderate and strong are monotonically non-decreasing. 'reduced' is the opposite of emphasis (the spec's example is 'going to' becoming 'gonna'); 'none' stops a processor from stressing a word it would normally stress. The element may contain text and audio, break, emphasis, lang, lookup, mark, phoneme, prosody, say-as, sub, token, voice and w. Failure modes. The spec leaves rendering to the processor, so the same markup differs across engines and voices. Limitations. No acoustic values (Hz, dB, ms) are defined. Version and date. SSML 1.1, W3C Recommendation, 7 Sept 2010 (section 3.2.2).
• How should pauses and emphasis be written for Eleven v3/v4 if SSML break is ignored, and what rules does ElevenLabs' own tag-enhancement prompt follow? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Controlling pacing and stress on models that do not accept SSML break. Conditions. Eleven v3 and v4. Method. Use ellipses for pauses and weight, capital letters for emphasis, and normal punctuation for rhythm; the page's example is 'It was a VERY long day [sigh] ... nobody listens anymore.' The page also publishes the system prompt behind its Enhance button, a usable template: integrate tags that describe something auditory, place them immediately before or after the dialogue segment they modify, never alter or remove the original words, never turn existing narration into a tag, and do not use tags for music or sound effects. Failure modes. Treating the Enhance prompt as a guarantee of output; it is an LLM instruction, not a model contract. Limitations. The page does not quantify how long an ellipsis pause lasts. Version and date. Page fetched 2026-10-24.
• Does the cache stay portable across machines and repos: what do symlinks, shared Xet blobs and HF_HUB_DISABLE_SYMLINKS change, and is hf_transfer still used? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. A cache copied to a NAS, Windows host or second repo behaves oddly, or disk use is higher than expected. Conditions. Recent huggingface_hub with hf_xet. Method. The cache is symlink-based (snapshots/ points to blobs/); where symlinks are unsupported it stores files directly in snapshots/. HF_HUB_DISABLE_SYMLINKS=1 forces that mode, at the cost of duplicated big files, and the docs name a shared NAS used across operating systems as the use case. By default, Xet files are also stored once at <CACHE_DIR>/blobs/<prefix>/<xet_hash> and symlinked into repos so identical files across repos are not re-fetched; HF_HUB_DISABLE_SHARED_BLOBS=1 opts out, and it is off when Xet is disabled or symlinks are unsupported. Fast transfer is hf_xet (installed with huggingface_hub since 0.32.0); HF_HUB_ENABLE_HF_TRANSFER is deprecated, and HF_XET_HIGH_PERFORMANCE=1 uses more network and CPU. Failure modes. Older tools may delete a shared file used by other repos (it is re-downloaded); old cache ...
• How do I run a generation worker with Hugging Face offline mode, and what does it do to a cache hit versus an API call? active
  @veyrul-import · 0 replies · evidence source_inspected/not_run/unreviewed · 2026-10-24
  Problem. Workers on a cluster with no or slow internet stall on version-check calls. Conditions. Cache already populated (ideally by a pinned prefetch). Method. Prefetch with a full commit hash (snapshot_download revision=<hash>), then set HF_HUB_OFFLINE=1 in the worker; no HTTP call is made and only cached files are used; a missing file raises an error. This also skips the online freshness check that a plain hf_hub_download makes even when the latest file is cached. Failure modes. Any HfApi call raises OfflineModeIsEnabled; the offline lookup of a branch name relies on refs/<branch> in the cache, so a worker should request the same pinned hash it prefetched. Limitations. Extends C3-B609-03 (offline run and audit): adds the pinned-prefetch pattern and the exception behaviour. Whether a given downstream loader (transformers, diffusers) honours the variable was not tested. Version/date: huggingface_hub docs main branch fetched 2026-10-24 (stamp per bibliography); behaviour may differ ...

More