mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #951] Dynamic Normalization is to much for a Pi Zero to handle. #463
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#463
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JasonLG1979 on GitHub (Jan 27, 2022).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/951
See:
https://github.com/dtcooper/raspotify/issues/504
Basically the combination of (the new) dynamic normalization and the CPU spike that generally happens when a track is buffering is just above what the Pi Zero can handle and it throws ALSA into a error loop that hangs the CPU at 100% for a while before finally dying.
There's not much that really can be done I don't think, this issue is more for something to link to if others have the same problem.
The solution is to just not enable dynamic normalization on the Pi Zero. Feel free to close this or leave it open @roderickvd if you like?
@roderickvd commented on GitHub (Jan 27, 2022):
A reason to not deprecate the basic limiter I think.
Have your users and you tried with dithering disabled? Maybe the Zero has enough oomph to do one but not both.