50a792283c
Initial alignment showed PSNR ~12 dB because public's LTX2_BASE preset sets ``ltx2_modality_scale_video=3.0 / rescale=0.7 / stg_video=1.0`` while internal's default ForwardBatch lands at ``1.0 / 0.0 / 0.0``. Pinning these explicitly on both runs aligns the denoising mechanics so the diff measures pipeline parity, not preset divergence. Result with both sides pinned to mod=1.0/rescale=0.0/stg=0.0: max_abs_diff = 203 mean_abs_diff = 0.788 rms_diff = 1.864 psnr_db = 42.72 dB exact pixels = 52.87% within 1 lvl = 86.94% within 4 lvls = 97.93% The ~47% near-but-not-exact bucket is consistent with bf16 reduction non-determinism on B200 plus the fact that the public LoRA matcher emitted "applied to 0 layers" for the LTX2-Distilled refine LoRA (internal side did not). Both runs effectively skip the refine LoRA, so they share the same effective stage-2 model — the residual diff is the right ballpark for "same algorithm, different bf16 reduction schedule". The typed-API path also sets the same overrides via setattr on the GenerationRequest so the typed path stays comparable. Once the typed SamplingConfig grows ltx2-specific fields the setattr workaround can go. Co-authored-by: Junda (David) Su <90978028+Davids048@users.noreply.github.com> Co-authored-by: Matthew Noto <99706358+RandNMR73@users.noreply.github.com> Co-authored-by: XOR-op <17672363+XOR-op@users.noreply.github.com> Co-authored-by: Zhang Peiyuan <42993249+jzhang38@users.noreply.github.com>