-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lewton_decoder as default, libvorbis_decoder as optional #124
Conversation
86946d0
to
5d5e081
Compare
cc @est31 |
Are there any upsides/downsides to doing this? Presumably libvorbis is more mature? |
Upsides:
Downsides:
|
Thanks for clarifying. Sounds like we could make the switch to lewton as default without too much impact then. We may also want to consider switching the default build mode to release if we do make lewton the default, depending on the speed, but given that librespot is eventually to be the behind-the-scenes library for the daemon, it's probably unnecessary. Thoughts? |
AFAIK there isn't a way of changing what There's a couple of other places in librespot which are pretty slow in debug mode (generating DH keys during handshake for example takes a handful of seconds on x86_64, and likely a lot more on low end devices) so this isn't really a concern to me. |
a3fc178
to
ade0797
Compare
I have rebased this against current #123 It now builds as follows:
In summary:
Chosing between lewton and vorbis: |
ade0797
to
f400a89
Compare
If no one objects, I'll merge this in a couple of hours and update the docs. |
Switch
lewton_decoder
as default andlibvorbis_decoder
as optional after #123Works fine here