Merged
Conversation
laggui
approved these changes
Apr 14, 2026
Member
laggui
left a comment
There was a problem hiding this comment.
Thanks for linking your implementation!
The tests currently seem to trigger independent, unrelated bugs in both the ndarray and cpu backends. I'll file issues once I figure out the causes.
Please do once you figure out the issue 🙏
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'd like to add my project privacyresearchgroup/wav2vec-burn to the community contributions table.
It's intended to be a readable implementation of wav2vec 2.0, currently only for study purposes, but we might use it in production in the future at Signal at some point. It currently only supports the
baseandlargevariants of wav2vec.I'm actively working on this project, so more documentation, testing, and support for more variants will come soon. Support for fine-tuning after that.
The tests currently seem to trigger independent, unrelated bugs in both the
ndarrayandcpubackends. I'll file issues once I figure out the causes.