mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #681] Librespot: thread '' panicked at 'attempted to zero-initialize type vorbisfile_sys::ov_callbacks, which is invalid' #389
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#389
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 @heitbaum on GitHub (Mar 26, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/681
With LE10 - librespot was failing due to an error in vorbis-rs
https://github.com/LibreELEC/LibreELEC.tv/issues/5038
the fix was identified in https://github.com/tomaka/vorbis-rs/issues/19 and https://github.com/RustAudio/lewton/issues/89
we are adding a patch to LE10 to have librespot working via PR https://github.com/LibreELEC/LibreELEC.tv/pull/5166 and specifically the following patch to the librespot 0.1.6 source https://github.com/LibreELEC/LibreELEC.tv/pull/5166/commits/04c7591233348c9d845a36fd9696e325e09f8b44
would be great if you could have this or similar included in the mainline librespot.
@Johannesd3 commented on GitHub (Apr 19, 2021):
Seems as if vorbis-rs isn't maintained anymore by @tomaka. Should librespot create its own fork? Maybe we can share some code with librespot-tremor, as it is essentially the same.
@roderickvd commented on GitHub (Apr 19, 2021):
While forking seems a fine idea if we want to keep
libvorbissupport around, is that indeed what we want to do? What does it add overlewton, that's fast enough even on a RPi Zero? Even fortremorI'm not sure which hardware without hard float support is actually a target forlibrespot.@roderickvd commented on GitHub (May 18, 2021):
@heitbaum removing support for
libvorbisandtremoris under serious consideration. As far as I know,LibreELECis the only thing downstream that compiles with--features with-vorbis. Any arguments against moving tolewton100%?I just checked and compiling
with-vorbisonly saves 167 kB. Likewise the slight boost in performance will be neglible. At the same time, the bindings are unmaintained and only pass integer samples instead of the floats they were originally in, causing quantization error and lower sound quality. Finally, there is no Rust-unsafe code inlewton. So there's a lot to say about moving tolewtonand nothing of significance for keepinglibvorbisas I can see.Thanks in advance for your feedback, I'll be submitting a PR to remove
libvorbisandtremorsoon.@heitbaum commented on GitHub (Nov 20, 2021):
I have just raised the PR for LIbreELEC for 0.3.1 - just asked our forum for someone to test. All updated with your vorbis cleanups 👍 https://github.com/LibreELEC/LibreELEC.tv/pull/5891 and https://github.com/LibreELEC/LibreELEC.tv/pull/5892
@roderickvd commented on GitHub (Nov 20, 2021):
Great stuff @heitbaum!
pkg-configto docker build container #904