Rust implementation behaves differently to the depreciated recognize_song method

[tjosgood]

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]

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).

[sebibek]

my observations: can confirm that the success rate is even 0 w/ recognize (rust implementation), while there is one definitely using the good ol' recognize_song. Trust me, I sampled extensively 😸

My usage example (segment is typed as pydub.AudioSegment):

chunk_bytes = io.BytesIO()
segment.export(chunk_bytes, format="wav")
out = await shazam.recognize(chunk_bytes.getvalue(), proxy)

Looks like a bug in the rust implementation if you ask me! (it worked for me for >1 year)