LTX2.5-Studio / docs /SPACE_MODE_MATRIX.md

Commit History

2 days ago

  1. 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 signature
    abc9150
  2. 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 signature
    ca1f2a8
  3. 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 signature
    c8c5965
  4. 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 signature
    da5f47d
  5. 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
    0646770

3 days ago

  1. 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 signature
    0300944
  2. 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 signature
    1132d15
  3. 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 signature
    1f05c04
  4. 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 signature
    b27082c
  5. 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 signature
    67c1514
  6. 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 signature
    41d0e94
  7. docs: the enhancer is verified on real weights after its transformers 5.23.0 fix, and the 9 dB audio loss has a found cause⁠

    Unverified signature
    7dd6ff6
  8. docs: the local matrix calls the test inputs generated images, not photos⁠

    Unverified signature
    71b405c
  9. docs: the local matrix and the README follow the lead's later runs: mode 11 follows colour words, and the audio encode loses about 9 dB⁠

    Unverified signature
    1c9e1f6
  10. docs: the mode matrix says what has been verified since the fixes, and that the Space has not been re-run⁠

    Unverified signature
    342075f

  1. docs: the app ran its whole life on half a GPU — `auto` cannot promote, and four documents said otherwise⁠

    Unverified signature
    caf1083
  2. docs: the NVML allocator assert has been seen three times — collected, hypothesised, and deliberately not chased⁠

    Unverified signature
    06acd83

  1. docs: every Space generation result was garbage — the invalidation, stated at the top⁠

    Unverified signature
    898dad2
  2. docs: the 2026-08-25 session — byte identity sha256-verified, 1216x704 proven, the stage-2 ceiling found⁠

    Unverified signature
    76c408d
  3. docs: the audit's stale claims annotated — measurements stand, corrections dated on top⁠

    Unverified signature
    fd85c87

  1. docs: 11 of 11 on the Space, and what that still does not claim⁠

    Unverified signature
    17b589c
  2. docs: name why the picklability finding is load-bearing, not incidental⁠

    Unverified signature
    fc566af
  3. docs: the fork-boundary fix is a pair, and half of it is a regression⁠

    Unverified signature
    f927c4e
  4. docs: nine of eleven modes generate, and the failure is video input⁠

    Unverified signature
    99e3652