Spaces:
Running on Zero
Running on Zero
Commit History
2 days ago
-
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
3 days ago
-
fix: the Space harness gates a chained input when its file exists, runs the app's gate as the Space does, and can carry the lead's matrix over several days
Unverified signatureTwo harness tests were red. The dry run handed generate.prepare_request a made-up path for an input an earlier call produces, and since the app opens every video before dispatch that path was refused: the harness's validation was wrong. A call with a chained input is now marked "checked when it exists" in the dry run, and the app's gate runs on the real file, before anything is sent, once the producer has run; every call whose inputs exist still goes through prepare_request, and a bad real file is still refused offline. The example plan test wrote 0.34 s of audio for every wav, so any set length was refused: its fixture now has the lengths, rates and channels of the lead's files, and the plan was stale too. The gate runs as the Space runs it. Stage 2 and the diffusion decoder are refused off CUDA, so on a machine with LTX25_DEVICE=cpu or mps the gate would have applied that machine's limits to a Space plan; device.current() now answers with the Space's own resolution (ZeroGPU, CUDA) w…6ae3c5a -
feat: the Space harness runs a plan of calls by field name inside a hard daily GPU budget, and keeps the evidence of every call
Unverified signaturescripts/space_matrix.py could only loop the eleven modes at 256x256x9 with one prompt and six settable fields, could not apply a LoRA, fed each conditioned mode the harness's own earlier output (so "follows its input" proved nothing), priced an enhanced call at half what the app reserves, kept its ledger inside whichever checkout ran it, and never saw the queue's progress events. A plan (--plan FILE) is a list of calls: a label, a mode, any /on_generate field by its key (a field appended to ui/fields.py is passed through once the spec has it), media as files under --assets-dir, optional LoRAs and an expectation. An input comes from an earlier call only when the plan says {"from_call": ...}, and the record says "chained". --plan default is the old loop with its chains written out, --mode builds one call from flags, --only picks labels. Every call is checked offline by the app's own generate.prepare_request (limits, required inputs, the length an audio mode takes from its audio) and aga…d043b52