Repository navigation
Slice update with operation - #3266
Merged
Merged
Conversation
Member
Author
|
Fixed CUDA. This is the benchmark on H100 now, pretty clearly faster than PT |
1 task done
This was referenced Jun 4, 2026
fix(audio_vae): work around mlx 0.31.2 Metal strided-scatter bug (silent audio)
dgrauet/ltx-2-mlx#35
Closed
dgrauet
added a commit
to dgrauet/ltx-2-mlx
that referenced
this pull request
Jun 7, 2026
mlx 0.31.2 shipped a Metal scatter-kernel regression (ml-explore/mlx#3266, reported as #3477, fixed upstream by #3483 but not yet released) where `mx.array.at[<strided slice>].add()` mis-indexes its source on the Metal backend. The audio path used that op for zero-insert upsampling in the BigVGAN vocoder (UpSample1d) and the BWE resampler (HannSincResampler), so the corrupted zero-insert fed every SnakeBeta activation and collapsed the waveform to near-silence (mean ~-52 dB vs the healthy ~-13 dB). Video was unaffected. Both call sites now use plain strided assignment, which is equivalent (the destination is freshly zeroed) and correct on mlx 0.31.1, 0.31.2 and main. No version pin is added: 0.31.1 is itself unsafe on some setups (Metal watchdog crashes at text-encode) and mlx-lm>=0.31.3 requires mlx>=0.31.2. Validated end-to-end on mlx 0.31.2: generate (q4, distilled, 576x384x65) audio measured at mean -13.4 dB / max -1.4 dB (was -52 dB pre-patch). New tests assert both call sites against a NumPy reference (fail on 0.31.2 pre-patch, pass post-patch) plus a framework canary that skips with a diagnostic on an affected backend. Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
slice_update_opvariants. Allow for faster implementation of slice updates that don't fall back to scatter. The CPU and CUDA implementations are still missing (will add them before merging).There are still optimizations to be done but the first numbers are (M3U gpu)
where
MLX^-means before this PR so it converts the slices to index arrays and uses scatter.One of the main benefits of this PR is that changing code like
x[idx] += 2tox = x.at[idx].add(2)will almost certainly be significantly more efficient now since it will allow donatingx.The CPU version gets a pretty big boost as it is much simpler to implement (and I added a small SIMD optimization). M3 Ultra numbers below: