Skip to content

docs: add ANE float16 beeping issue to iOS CoreML issues#16

Merged
Alex-Wengg merged 2 commits intomainfrom
docs/ane-float16-beeping-issue
Jan 31, 2026
Merged

docs: add ANE float16 beeping issue to iOS CoreML issues#16
Alex-Wengg merged 2 commits intomainfrom
docs/ane-float16-beeping-issue

Conversation

@Alex-Wengg
Copy link
Contributor

Summary

Context

The Mimi decoder has 23 streaming state tensors fed back every 80ms. When running on the ANE (native float16), precision errors compound across frames in overlap-add buffers and attention caches, producing beeping artifacts. Switching to .cpuAndGPU for the Mimi decoder specifically fixes the issue while keeping other models on ANE for performance.

Add issue #7 documenting the Mimi decoder beeping artifact caused by
ANE float16 precision loss in streaming state feedback. Update issue #4
to reflect the per-model compute unit configuration.
- Add issue #8: voice-dependent duration differences between MLX and CoreML
  (azelma -2.00s, javert +1.92s — model-level behavior, not fixable in Swift)
- Update issue #4: all models now use .cpuAndGPU (not per-model config)
- Update issue #7: reflect all-models .cpuAndGPU fix
@Alex-Wengg Alex-Wengg merged commit fe10dd3 into main Jan 31, 2026
@Alex-Wengg Alex-Wengg deleted the docs/ane-float16-beeping-issue branch January 31, 2026 02:45
Alex-Wengg pushed a commit that referenced this pull request Feb 3, 2026
`torch.no_grad` is thread local, I now run the autoregressive generation
in a separate thread, in addition of the thread running mimi, and forgot
to add `torch.no_grad` to the function inside this thread.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant