DawIt starts with a person’s ideas about making music and learning it. AI helps write the code. Audio tools, local models and checks turn those ideas into something you can hear.
Here’s who does what, what runs on your computer, and the open building blocks behind it.
Ask a musical question.
What would help someone understand?
02
Build something to try.
Code, controls and a first explanation.
03
Check what it does.
Measure the sound. Look at the result.
04
Make the lesson clear.
Words, pictures and an example to hear.
The explanation is part of the instrument.
The decisions and the doing
A person sets the direction. AI helps with the building.
What should DawIt teach? Which tool would make an idea easier to hear? How should it explain that to a beginner? Those are human decisions.
01 / HUMAN DIRECTION
The idea, the taste, the decisions.
A person chooses the features, their order and the way each guide explains its subject. They review what comes back, try it and ask for changes when it needs work.
The aim stays the same: help you make music and understand your choices.
02 / AI-ASSISTED DEVELOPMENT
The code, the tests, the first drafts.
Claude Code and OpenAI’s Codex help write and revise the app, its tests, its theory text and this website. A person reviews the work and decides what belongs.
AI-written code is checked with the same sound measurements and app reviews described below.
Two different uses of AI.
The tools used to build DawIt are separate from its optional musical tools. You can explore guides, write notes and use the built-in effects without running a language model.
C++20 and JUCE provide the desktop app, audio, MIDI and plugin hosting.
DawIt’s effects and synthesisers use signal processing to make and shape sound. The theory guides and live pictures help explain what those tools are doing.
The song holds the tracks, clips, key, chords, words and sections.
↓
THE AUDIO TOOLS
Play it. Shape it. Hear it.
Instruments, effects, buses and sends turn the parts into the mix.
↓
THE EXPLANATION
See what changed.
Meters, pictures and guide topics read the song or settings as you work.
Optional AI inside the app
Your computer does the listening.
Different jobs use different models. DawIt runs these tools locally. Some models are included; others download when you choose to use them. Model downloads need a connection.
ONNX Runtime runs the voice’s models. English only. No voice comes with DawIt; each voice and vocoder has terms from its maker.
BRING YOUR OWN VOICE
Music processing stays on your computer. Ollama connects to your own machine by default; its server address is configurable.
Checks for a music app
Don’t just read the code. Measure the sound.
The test suite checks things you can hear: levels, pitches, harmonics, timing and decay. The interface and explanations need their own review too.
01 / THE SOUND
Put a known signal in.
Tests feed notes and audio through the tools, then measure what comes out. That checks whether a filter, compressor, synth or reverb behaves as expected.
02 / THE APP
Look at it in use.
The project’s review workflow opens windows and guides in DawIt and inspects app screenshots for layout, text and the right state.
03 / THE LESSON
Check the explanation.
Theory sources are recorded with the project. Numbers in explanations are checked against tests, standards or established references.
Credits & technical details
Good building blocks. Credit where it’s due.
Open a group for the tools, libraries and models behind DawIt, including their recorded versions, makers and licences.
App, audio & music notationThe language, framework, plugins and music font.+
The whole app: the windows and controls, audio and MIDI, plugin hosting, files, JSON and HTTP, on macOS, Windows and Linux. DawIt Tune finds a voice's pitch with McLeod's method and moves it with PSOLA, plain DSP on JUCE's own FFT, so it needs no library of its own.
Steinberg · SIL Open Font License 1.1 · pinned commit
The music font that draws clefs, rests, flags and note heads in the score view and its PDF. It is the reference font of the SMuFL standard, downloaded at a pinned commit and checked by its hash. Its licence text comes with the app.
Carnegie Mellon University · free for any use, with its origin named · 3.6 MB
How an English word sounds, with about 135,000 entries for about 126,000 words. It is built into the app, for Sing this and for finding rhymes and counting syllables in the lyrics window.
The format that singing voices are exported in. DawIt links none of its code: it runs a voice's ONNX models with ONNX Runtime, for Sing this. No voice comes with DawIt. You add one yourself, and each voice (and its vocoder) has its own terms.
An open-source editor for singing voices. DawIt follows it as the reference for how a voice is laid out and in what order its models are called. No OpenUtau code is used.
CMake configures the app and tests; Ninja builds them. Versions are recorded in the build configuration, with checksums for the downloaded source archives and models that specify them.
Keeps the history of every change, each with a sentence on what it does.
A note on licences.
JUCE 8.0.9 is offered under AGPLv3 or a commercial licence. DawIt’s plugin builds use the bundled VST3 SDK under GPLv3; the Bravura music font uses the SIL Open Font License 1.1. Models, voices and vocoders retain their makers’ terms.
For the available way to build and run the app, see Get started.
And this website?
Plain pages. The real app.
Static HTML, one shared stylesheet and a small script for navigation, search and colour themes. System fonts keep the pages self-contained. The images show DawIt itself.
There are no website accounts or analytics. ChatGPT created the book-and-levels logo; the app screenshots come from DawIt.