diffusers

745d7984 - [LTX-2.5] stop the decode pipeline second-guessing the scheduler's config

[LTX-2.5] stop the decode pipeline second-guessing the scheduler's config `_check_scheduler` warned on `shift`, `shift_terminal` and `stochastic_sampling`, saying the decode "will be worse". That was wrong. Those are properties of the schedule the LTX-2.5 checkpoint happens to be distilled on, not of diffusion decoders in general, and a finetune is free to prefer something else — `shift=5.0` reshapes the sigmas from [1.0, 0.667, 0.333] to [1.0, 0.909, 0.714] and decodes perfectly well. Being able to make that change is the reason the loop moved onto a scheduler in the first place; warning about it takes back what the move gave. The precedent I had in mind does not support it either: the `steps_offset` / `clip_sample` checks in the older pipelines correct known-broken legacy configs, which is not the same as flagging a deviation from a default. What is left is the one setting this pipeline genuinely cannot drive: `use_dynamic_shifting` needs a resolution-derived `mu` that it never computes, so the decode cannot run at all. That now raises with a pointer to `diffusion_decoder_scheduler`, which matters because it is exactly what `scheduler=pipe.scheduler` hands you and the scheduler's own "`mu` must be passed" does not say where to find a working one. The two warning tests are replaced by their opposite: one pinning that a reshaped schedule reaches the decode and changes it, one pinning the error. The component docstring and the decode docs made the same overstatement and are corrected to match. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>