Please put “BPMfinder” in the subject line and allow a few business days for a reply. This is a small independent project, not a support desk.
What to include
- For a tool question: the browser, the file format, and what you saw (the BPM or the error).
- For a guide correction: the page URL and the sentence you think is wrong.
- For a privacy request: the email you used and what you want changed or removed.
- For a broken link: the page you were on and the link that failed.
Do not send passwords, API keys, or private audio you do not want a stranger to hear.
Publisher
Justin Helmer · Canada. The site is part of the Excavationpro / LYGO workshop. Public updates are at @Excavationpro and the source projects are at github.com/DeepSeekOracle.
Support the project
Optional support through PayPal.me/ExcavationPro helps pay for hosting and time. It does not buy a ranking, a custom guide, or a guarantee of support.
Response times and limits
Most messages get a reply within a few business days. I cannot debug a specific DAW project, recover a lost session, or provide legal advice about a sample or a licence. I can answer questions about the tool, correct a factual error in a guide, and route a privacy request.
If you are reporting a BPM result that looks wrong, include the file format, the browser, the expected tempo, and the returned tempo. A short screen recording or a link to the file (only if you have the rights to share it) is more useful than a description.