LTX-2.5 community integration proposal: distilled-control boundaries in a Mac video API
Proposing a community deployment note for the distilled LTX-2.5 MLX Q8 path, separate from the card's CUDA, ComfyUI and Diffusers instructions.
Rapid-MLX exposes asynchronous video jobs and a capabilities endpoint. Its LTX-2.5 tests cover the distilled control surface and packaged-runtime integrity. A community example should use those advertised controls, preserve the 8n+1 frame constraint, and avoid copying guidance/negative-prompt parameters that the selected path rejects.
The model card describes an audio/video system; a completed video file alone would not establish the audio behavior. The final acceptance receipt should include both tracks, dimensions, frame count, exact conversion/runtime and measured memory. This proposal does not resolve the separate ComfyUI Apple Silicon error thread or claim parity with its workflow.
Concrete catalog entry: ltx-2.5-mlx-q8 → MrMofer/ltx-2.5-mlx-q8@f1b56e7dc89f71a9af2cddac787b89ed22a8b7fc. This is a conversion/distribution artifact; it is not presented as an official upstream release.
Source references (fixed Rapid commit): catalog, video API guide, LTX-2.5 contracts.
Verification status: this proposal is based on reading the catalog, implementation and the linked documentation/tests. No fresh model inference or test-suite run was performed for this submission; source tests are not an end-to-end qualification. It requests a community documentation scope, not an official endorsement or a performance listing.
Disclosure: I maintain Rapid-MLX. Prepared with AI assistance under my direction. Anonymous usage-metadata telemetry is enabled by default; DO_NOT_TRACK=1 disables it. The original model and conversion terms continue to apply.