"Cannot copy out of meta tensor; no data!" means some parameters were never
materialised, and it names none of them -- which sends the reader hunting for
a corrupt file.

Measured on LTX-2.3-10Eros and -PinkCherry: diffusers already ships
convert_ltx2_transformer_to_diffusers and it works almost completely, mapping
their 4444 GGUF tensors onto exactly the 4186 the class expects. Precisely 12
remain unprovided, all in one conditioning branch, identically in both
fine-tunes. So the checkpoints are fine and the converter is fine; those
fine-tunes were exported without that branch, and the 12 stay on the meta
device.

The refusal added earlier now carries that analysis: how many tensors mapped,
how many remain, and which submodules they belong to. Best effort throughout
-- any failure to analyse returns nothing and the original error stands.

It deliberately does NOT offer to fill them in. Supplying parameters a
checkpoint does not contain is a substitution, and the surrounding refusal
exists precisely because a silent substitution (here: the 38 GB bf16
transformer, on a 24 GB card) is worse than a failure. A test pins that: the
hint must not grow a flag that papers over it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014T3rZnmWyKjWZerwsb27jZ