About MusicalBoard
About MusicalBoard
MusicalBoard is a free, browser-based practice space centered on singers: live pitch feedback, vocal scales, a metronome, a reference keyboard, spectrum and dynamics views, and recording — together in one dashboard, without another app install or an account.
Why this project exists
Practicing vocals at home used to mean juggling a tuner, a metronome, a DAW or voice memos, and sometimes a piano plug-in — every switch breaks focus. I wanted a single tab I could open on a laptop or tablet, approve the microphone once, and move from humming warmups to checking intonation without hunting for the right program. Modern browsers are finally fast enough for responsive audio; WebAssembly and the Web Audio API make it realistic to keep analysis on your machine. MusicalBoard grew out of that constraint: a small toolkit that stays in the browser instead of asking you to install one more native app.
Who runs MusicalBoard
The site is built and maintained by an independent developer with a software background and a long habit of using these same exercises while practicing singing. This is not a conservatory, record label, or medical service — it is a focused technical side project meant to support lessons and self-directed practice. The tools show what your microphone hears; they do not replace a vocal coach, teacher, or hearing professional, and they are not a substitute for personalized instruction when you need it.
What you can do here today
Eleven practice tools cover the parts of a vocal warmup and review session that used to need separate apps:
Technology
MusicalBoard is written in Rust and compiled to WebAssembly with the Yew framework, using the Web Audio API for capture, playback, and the real-time analysis in each tool. Vocal isolation is the one exception that runs a model rather than plain signal processing — a pre-trained separation network through ONNX Runtime Web, fetched once and cached in the browser rather than called on a server. That is the whole reason your voice does not have to leave the tab: WebAssembly is close enough to native speed that pitch detection, spectrum analysis, and pitch correction can run per animation frame on the device you are already using.
How the tools and guides are maintained
MusicalBoard is maintained as one connected browser project, not as a collection of embedded widgets. A tool page describes the controls and measurements that are actually available on that page: what the browser measures, what is saved locally, and where a result stops being reliable. When a feature changes, its page and related guide are reviewed so that the explanation does not promise a workflow the tool cannot perform. The aim is a practical reference for a singer using their own microphone and headphones, not a substitute for a lesson, hearing assessment, calibrated acoustic measurement, or commercial production software.
If a result, instruction, or accessibility detail is unclear, please report the page, browser, device, and the steps that led to it. That makes it possible to reproduce the issue and correct either the tool or its documentation.
What this does not try to be
There is no account system, so there is no cross-device sync and nothing saved on a server to lose or recover — settings and takes live in this browser's local storage and IndexedDB, and clearing site data clears them. The tools report numbers (cents, dB, a readiness score), not verdicts about your voice or your technique; a teacher, coach, or clinician reads context this page cannot see. Vocal isolation and auto-tune are practice aids built from one open model and one DSP algorithm respectively — they are not a substitute for paid stem-separation or mastering software on anything you plan to release.
Frequently asked questions
Is MusicalBoard affiliated with a music school or a vocal-health clinic?
No. It is an independent side project. The numbers it reports (pitch, timing, level, spectrum) are informational, not medical or pedagogical advice, and do not replace a teacher, coach, or hearing professional.
Why does a tool not have a feature I expected, like a mobile app or saved cloud profiles?
The project is intentionally browser-only with local storage instead of accounts, so there is nothing to build or maintain on a server for your practice data. That keeps the tools free and keeps audio off our servers, at the cost of cross-device sync.
Can I suggest a new practice tool or report something that feels wrong?
Yes — that is what the Contact page is for. Specific, reproducible feedback (which tool, which browser, what you expected versus what happened) is the most useful kind and the most likely to lead to a fix.
Contact and policies
Thoughtful bug reports, accessibility feedback, and ideas for practice tools are welcome through the Contact page. For data use, advertising, and your rights, read the Privacy Policy and Terms of Use. For a direct question, email tooliverse0520@gmail.com.