Skip to content
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

unsafe-libopus: how well does it work for encoding? #1

Open
DCNick3 opened this issue May 12, 2024 · 1 comment
Open

unsafe-libopus: how well does it work for encoding? #1

DCNick3 opened this issue May 12, 2024 · 1 comment

Comments

@DCNick3
Copy link

DCNick3 commented May 12, 2024

Hi =)

I see that you are using unsafe-libopus in your project. I think last time I touched it and tried to make more comprehensive tests, I encountered some problems on the encoding side of things.

I think the version in crates.io might not be affected by this, but the master, having some more refactors, might be. Just thought I should let you know. I do eventually plan to figure it out and make better tests to prevent this, but right now it's broken AFAIK =(

@hazelmeow
Copy link
Owner

Hi! I'm using 0.1.0 from crates.io and it seems to be working so far. Cool project, you saved me from my attempts to compile libopus to wasm directly :)

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

No branches or pull requests

2 participants