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

Rust implementation behaves differently to the depreciated recognize_song method #138

Open
tjosgood opened this issue Apr 4, 2025 · 1 comment

Comments

@tjosgood
Copy link

tjosgood commented Apr 4, 2025

Not sure if this is a bug or just an FYI, I found that using the new .recognise has a lower success rate compared to the old recognize_song method.

With several random audio files, sending the same file to both methods would often fail with the new method but succeed with the old method.

So for now I am sticking to the old implementation.

Just wanted to raise it in case it was not known already.

Thanks for the library though, its great!

@sskylar
Copy link

sskylar commented Apr 10, 2025

Noticed the same.

Using the older recognize_song I'm getting results, however with recognize I often get nothing but {'matches': [], ...}.

Attached is an example:
test.ogg.zip

result = await shazam.recognize('test.ogg')
print(result)

With this I just get an empty result {'matches': [], ...}.

Also worth noting the dora.ogg file in the examples seems to be returning an empty result for both recognize and recognize_song (Gloria.ogg is working).

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