You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2022. It is now read-only.
According to the README, echoprint-codegen's algorithm processes samples at 11025 Hz. I'm interested in using additional frequencies to increase match accuracy, decrease the length of the sample required, and possibly handle recordings that are more active in lower frequencies.
So... I'm curious about the choice of 11025 Hz. Is there anything fundamental to the algorithm that depends on this choice of frequency? Are there things about lower or higher frequencies that make them less attractive, in your experience? Are there any constants etc. in the code that I should make parameterizable to properly handle other frequencies?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
According to the README, echoprint-codegen's algorithm processes samples at 11025 Hz. I'm interested in using additional frequencies to increase match accuracy, decrease the length of the sample required, and possibly handle recordings that are more active in lower frequencies.
So... I'm curious about the choice of 11025 Hz. Is there anything fundamental to the algorithm that depends on this choice of frequency? Are there things about lower or higher frequencies that make them less attractive, in your experience? Are there any constants etc. in the code that I should make parameterizable to properly handle other frequencies?
The text was updated successfully, but these errors were encountered: