Content on PitchDetector.com is created and maintained by the PitchDetector Editorial Team. This page explains who is responsible for what, how we research and verify guides, how tools are tested before release, how we use AI-assisted tools and how you can report an error.
Our topics range from beginner music theory to signal processing, so readers should be able to see how information is checked and how mistakes are corrected. The aim is not to make pages sound more authoritative than they are, but to make each one as accurate and useful as its subject requires.
Who Creates PitchDetector.com Content
The PitchDetector Editorial Team researches topics, writes and updates guides, documents the tools, checks factual claims and keeps pages consistent with each other. We do not present anonymous labels as proof of expertise, and we do not invent author personas or credentials. When a page receives specialist review from an identifiable contributor, that person and their role will be named on the page. More about the site itself is on About us.
Authors and Reviewers Have Different Roles
An author creates or substantially contributes to a page. A reviewer checks a specific area where extra subject knowledge matters. A how-to for a tool may need editorial and functional checks only, while a page on pitch-detection algorithms, acoustics or vocal health needs deeper source checking. Not every page needs specialist review, and we do not use “expert reviewed” as a label without saying who reviewed what.
How We Research
We use the most authoritative source available for each claim, in this order:
- original research and primary sources;
- official technical documentation and standards;
- established academic or professional organisations;
- reputable educational and reference works;
- high-quality secondary sources when primary material is not practical.
For browser technology that means official documentation; for algorithms, the original papers; for music theory, recognised reference material. AI output, search snippets, social posts and competitors’ marketing copy are not treated as evidence.
How We Verify Technical Claims
Small numbers matter on this site. Claims we check with particular care include:
- note frequencies and note names, calculated from the equal-temperament formula rather than copied;
- cents and tuning deviation;
- tuning references such as A4 = 440, 432 or 415 Hz;
- pitch-estimation methods and their limits;
- browser microphone behaviour and latency;
- harmonics and the fundamental frequency;
- vocal range figures and singer records, stated only when widely documented and phrased with care.
Where a claim concerns one of our tools, it is checked against the running tool, not against what the tool is supposed to do.
How Tools Are Tested Before Release
Tool pages must describe what the current tool actually does, including its inputs and outputs, supported files, tuning references, browser requirements, microphone use and known limitations. We do not claim a feature, algorithm or accuracy level simply because it is common elsewhere.
Every tool version is tested with generated audio whose correct answer is known: offline against the engine, then in a real browser with a simulated microphone, on desktop and phone-sized screens, with structured data validated. A version ships only when every check passes. We publish the measured results and the test conditions on our methodology page, and every release is recorded in the changelog. When a tool changes, its page is reviewed with it.
How We Handle Accuracy Claims
Pitch detection is an estimate. A steady note in a quiet room is much easier to measure than speech, chords, strong vibrato, background noise, distorted audio, overlapping instruments or a weak microphone. We therefore only publish accuracy figures that come from documented testing, and we say what was tested:
- the reference signal and the expected result;
- the observed result and the error;
- the test conditions, browser and input range;
- the test date and tool version;
- the known limitations.
We avoid “perfectly accurate”, “scientifically proven” and “professional-grade” as substitutes for evidence.
Music, Singing and Health
Our music-theory guides cover notes, scales, intervals, tuning, intonation, rhythm and ear training. Our singing guides cover pitch matching, vocal range and voice types, singing accuracy, warm-ups and practice routines. Both are written as music education.
They are not medical advice. Content about vocal technique should not be read as diagnosis or treatment, and pain, injury, persistent hoarseness or other voice problems belong with a qualified healthcare professional, not an online tool. Where a guide touches on vocal health, it says so and points to professional help.
Privacy and Security Claims
Statements about microphone access, audio processing and data must match the real implementation. Audio handling is documented on our data security page and broader website data on the privacy policy, and cookies and browser storage on the cookies policy, so none of them overstates the others.
How We Use AI-Assisted Tools
AI-assisted tools may help us organise research, plan structure, find questions worth answering, draft text and write test scripts. AI output is never treated as a source: calculations, tool behaviour, citations and factual statements are checked against real sources, the formula or the running tool before publication. Responsibility for everything on PitchDetector.com stays with the people who run it.
Our Update Policy
We update a page when there is a real reason to, for example:
- a change to one of our tools;
- new or better technical documentation;
- a corrected calculation;
- a change in browser behaviour;
- new research or evidence;
- broken or outdated references;
- an error reported by a reader;
- outdated screenshots or instructions.
We do not change dates just to make a page look fresh. A new review date means the page was actually reviewed.
Corrections Policy
Mistakes can still happen. To report one, email support@pitchdetector.com and include:
- the address of the page;
- the statement you believe is wrong;
- a short explanation;
- a source, screenshot or example if you have one.
You can also use our contact page. We check the report against the evidence and the current tool. If a correction is needed, we fix the page, and material changes get an updated review date or a correction note. Tool fixes also appear in the changelog.
Editorial Independence
The site shows no display ads. It earns commissions through affiliate links to the 30 Day Singer online course on our singing-lesson guides, such as the 30 Day Singer review: if you start a trial or subscription through one of those links, we may earn a commission at no extra cost to you. These links are marked as sponsored, and each page that has one carries a disclosure. Commissions never decide a tool’s output, our calculations, the limitations we document or our factual conclusions, and no one can pay for a place in our recommendations.
How We Choose Internal Links
We link to the page that answers your next question, not to raise a link count: technical readers to the methodology, readers with microphone problems to troubleshooting, new terms to the glossary, and broader topics to the Knowledge Hub. Every tool is listed on the tools page.
Accountability Matters More Than Labels
Where expertise is relevant, we prefer to show who contributed, what was reviewed, which sources were used, when the page was reviewed, where you can check the supporting information and how to report an error. Until identifiable specialist reviewers are added, content maintained together is credited to the PitchDetector Editorial Team rather than to invented people or unverifiable expert personas.
Contact the Editorial Team
Email support@pitchdetector.com or follow PitchDetector.com on Facebook. Related policies: disclaimer and accessibility.
Last reviewed: September 27, 2026.
