topabaem commited on
Commit
fa92dce
·
verified ·
1 Parent(s): 77ec797

Point the card at the BF16 comparison, including where it loses

Browse files
Files changed (1) hide show
  1. README.md +33 -12
README.md CHANGED
@@ -65,18 +65,39 @@ harmless on this calibration set and fragile by construction.
65
 
66
  ## Samples
67
 
68
- `samples/` holds five clips made with `A3` driving `LTX25-distilled-DiT-Q3_K_M.gguf`
69
- — 768x512, 24 fps, video and audio muxed, 2.0-4.0 s, one seed per prompt, no LoRA
70
- and no latent upscale. Prompts and per-clip notes are in `samples/README.md`.
71
-
72
- `sample-00` is the representative one: an actual robot, dome head and segmented
73
- neck, and the BF16 encoder renders the same thing from the same card and seed.
74
-
75
- `sample-01` through `sample-03` do **not** follow their prompts no robotic hand,
76
- no four-legged robot, no swarm of wheeled robots. The BF16 encoder fails those
77
- same three identically, across seeds and CFG up to 6.0, so it is a limit of
78
- LTX-2.5 distilled rather than compression damage. They are published unedited
79
- instead of being cherry-picked out.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
80
 
81
  ## Memory
82
 
 
65
 
66
  ## Samples
67
 
68
+ `samples/` holds every clip twice once from the **BF16 original (26.264 GB)**
69
+ and once from this **4-bit build**, with everything downstream of the encoder
70
+ held identical: same DiT, same seed, same schedule, same VAE settings, one
71
+ process. `compare-NN.mp4` stacks each pair, BF16 on the left.
72
+
73
+ Two sets, because they answer different questions. `compare-NN.mp4` uses the
74
+ vendor's `euler_ancestral`, which is what you actually get; it re-rolls noise
75
+ every step, so the two builds return different *takes*. `compare-det-NN.mp4`
76
+ uses deterministic `euler`, where the seed fixes the starting noise and the
77
+ conditioning is the only thing left that can move a pixel that is the set
78
+ that attributes a difference to the encoder.
79
+
80
+ Mean absolute error against BF16 over every decoded frame:
81
+
82
+ | clip | `euler_ancestral` | `euler` |
83
+ |---|---:|---:|
84
+ | robot in rain | 0.0172 | 0.0182 |
85
+ | dune | 0.0596 | 0.0580 |
86
+ | forge | 0.0098 | 0.0129 |
87
+ | night road | 0.0702 | 0.0252 |
88
+ | smoke | 0.0128 | 0.0165 |
89
+
90
+ **Four of the five deterministic pairs hold together** — same composition, same
91
+ lighting, same timing, differing in surface detail. **The dune does not**: BF16
92
+ renders a soldier in fatigues where the 4-bit renders a man in a business suit,
93
+ from the same seed under a deterministic sampler. That difference belongs to
94
+ the encoder, and it is published rather than cropped out. The qualification it
95
+ deserves is that neither build followed that prompt — it asked for an astronaut
96
+ and got neither — so the model had no confident answer there for a small
97
+ conditioning change to disturb.
98
+
99
+ `samples/README.md` carries the prompts, the per-clip conditioning drift, and
100
+ what these clips do and do not establish.
101
 
102
  ## Memory
103