Spaces:
Running on Zero
Running on Zero
Commit History
2 days ago
-
fix: below 1024 px a control reached by Tab stops above the commit bar instead of under it: the page holds back the bar's height when it scrolls (round 4's N5, WCAG 2.4.11) (#20)
Unverified signatureBelow 1024 px the commit bar (the "Needs a prompt" line and Generate) is fixed to the window's bottom, 97 px tall. A browser scrolls a control reached by Tab only as far as the window's bottom edge, so it came to rest under the bar. The round-4 rig caught it at 390 on 1d8deb6: Tab from Advanced to the monitor's Play scrolled the page to 1104, and Play (y 800-844) lay entirely under the bar (y 747-844). That fails WCAG 2.2 SC 2.4.11, Focus Not Obscured (AA). On 25e35b7 the same Tab had left Play clear of the bar, at y 518-562; nothing held back the bar's height when the page scrolled, then or now. One rule in the below-1024 px block: html { scroll-padding-bottom } takes the same room the page already keeps below its content for the bar (var(--mr-bar-h) + the safe area + 16 px). A browser honours a scroll container's padding when it scrolls a focused control into view, so the control stops above the bar (WCAG technique C43). Desktop is untouched: its Generate sticks inside the rail. te…ea5b282 -
docs: every sentence stays true after the deploy: README and the release notes say this is deploy 2's code and point to issue #32 for what the Space shows, and no doc says the Space still runs deploy 1, is not deployed, or has not been redeployed since August (#32)
Unverified signatureThe commit we deploy is also what origin/main is fast-forwarded to, and nothing can be pushed after the deploy without restarting the public Space, so a sentence that a deploy makes false would stay false. README: "Where things stand, 2026-11-17" says the README describes deploy 2's code, which replaces deploy 1 on the Space, points to SPACE_MODE_MATRIX 10.1-10.3 and the release notes, and to issue #32 for deploy 2's own check on the Space. The cold-start time points to #32 instead of "has not been measured"; the longest accepted reservation is "not measured by these runs"; the browser runs of 2026-11-16 "did not finish in that session" instead of "have not been run ... yet". docs/RELEASE_NOTES.md: "Deploy 2 - 2026-11-17", the code of this commit's tree, the Space result on #32 (also under "On the Space"); deploy 1 "ran" as 0cd54f2 until deploy 2, and main "was fast-forwarded" to 1e9fd20 that day. The other docs, the same way: SPACE_MODE_MATRIX's header and 10 intro, 10.2 and 10.3; …abc9150 -
docs: the release notes' Deploy 2 section names its commits as integrated: UI-B's round-4 package (78036d2 ... 7cef5fb) by issue and these docs by issue, and drops the list of what was still to land (#32)
Unverified signatureb5a4494 -
docs: UI_DESIGN quotes mode 11's sentence as the page shows it and as the brief gives it, "With a speech recording and no first-frame picture, some seeds come out as a black-and-white period film ...", instead of paraphrasing it (#28)
Unverified signature1cda206 -
docs: the release notes open a "Deploy 2 - 2026-11-17 (in preparation)" section: what changed since deploy 1, issue by issue with its commits (all 35 on fix/studio-2026-11), what lands next, what is not in it, and an "On the Space" heading for the result after the deploy (#32)
Unverified signature85c4433 -
docs: the README describes the page after the round-4 review where a reader needs it (the line beside Generate names what returns, the monitor keeps a run and offers another mode's sample and the way back, the player answers keyboard and touch, the Done card's length words, the sound download, an adapter's next step, Restore's note), and UI_DESIGN adds the players' access (#20)
Unverified signature4d60faf -
docs: the diffusion decoder is built once at start-up, beside the pipeline, and packed with it on the Space, with each run building its own only if that build failed: the README's decoder paragraph and two PLAN passages say so (#17)
Unverified signatured8bbbdb -
docs: the handoff's and ZEROGPU_DISK's status boxes no longer say the Space has run nothing since August: it runs deploy 1, whose Space record is SPACE_MODE_MATRIX §10.1, and the handoff points at the release notes (#29)
Unverified signature70ddbf2 -
docs: the weights come from the image: the README, PLAN and the handoff say preload_from_hub fetches the 35 model files (71.92 GB, no temporal upsampler) and the prompt enhancer's 8 (2.49 GB) before the app starts, and start-up downloads only what is missing, if the disk can hold it (#23)
Unverified signature41dcf05, ff62c55 and 72b989d made the preload live: the README's front matter (B3's) fetches the 35 files the int8 Space loads at their pinned commits and the enhancer's 8 at its own, and preflight.ensure_weights checks the cache at start-up, downloads only the missing files after one warning, and refuses a download the disk cannot hold (missing bytes + ZeroGPU's packed copy + a 10 GB margin, under the 150 GB cap) before writing a byte. The docs still said the Space downloads 72 GB at every start because the preload 401s on a private Space. README: the enhancer paragraph says the image brings its weights on the Space and the start-up prefetch (CUDA only, app.py) is the fallback; the ZeroGPU table gets a Weights row. No cold-start time is claimed: none is measured with the preload. docs/PLAN.md: 2.3 notes the 35-file set, the deploy-shape table's Space and Weights rows are corrected in place (public; from the image), 6.2 and 6.2.1 open with a 2026-11-17 correction, and the enhancer-pre…38e36e9 -
docs: the reservation follows size and length: the README's table is the estimator's (the default run 60 s, needing 120 s of quota), the measured envelope is a stated limit, and SPACE_MODE_MATRIX §10.3 records the six size-and-length runs and the answer to the operator's question (#21)
Unverified signatureac68de5 made zerogpu.estimate_duration a fit of the Space's measured runs with a 1.3 margin per term; the docs still said a flat 180 s, x1.5 with Upscale, +60 with an adapter and +180 with Enhance. README: the reservation section says how a run is priced now and gives the estimator's own figures (computed from the code: the default 704x480, 5 s run reserves 60 s and needs 120 s free; +45 s with Upscale at that size, +40 s with adapters, +80 s with Enhance; 1280x704 at 10 s 145 s; 960x544 at 10 s with Upscale 240 s; a sound-only mode 45 s), that LTX25_GPU_DURATION_SECONDS is ignored and LTX25_GPU_DURATION_FLOOR_SECONDS sets a minimum; deploy 1's GPU windows stay as the history they are. The limits section states the envelope the Space refuses past (64,000 tokens per pass, 520 million returned pixel-frames) in the refusal's own words (tests/test_reservation.py). Enhance's "reserves 180 s more" is 80 s, Upscale's x1.5 is 45 s at the default size, and the Upscale paragraph gives what the …ca1f2a8 -
docs: wording in deploy 1's record: the README's adapter-on-the-Space sentence says Validate once, the matrix's 10.1 intro reads as one paragraph, and the release notes' browser runs open with a sentence (#25)
Unverified signaturec8c5965 -
docs: the decoder choices are named by what a user sees: Auto, "Steadier (diffusion decoder)" and "Sharper (standard decoder)" in the README and UI_DESIGN, with what the Space's A/B showed and what the diffusion decode costs (#27)
Unverified signatureOn the Space (deploy 1, the same seed, prompt and size through both decoders; SPACE_MODE_MATRIX 10.1, rows 1 and 7): the same scene (SSIM 0.876); the diffusion decoder a little softer and steadier from frame to frame, the standard decoder sharper frame by frame with more shimmer (fine detail 10.30 vs 11.65, Laplacian variance 421.6 vs 591.6, shimmer 1.471 vs 1.883). So "Best quality" / "Fast" said the opposite of what a user sees; the UI package renames them, Auto stays the vendor's default, and these docs use the new names. The decode step on the Space, from the last sampling progress to "writing the file" in the two calls' events, took 4.4 s with the diffusion decoder and 1.9 s with the standard one, so the README says about 2.5 s more per run (rounded to the second it is the 3 s the issue cites). The labels at this head are still the old ones in ltx25_studio/ui/render.py; these docs follow the UI package's change.360edcc -
docs: the small truths: the Space is public and runs deploy 1, the README says what the page shows about cost on a Mac in place of the comment that asked for it, the browser session on the fixed build is written, and a speaking face gets the page's own words (#29)
Unverified signatureREADME body: - "Deploys to a private Hugging Face Space" now says public: the repo and the Space were made public on 2026-11-16 (the YAML front matter's preload comment, which also explains the 401 in terms of a private Space, belongs to the package editing the front matter and is untouched); - "Where things stand" no longer says the Space runs the August build: it runs deploy 1, on which all eleven modes ran and were looked at, and it points at the matrix (10.1 the Space, 10.2 the Mac) and the release notes; - the HTML comment addressed to the lead is gone; in its place the sentence it asked for: on a Mac the cost panel reads "Runs on this Mac's GPU; nothing is metered" and nothing on the page speaks of quota, reserving, billing or paying (render.py; pinned by test_ui_device_words.py). This is also the README sentence #19 asks for; - the browser runs: the second session, on a build with the memory check fixed, finished text to video with sound through the page with the…da5f47d -
docs: deploy 1's Space run is in the repo: SPACE_MODE_MATRIX §10.1 call by call, PR #1's corrected texts as the release notes' Deploy 1 section, and the README's Space sentences carry what the Space measured (#25)
Unverified signature§10.1 was a placeholder waiting for the post-deploy Space run. It now records deploy 1's 24 calls (2026-11-16, 16:02-16:27 UTC, Space commit 0cd54f2, the tree of 1e9fd20): per call what was sent, what came back, what was seen and measured, and the GPU-s bound (the window x 2), each row named by its label under the run's evidence/space/matrix/, where every figure in the row can be found (checked by script: 245 figures, none missing). With it: the build and the start-up report, how the outputs were judged (and why the client's MISMATCH on the 13 video-with-sound calls was the client's), what the calls settle, the decoder and adapter A/B pairs, mode 11's colour by seed, and the findings the calls left open. The document's header, the never-written-up block and the section 8 follow-ups that waited on the Space (7, 8, 9, 12, 13) now say what deploy 1 showed. PR #1 is merged and stays as it is on GitHub. docs/RELEASE_NOTES.md holds its corrected body and comment as the "Deploy 1 - 2026-11-1…0646770 -
docs: UI_DESIGN gives the figure line and the Upscale line as the reservation now sizes them: the default run's figure reads "704 × 480, 5.0 s, needs 120 s quota", and the Upscale line names its seconds at the default size and length and points to the cost panel (#21)
Unverified signatureThe reservation follows each run's size and length since #21, so a default run needs 120 s of quota to start (a 60 s reservation, times 2), not 360, and the Upscale line reads "Reserves 45 s more at the default size and length; when it is on, the cost panel shows what it adds." The figure-line paragraph, which this branch extended for M1, still quoted the old 360 s, and the cost-words paragraph said only that the Upscale line names its seconds. Both now say what the page says (the figure as handlers.review and render.figure_line give it for the default Text to video with sound on the Space build).7cef5fb -
fix: mode 11's first-frame line names the cause the round-4 verdict found: with a speech recording and no first-frame picture, some seeds come out as a black-and-white period film; add "in colour" to the prompt, or give a first-frame picture (#28)
Unverified signatureThe round-4 verdict found that the black-and-white result depends on the seed (the same recording and prompt gave a period film at seed 7 and colour at seed 21), not on how old the recording sounds, so "An old-sounding recording can come out as a period film" sent the user looking at the wrong cause. The sentence is now exactly: "With a speech recording and no first-frame picture, some seeds come out as a black-and-white period film: add “in colour” to the prompt, or give a first-frame picture." It stays where it was: in Audio to video's first-frame caption only, under the picture and above the prompt, the two remedies it names. UI_DESIGN's paragraph on mode 11's help says the same. Test (tests/test_ui_copy.py, re-pinned through the built page's own switch): in Audio to video exactly one shown component holds the new sentence, between the picture and the prompt, and the caption is "Optional. Used as the first frame. " followed by it, with no "old-sounding"; in every other mode no com…9887158 -
docs: UI_DESIGN's failure-card paragraph, which this branch extended, is rewrapped at the file's width (#20)
Unverified signature67478d3 -
docs: UI_DESIGN's lines this branch added wrap at the file's width (#20)
Unverified signaturee48ebc3 -
fix: Restore settings says what it did, the seed included: a quiet line in Recent runs reads "Settings from 08:06 restored; the seed is random again, as it was for that run. Your current audio stays as it is." until the next run (#20)
Unverified signatureRound 4, minor 10. Restore writes the run's own settings back, its seed setting among them (usually -1, a new seed each run), and keeps the current media. On a desktop nothing moved and nothing said so (S11 and S12 are the same frame), and "Reuse seed" then "Restore settings" on one row silently went back to a random seed. Restore keeps writing the run's seed setting (it is one of that run's settings; Reuse seed is the seed's own button) and now says so, with the media it keeps, in a line under the Recent runs heading (elem_id recent-note, the page's quiet hint style); the next run's start takes it away. Tests (tests/test_ui_restore_says.py, through the built page's own steps): Reuse seed then Restore writes -1 back and says the seed is random again, naming no media in a mode with none; a run at seed 42 in Audio to video is restored with "with that run's seed, 42" and "Your current audio and image stay as they are."; the next run hides the line; the words.6150e0e -
docs: UI_DESIGN says a LoRA rejection gives one next step for its kind and "Nothing was spent." only on ZeroGPU, and gives the idle monitor's line on each platform; it reflows the strength sentence minor 1 added (#20)
Unverified signaturee6f95d8 -
fix: a failure card no longer outlives Show, a Restore or its own remedy within one mode: each turns it into its one line, "Last run: <mode>, <time>. <headline>." (#20)
Unverified signatureRound 4, minor 2 (R4's residue). R4 collapsed a failure card when the mode changed. Within one mode it stayed red and open: in the round-4 captures Enhance was already unticked and "The prompt enhancer is unavailable. Turn Enhance off to run with your own prompt." stood under Generate, through Show, Restore, LoRA staging and Upscale. Now the same line R4 writes replaces the card when Show puts another run on the monitor, when Restore writes a run's settings (in its own mode too), and when a control the card's step names changes: Enhance for the enhancer card; Upscale, Enhance or LoRA for the quota card; Enhance or Upscale for the per-run limit; size, length or Upscale for a timeout or memory card; LoRA for an adapter card; any field for a refused input (its detail names the field); the media for "Your inputs could not be read". A card whose step names no control (press Generate again) stays until the next run. render.step_names holds which fields each card's step names; each field's c…7896071 -
fix: a cost lamp's state is not in colour alone: an unlit lamp is hidden from assistive tech and the lamps' row is a named group, so what is read is the costs that apply (#20)
Unverified signatureRound 4, minor 12, the panel's part (the visual lens's N2). The lamps marked lit and unlit with a class only, and named their row with aria-label on a plain div, which ARIA does not allow and screen readers skip; a screen-reader user heard every lamp as if it applied, and off ZeroGPU a lit and an unlit lamp carry the same words ("Upscale", "LoRA"). WCAG 1.3.1. An unlit lamp now carries aria-hidden="true" and the row role="group" with its name, as the lens proposed. The picture is unchanged. Test (tests/test_ui_lamps_read.py, panels from handlers.review): at the defaults every lamp is unlit and hidden; with Enhance on, the Enhance lamp is lit and read and every unlit lamp is hidden; the row is a named group. tests/test_ui_parked_upscale.py's lamp reader now reads a lamp whatever its attributes.44edefb -
fix: the run summary's time for a run under half a second reads "under 1 s" (on ZeroGPU "under 1 s of GPU time, under 2 s of your quota"), never "Took 0 s" (#20)
Unverified signatureA sub-second run, as on the tiny checkpoint, read "Took 0 s on the CPU" in the Done card, and "It used 0 s" in the card for a result that could not be shown: a run that took no time at all, which is not what happened. took_words rounds as before, and a run that rounds to 0 s says "under 1 s"; on ZeroGPU the quota it drew is "under" the multiplier's seconds rather than "about 0 s". Half a second and more still reads "1 s". Tests: tests/test_ui_report.py adds the sub-second case on the CPU, unlabelled, on ZeroGPU and at 0.6 s; tests/test_ui_run_end.py's check that the card states what the run used now accepts "under 1 s" (its fake run is sub-second).74d0925 -
fix: each sample's caption says it was made earlier by this app from its example, with that example's inputs and seed, and no longer promises the same result from the same prompt and seed (#20)
Unverified signatureRound 4, minor 8. The samples were made on the operator's Mac (Q8 GGUF transformer); on the Space the same prompt and seed give another take (mode 05 at seed 12: two crewmen on deck there, the ship from above in the sample), yet the captions said "Same prompt and seed as “Storm on deck”" or "same seed", inviting a Space visitor to expect the sample from 360 s of free quota. Every caption now reads "Made earlier by this app from “<example>”, with its <prompt / picture / clip / recording> and seed: ...": what the sample is and where it came from, with no promise of a repeat. The words live in examples/manifest.json. Test (tests/test_ui_sample_captions.py): every shipped caption starts "Made earlier by this app from “" and says neither "Same prompt and seed" nor "same seed".b46dfc2 -
fix: the Done card says "chosen by the model" only for a length strictly inside the range the user allowed, and at either end which end it is; "How quota works" gives the timeout card's step; no "legal" on the page (#20)
Unverified signatureRound 4, minor 14, three parts. The Length row. With "Let the model pick the length", diffusers clamps the duration head's figure to the shortest and longest the user allowed and snaps it to the frame grid; on the Space the head said 4.47 s, the range made it 5.0 s, and the card said "chosen by the model" (issue #16). The run record carries the frames rendered and the request the range; constraints.duration_head_frame_range gives the frame counts the head returns at each end, exactly as the pipeline clamps. A length strictly between them is the model's own figure, and only there does the card say "chosen by the model". At an end it says "the shortest you allowed" or "the longest you allowed" ("the only length you allowed" when both ends meet): true whether the range moved the figure or the model landed there, and the run's own note (#16) says what the model chose. The record has no field for the head's figure, so the card does not claim more than this. "How quota works" said a timed-…a8bf7a4 -
fix: "Use this prompt" turns Enhance off in the same step and says so ("Copied to your prompt; Enhance is off"), so the next run sends the enhanced prompt as it is; in a mode that takes no prompt it parks both instead of writing a hidden value (#20)
Unverified signatureRound 4, minor 9. After a run with Enhance on, the Done card offers "Use this prompt" with the prompt the model was sent. It wrote that prompt into the box and left Enhance on, so the next run enhanced the enhanced prompt again (on the Space, reserving the enhancer's seconds again): the next run did not use "this prompt". The click now writes the prompt and unticks Enhance together, and the button reads "Copied to your prompt; Enhance is off", disabled, until the next run offers it afresh. Found on the way: in a mode that takes no prompt (Image to video, after a switch) the click wrote into the hidden prompt box, which a run would then send; it now parks the prompt and Enhance, which come back with the prompt box, as a mode switch does. Tests (tests/test_ui_use_prompt.py, a run with a faked enhancer through handlers.run and the real generate(), the real finish step and click): the prompt is written and Enhance turned off, with the button's words; the next run offers the button afresh…8183336 -
fix: off CUDA a parked Upscale promises no size: while this machine cannot run it for the request, its label is the bare "Upscale ×2" and the cost panel shows no Upscale lamp; at a size it can run, both come back (#20)
Unverified signatureRound 4, minor 7. Where this machine cannot run Upscale ×2 for the request, the control is parked (unticked, disabled, the backend's reason as its line), but its label still read "Upscale ×2: returns 1408 × 960" over "Upscale ×2 needs a CUDA GPU; this machine runs on the CPU.", and the panel kept an unlit Upscale lamp. P12's rule, a size only when it will run, now holds here too. The review step, which already decides the parking, now writes the label with it: the bare label while parked, the returned size for a size the model takes otherwise. The size-hints step no longer writes the label, so two steps fired by one change cannot race over it. The panel drops the Upscale lamp while it is parked. Tests (tests/test_ui_parked_upscale.py, on the CPU platform, through the built page with its first paint): parked at the default size with no size in the label and no Upscale lamp; at 64 × 64 × 9 freed with "returns 128 × 128" and the lamp; at 704 parked again with the bare label; only the re…44c216d -
fix: arrow keys on a LoRA strength slider reach the run: the slider's input is wired as well as its release, last value wins, and the value it sends is held to the slider's own range (#20)
Unverified signatureRound 4, minor 1. The strength was wired to the slider's release only, and Gradio 6.24's slider sends release on pointer-up over the range or on leaving its number box; arrow keys on the range send input and change. A keyboard user saw 0.7 on the slider while the LoRA label, the cost panel's LoRA row and the run kept 1.0. Each row's slider now also listens to input (trigger_mode always_last), running the same step and the same label and review after it. Input fires on every keystroke in the number box too, and a typed value passes through numbers outside the range ("0" on the way to "0.7"), which Gradio's own slider preprocessing refuses with an error on screen; so the value input sends is held to the slider's min and max as the page holds them (read off the range element, elem_id lora-strength-N, since the LoRA package sets the range lazily). The pointer path is unchanged. Tests (tests/test_ui_lora_strength_keys.py, through the built page's own steps): an adapter staged through the …d468ab6 -
fix: the line beside Generate names what the run returns: the returned size, with "upscaled" when Upscale ×2 is on ("1408 × 960 upscaled, 5.0 s, needs … quota"), and "Sound" in a sound-only mode ("Sound, 5.0 s, …"), keeping the length and the quota or device words (#20)
Unverified signatureRound 4's M1. The one-line figure beside Generate (the desktop line over the button on a short window, and the phone and tablet bar's ready line) started from the render size: under Upscale ×2 it said "704 × 480, 5.0 s, needs 540 s quota" for a run that returns 1408 × 960, and in the three sound-only modes it named the 256 × 256 picture they render and throw away. The panel's Returns row, a few centimetres above, said otherwise. figure_line now starts from what the run returns, as the Returns row does: the returned size, with a no-break "upscaled" when stage 2 is on, or "Sound" when only sound comes back; then the length (or "the length of your clip" / "the length of your audio" where an input sets it, as the panel says), then the quota needed on ZeroGPU or where it runs elsewhere. commit_line's ready state is the same line. Tests (tests/test_ui_rail.py): the every-mode test that pinned the render size (test_the_mode_names_its_figure_in_every_mode) is rewritten to pin the returned si…05737f6 -
fix: mode 11 says an old-sounding recording can come out as a period film, and how to get colour: one sentence under its first-frame picture, above the prompt, in Audio to video only (#28)
Unverified signatureOn the Space the same prompt and recording gave a 1940s-film picture at seed 7 and colour at seed 21; with a first-frame picture the result is in colour. A user who expected colour got a period look and did not know why. The sentence is "An old-sounding recording can come out as a period film: say “in colour” in the prompt, or give a first-frame picture." It is in the caption of Audio to video's optional first-frame image, which sits between the picture input and the prompt box, the two remedies it names; the audio caption keeps its three sentences about lip-sync as round 3 pinned them. Test (tests/test_ui_copy.py, through the built page's own switch): in Audio to video exactly one shown component holds the sentence, the image caption, between the image and the prompt; in every other mode none does.9dcc63c -
fix: the decoder choices are named by what they do: "Auto", "Steadier (diffusion decoder)" and "Sharper (standard decoder)", in the choice, its line, the Upscale lock line, the Done card and the backend's refusals; the values sent stay auto, diffusion and conv (#27)
Unverified signatureOn the Space the same seed and prompt through both decoders gave the same scene: the diffusion decoder a little softer and steadier from frame to frame (fine detail 10.3 against 11.6, shimmer 1.47 against 1.88), the standard decoder sharper frame by frame with about 28% more shimmer (evidence/space/matrix/ab_decoder). The page called the softer one "Best quality" and the sharper one "Fast". Now the choices read "Auto" (still the vendor's default), "Steadier (diffusion decoder)" ("A little softer, steadier from frame to frame; takes a few seconds longer.") and "Sharper (standard decoder)" ("Sharper frame by frame, with a little more shimmer; faster."). Auto's line is true on every machine: "Diffusion decoder on an NVIDIA GPU that can run it, standard decoder elsewhere." Off CUDA, Auto always takes the standard decoder (pipelines.StageRunner._single_stage_decoder), so the old "where this machine can run it" was untrue on a Mac, and round 4 asked for the NVIDIA wording. The Upscale line …1c8a58d -
feat: a video + sound result offers its sound track as a quiet "Download the sound (WAV)" in the Done card's action row, beside Reuse seed, only when the run returned the picture and the sound as two files (#6)
Unverified signatureF30. Since 20155a1 every video + sound run also writes its sound as its own WAV and the public endpoint returns it, but the page played the video in one player and offered no way to save the sound alone. The action row that closes the Done card now holds a gr.DownloadButton (quiet, elem_id sound-download) set by the finish step to the run's WAV when the run returned a video and a separate sound file that is still on disk, and hidden otherwise: a sound-only or silent run, one file carrying both tracks, a failed run, and while a run is in flight. It is in the action row, not the monitor's corner toolbar, as round 4 asked (the corner clips focus rings, P17). Tests (tests/test_ui_sound_download.py): runs through handlers.run and the real generate() with the production writer (the pipeline faked), then the real finish step: a video with sound shows the link with the wav's path, beside Reuse seed; a sound-only and a silent run do not; one muxed file is not offered twice; a new run and a fa…99f710e -
fix: a request Gradio refuses before any handler runs can no longer leave the page on "Generating…": typed number fields declare no range, and a last failure listener that reads no input brings Generate back with a card (#5)
Unverified signatureF28, the hole left in F72. Two ways Gradio could fail the generation step while preparing its inputs, before any of the app's code ran: a seed typed below the field's minimum of -1, and an upload whose file Gradio's cache clean-up had removed after six hours. The failure step that brings Generate back takes the same inputs, so it failed the same way and the page stayed on "Generating…" with no card. Both reproduced through Gradio's own process_api: _on_generate Error then _finish_failed Error, and nothing after. The seed field no longer declares minimum=-1 (no typed number field declares a range now; sliders keep theirs), so a seed of -2 reaches the app's own gate, which refuses it before any GPU time in its own words ("seed=-2 is out of range: use a whole number from 0 to ..., or -1 for a random seed."), and the panel says so before Generate is pressed. After each failure step a last .failure listener (_finish_bare) takes no inputs, so nothing Gradio prepares can stop it, and sends …bfd58d1 -
fix: after a run every mode's sample can still be seen: while the monitor holds a run of another mode than the selected one, the button under the purpose line reads "See an example of <mode>" at every width (class mr-over-run), puts that sample on the monitor and lets later switches follow with their own, and reads "Back to your run" while a sample covers the run (#20)
Unverified signatureRound 4's M4: after one successful run no mode's sample could be seen again in the session. The monitor rightly kept the run when the mode changed (AC-06), the jump to the sample showed only while the monitor held a sample, and it was hidden at 1024 px and wider; a reload was the only way back, and it emptied Recent runs. The monitor state of a run now carries its mode, seed, files and whether it is an earlier run (Show). The button under the purpose line is decided from the selected mode and that state in one place (_jump_update): over a run of another mode whose mode has a sample it reads "See an example of Audio to audio" with the class mr-over-run (UI-A's stylesheet shows it on a desktop with that class); while a sample covers a run it reads "Back to your run", as long as the run's file is on disk; while the monitor shows a sample with no run under it, it is the phone's plain jump. A click puts the sample on the monitor with its usual caption and sets the state to "sample" with th…78036d2 -
fix: the image preloads the prompt enhancer too: a third preload_from_hub entry, generated like the others, fetches the 8 files its loader reads at its pinned commit (2.49 GB), so a first enhanced call in a fresh container no longer risks paying the ~88 s Hub fetch inside its GPU reservation; the start-up prefetch stays as the fallback (#23)
Unverified signatureThe reservation for Enhance is now sized for a warm enhancer (+80 s, #21). A first enhanced call in a container whose daemon prefetch (app.py, enhance.start_prefetch) had not finished would have spent the ~88 s download inside that reservation and could have been aborted. The enhancer repo, google/gemma-4-E2B-it-qat-mobile-transformers at dd693ff4, is not gated, so the Space's preload can fetch it at the same time as the model. One source. The repo id, the pin and the files with their sizes live in model_files (ENHANCER_REPO_ID, ENHANCER_REVISION, ENHANCER_SIZED_FILES / ENHANCER_FILES), and preload_from_hub_entries() emits a third entry from them, which the drift test keeps the README equal to. config.DEFAULT_PROMPT_ENHANCER_REPO and enhance.ENHANCER_REVISION now read those values instead of holding their own literals. The list lives in model_files rather than beside the loader in enhance.py because the architecture test (test_no_hardcoded_hub_strings_outside_model_files) admits a che…72b989d -
fix: start-up refuses a fallback download the disk cannot hold, before writing a byte: the missing files, ZeroGPU's packed copy still to be written and a 10 GB margin must fit in the free space (on ZeroGPU, also under its 150 GB cap), or start-up stops with one message naming the directory, the count and GB, the free GB and the remedy (#23)
Unverified signatureA download that fills the disk part-way is the worst failure a public Space can have; a clear refusal is better. ensure_weights now calls _require_room(missing bytes, count, cache directory, on_zerogpu) after it has found what is missing and before it says it is downloading. Needed: the missing bytes (from model_files' per-file sizes), a 10 GB margin and, on ZeroGPU only, the packed copy still to be written: ZEROGPU_PACKED_COPY_GB = 42.1 (40.6 GB measured on the 2026-11-13 boot, 41.24 derived, plus the 0.83 GB decoder now packed with it). A CUDA box that is not ZeroGPU packs nothing to disk, so it is not charged for one; it fetches the set with 81.9 GB free. Free: shutil.disk_usage of the cache directory (or its nearest existing parent). On ZeroGPU that is the host's filesystem -- the first deploy's report once read 1969.8 GB free of 8589.9 GB there while the workload was being evicted (pipelines.disk_footprint's docstring) -- so on its own it could never refuse. On ZeroGPU the room …ff62c55 -
fix: the diffusion decoder is built once at start-up, beside the pipeline, so ZeroGPU packs it and every run's worker uses that instance instead of loading it again; a start-up build that fails logs one line and leaves the per-run build as before (#17)
Unverified signatureOn the Space the default decode is the diffusion decoder. It was built lazily inside each GPU worker and lost with it: every run loaded its 0.83 GB and resolved its NATTEN kernel over the network again (its load message appeared in every run's log of deploy 1). pipelines.build_decoder_at_startup(device=...) builds it with the existing _decoder_part, after the runners, and caches it where the runners' decoder factory already looks. app.py calls it at module scope in the CUDA branch, after the two get_pipeline calls, so its .to("cuda") is intercepted and registered for packing with the other components before demo.launch(); a forked worker's runner then finds the instance through _decoder_part's cache. get_pipeline itself still builds no decoder. Whether the NATTEN fetch needs a GPU at load time: it does not. diffusers' processor calls kernels.get_kernel("shi-labs/natten", version=1): the version-to-ref lookup and the variant download are network and disk; the build variant is chosen f…ed13532 -
fix: the Space's weights come from the image: preload_from_hub is live for exactly the 35 files the int8 Space loads (71.92 GB; the temporal upsampler, which nothing loads, is no longer fetched), every file carries its size in model_files, and start-up downloads only what the image lacks, saying how much (#23)
Unverified signatureThe Space is public now, so the gated repo can be preloaded; while it was private the preload step ran without the Space's secrets and got 401, and every cold start downloaded 72.19 GB itself (17 min 24 s on 2026-11-16, 14 min 55 s of it the download). model_files is the single source of the set and its sizes: each component lists its files with their byte sizes from the Hub's own listing at the pinned commits, size_gb is derived from them, and file_size / total_size_bytes answer per file and per set. temporal_latent_upsampler moves to the declared-but-not-fetched group: StageRunner wires only the spatial latent_upsampler and model_index.json does not list it, so it cost 0.26 GB on every start for nothing. The set goes from 37 files / 72,185,863,109 B to 35 files / 71,923,919,050 B. README front matter: preload_from_hub is live, generated by model_files.preload_from_hub_entries() (two entries, one per pinned commit: the decoder is pinned later), and its comment says what it does, why…41dcf05
3 days ago
-
fix: on short desktop windows the cost figure stays beside Generate, what a click changes comes into view, and Generate never leaves the rail
Unverified signatureAt 1366 x 657 and 1280 x 680 the stuck Generate covered 99-157 px of the cost panel at first paint (Reserves and Needs hidden, a 4 px band of covered text under the button); a failure card landed out of sight beside an enabled Generate; Show changed a monitor scrolled away; with the rail scrolled to its end Generate could leave at the top (review round 3, R1 and R2). - The rail script fits the monitor, its caption, the cost panel and Generate into the rail at rail scroll 0: on a short window the monitor gives up height first, down to 180 px, letterboxed; if the panel still runs under Generate, the panel's figure line ("704 x 480, 5.0 s, needs 360 s quota"; off ZeroGPU "on the CPU") stands above the button. With room to spare the caption keeps four lines less the panel's notes, so Generate stays put from mode to mode (P16). - Generate is sticky at both of the rail's edges, flush with them: no band of covered text shows past it, and a row passing under either edge runs into …3a32028 -
fix: off ZeroGPU the page names no meter: the cost panel says where the run happens and that nothing is metered, and no caption, card or reason speaks of quota, reserving, billing or paying
Unverified signatureThe lead's real-weights session on this Mac read "Reserves 180 s of GPU time", "Needs 360 s of quota free to start", "Billed for GPU time used x 2", "you pay for that GPU time" and "Any GPU time this run used is billed". adaf178 made the running sentence follow handlers.run_platform(); now everything else does (F75). Where the app is not on ZeroGPU: - the cost panel: Reserves / Needs / Billed give way to one row, "Runs on the CPU; nothing is metered" (on this Mac's GPU, on the GPU: the Done card's device words); the lamps carry no seconds; the refused panel says Generate stays off until the problem is fixed; the phone bar reads "704 x 480, 5.0 s, on the CPU"; - "How quota works" is not on the page; the column notes, the Enhance, Upscale and LoRA lines say what happens without a meter; - every failure card, the lost run and the empty-file card have no billing sentence; a request refused before running says "Nothing ran."; the quota and per-run-limit cards, which a local run…ab0c4df -
docs: the output folder is described: one outside the working directory and the temp dir is passed to Gradio as the one allowed path, and a result the page cannot show ends with a card, never on "Generating…"
Unverified signatureREADME, local settings: a row for LTX25_OUTPUT_DIR (outputs by default). A folder that resolves outside the working directory and the system temp dir is passed to launch as the only allowed_paths (e7cde1a), so the page can show what is written there; Gradio 6.24 reads GRADIO_ALLOWED_PATHS only when no allowed_paths is passed, so for that launch the folder takes its place. The README's closing rule (no code path where you press Generate and see nothing change) now names the case it missed until 55692f5: a file Gradio refused to serve left the page on "Generating…"; such a run ends with Generate back and a card saying the run finished but its result could not be shown, with the server's message. PLAN.md §2.7 gets the same as an "as built" note, with the one caveat from e7cde1a: a launcher that calls app.demo.launch() itself must pass the same arguments.c3c8672 -
docs: the local memory check is described as it now works: it waits for memory just freed to leave the gauge, reads a failing check again before it refuses, and its refusal is a kind of its own
Unverified signatureREADME, local section: a row for LTX25_MEMORY_SETTLE_SECONDS (2 by default, 0 to 60, 0 switches the wait off) and a paragraph on why the check waits. Freed GPU memory on the Mac leaves the gauge over a moment: the kernel gave the text encoder's 24 GB back over 0.1-0.35 s, so a reading taken at once was 3.5-23 GB too high, and with a browser and test suites running it refused a run that fitted. After a release the check now reads the gauge until two readings 50 ms apart agree within 0.25 GB; a failing check is read again every 0.1 s; both within that bound (memory.py at ba2d582 and a5caa41). On real weights the settled readings were 3 to 13 GB lower, in 0.16-0.36 s, and the three refused runs ran. A refusal is reported as its own kind, not as an app error (errors.MEMORY, 04c841e). The README's "a real-weights run through the UI on a Mac is not verified yet" is no longer true: through the page in a real browser, audio to video and text to video with an uploaded adapter finished; text to…68c528c -
docs: the local matrix records the final pass: every mode, the adapter, the enhancer and the model-chosen length run again on the final code, identical wherever compared with a run made after the RoPE fix
Unverified signatureSPACE_MODE_MATRIX.md §10.2 gets the lead's final pass (run log, 2026-11-16 19:16-20:16): fourteen runs on e59944e, each with the inputs, prompt, size and seed of an earlier run and compared with it, plus F11b_ocean and F11c_rail for mode 11's new sample and second example. Modes 01, 03, 04, 09, 10, 11, the adapter, the enhancer and the model-chosen length are identical to their references (SSIM 1.000, sound 1.000); 02, 05, 06 and 07, compared with runs from one commit before the float64 RoPE fix, show the same scenes framed slightly differently (SSIM 0.78-0.94), the same words and sound, and frame 0 of mode 02 at 0.7507 as before; mode 08 has the same sound. Lip sync on these outputs: +0.845 in mode 07, -0.379 in mode 11. Three runs refused on e59944e by the memory check's early reading (mode 08 twice, the enhancer, the model-chosen length at the denoise check) ran on ba2d582, with the settled readings 3 to 13 GB below the first ones; their peaks (77.0, 77.6, 84.5 GB) and the pass's (6…0300944 -
fix: a run whose result Gradio cannot show ends with Generate back and a card saying the run finished, what it used and the server's message, never stuck on Generating
Unverified signatureOn real weights the run finished and wrote its file, then Gradio refused to serve it (the output folder was outside the working directory and the temp dir) while it processed the step's outputs, after the handler had returned. Gradio 6.24's page then runs only that step's `.failure` listeners: in its Blocks script an `error` status throws, and the catch dispatches the failure triggers alone (`.then` runs only after `complete`). The listener wired there was the finish step itself, which re-sent the same file, failed the same way in Gradio's postprocessing, and nothing was left to bring Generate back. The `.failure` listener after /on_generate is now a step of its own, and the finish step has the same one after it. It sends no file, so it cannot fail the way the step before it did: Generate comes back, the monitor returns to its idle frame holding no file ("The result could not be shown"), and the report says the run finished but its result could not be shown, what it used (by device; b…55692f5 -
docs: the local matrix records video to audio on a clip with no sound track at all, the run behind the mode's shipped sample
Unverified signatureRow 09 of SPACE_MODE_MATRIX §10.2 listed only the runs at b12415f, where the clip had a sound track that never reached the model. S09_captain_voice (at 7cf1547) ran on a copy of the same clip with no sound track: the generated voice's loudness follows the track the clip originally had at 0.926. It is the run the mode's sample output comes from.1132d15 -
docs: running locally is described as one code path with the Space: the same stage graph, with the local runner supplying only what is resident when
Unverified signatureSince c712e7e the local runner is a StageRunner: the decode policy, stage 2 and its refusals, the audio conditioning, the clip variation and the run facts are one piece of code, and the local side adds residency through one seam. The README's local section and PLAN §7.1, §7.4 and §8.7 now say so, and what follows from it: off CUDA the default decode is the conv VAE and the run says why, and an explicit diffusion decode or Upscale x2 is refused before dispatch except at very small sizes. The measured memory and time figures stay, with the day's full range (peaks 57-72 GB at 704x480 or 480x704, up to 193 frames) and the enhancer's runs added. SPACE_MODE_MATRIX §10.2 says which of its runs predate the change.1f05c04 -
docs: audio to video is said plainly not to lip-sync, with the measurements, and a face that speaks in time is sent to image + text to video with sound
Unverified signatureThe README's audio section gains "Speech and lips": in audio to video the mouth's opening does not follow the words (correlation between -0.38 and +0.07 in every run scored, no better than an unrelated track), while speech the model writes itself scores +0.84; prompting for lip sync with the quoted words did not change it; holding the audio differently while sampling plus cross-modal guidance reached at most +0.26 in a probe and is not in the app; the vendor's lip-sync recipes for LTX-2.3 use the non-distilled model. SPACE_MODE_MATRIX §10.2 gets the lead's three tables as STATUS has them (the reference and controls, the prompt-technique A/B on the app's own path, the sampling probe) and the conclusion; row 11 no longer reads as if the man spoke the recorded line, and points to them.b27082c -
docs: the audio modes are described as measured after the audio-encoding fix, and the API's noise_scale default is said to snap to "a little"
Unverified signatureThe known-issue box about the 9 dB loss is gone: the cause (the mel transform's window taken from the vocoder's config) is fixed at 7cf1547. In its place the README states what the lead measured on real weights afterwards: audio to audio returns sound at the input's own level, graded by the choice (same events at the same times 0.97 / 0.95 / 0.71 on speech, transcript exact at "a little"); video to audio follows what is visible (on a silent clip of a shouting man, a voice whose loudness follows the clip's original track at 0.92); audio to video carries the recording exactly and takes its length from it, with or without a prompt and a first-frame image. Through the API, noise_scale has to be passed for video to video and audio to audio: the published default 0.5 snaps to 0.42 in both. SPACE_MODE_MATRIX §10.2 rows 10 and 11 carry the runs at 7cf1547 and the fixed defect, including the black-and-white pictures it caused; PLAN §5.4 says the analysis window is a declared convention, not a …67c1514 -
docs: video to video is described as verified on real weights: a variation of the clip at three levels, with the prompt acting at the highest
Unverified signatureThe README, PLAN §3.3 and the local matrix (SPACE_MODE_MATRIX §10.2) now say what the lead's runs of the new mechanism showed (V04_* at 85405e9, S04_summer_l091 at 7cf1547): SSIM to the clip 0.78 / 0.65 / 0.36-0.40 at "a little", "moderately" and "a lot"; the prompt acts only at "a lot"; it runs without a prompt; a sideways-stored phone clip comes out upright and a 60 fps clip is read in real time; the length is the clip's. All eleven modes are therefore verified locally, and every count of them says so. The follow-up comments the first docs pass left are gone. The Matroska/WebM length defect (F70) is not listed as a known issue: it is fixed at 16bbbd3.41d0e94 -
docs: UI_DESIGN describes the rail, parking, the levers and the report as the code now does them
Unverified signatureThe rail did not scroll inside itself (it wrapped off-screen); it does now, and the doc says how. Also brought up to date: the registry-derived media order, parking of hidden sizes and ranges, Restore through the switch, the clip and sound change choices, the decoder under Upscale, the status region and the column notes for assistive tech, the failure cards, "Took" by device, Show in Recent runs, the line-strong token and the native controls.e29af58