load on the processor.

[masksshow]

Hi. Great project.
You can tell why recognition is causing such a heavy load on the processor.
I am sending a file of 500 kb, this is enough for the detection, but the CPU load is huge at the moment of recognition.
Can the load be reduced? Does it depend on the file format for recognition?
Thanks!

[dotX12]

I know about this, but there is no way to get rid of it, the only solution is to transfer the task of searching for a song by file to a separate processor so as not to block the code. This is a difficult task of converting files, changing hertz patterns and searching for a signature in the shazam base.

[masksshow]

Thanks.

Is there a way to reduce the load?
Can you explain why get_next_signature is needed?

I remember that in older versions of api shazam, it was necessary to send only RAW file data 44100Hz, 1 channel (Mono), signed 16 bit PCM. No re-encoding.
Thanks a lot!

[dotX12]

Thanks.

Is there a way to reduce the load?
Can you explain why get_next_signature is needed?

I remember that in older versions of api shazam, it was necessary to send only RAW file data 44100Hz, 1 channel (Mono), signed 16 bit PCM. No re-encoding.
Thanks a lot!

Thanks, I'll check it out over the weekend.

[dotX12]

@masksshow,
Unfortunately, I don't have much time to check it myself.
If you have the time and opportunities, check it out and do a PR.

[dotX12]

• Speedup peak spreading #32 - Partial solution to the problem.

[dotX12]

#78

[dotX12]

Closed, problem fixed.
#76 (comment)