How it works

What happens to your score.

StaveWave runs two paths on one standard. The reading path — sheet music OCR, or optical music recognition — turns a PDF, scan, or photo into verified MusicXML. The engraving path turns MusicXML into a print-ready, publisher-quality PDF. Here are both, told without the jargon: machines read, arithmetic checks, layout is computed, and you only judge the bars that actually need a musician. Everything runs in the browser — an online service with nothing to install, on Mac, Windows, Linux, iPad, or Chromebook.

01 · Arrival

We look before we read.

A born-digital PDF, a flatbed scan, and a phone photo of a music stand are three different problems. Before any reading happens, StaveWave profiles your upload — page structure, print quality, skew, resolution — and routes it through the preparation that source actually needs. Nothing is force-fed through one generic cleanup.

This is also where impossible jobs get caught early, before they waste your time.

PDFScanPhotoeach gets its own preparation

02 · Reading

Several readers, one draft.

One music-OCR engine will happily be confidently wrong. StaveWave runs independent recognizers over every page and compares their readings note by note. Where they agree, the draft is probably right. Where they disagree, that exact spot is flagged for the check — disagreement is treated as information, not noise.

The same idea proofreaders have used for centuries: two readers catch what one misses.

1♩ = quarter2♩ = quarter3♪ = eighth?two agree, one dissents → that bar gets flagged, not guessed

03 · Checking

Every bar gets checked — because music has math.

A 3/4 bar must hold exactly three beats. Ties must land somewhere. A bass clef under soprano notes is suspicious. StaveWave runs those checks on every measure, then renders its own draft and compares it against your scan. Each bar comes out graded red, yellow, or green before you ever look at it.

On a typical scan, most bars grade green and never need your attention at all.

3 beats ✓3 beats ✓4 in a 3/4 barodd clefrhythm has arithmetic — a 3/4 bar holding 4 beats cannot hide

04 · Your part

Review with a spotlight, not a haystack.

The score check is where the ten minutes of human judgment happen. Findings arrive grouped by cause — “41 bars overfull”, “12 tie mismatches” — one plain-language card per pattern. Selecting one spotlights the exact measure on your original page. Verified fixes apply in one tap, across the whole pattern if you like. You can edit notes right on the notation, and play any bar to hear the mistake before you squint at it.

Auto-playing sketch of the check. Drive it yourself →

05 · Done

Export with receipts.

The result is standard MusicXML that opens in Sibelius, Dorico, MuseScore, Finale — anything that imports MusicXML. It ships with its receipt: what was read, what was flagged, what was fixed and by whom. If you ever wonder why a note is what it is, the answer is attached to the file, not lost in a black box.

Nothing is quietly smoothed over. Bars you confirmed are marked as yours.

score.musicxmlRECEIPT41 bars corrected12 ties healed3 clefs confirmedaudit log attached

The engraving path

From MusicXML to a printed page.

Recognition gets the notes right; engraving makes them read like a published edition. The same service powers MusicXML to PDF conversion and professional sheet music engraving, whether your file comes from a StaveWave scan or straight out of your notation app.

06 · Layout

Engraving starts where recognition ends.

The second path runs in the other direction: MusicXML in, a published-looking page out. The file is parsed and validated bar by bar — the same rhythm arithmetic and structural checks the OMR path uses — and then a layout engine computes optical note spacing, system breaks, and page turns from the music itself. Dense passages get room to breathe; sparse ones tighten. Beam angles, stem directions, and accidental stacking follow the conventions of published editions, not a one-size-fits-all default.

You can bring MusicXML from Sibelius, Dorico, MuseScore, or Finale — or hand over the verified file from a StaveWave conversion in one click.

dense — gets roomsparse — tightensspacing is computed from the music, not from a fixed grid

07 · The edition

Collision-free, deterministic, print-ready.

Every lyric, dynamic, and articulation placement is checked against every other and resolved before a page is rendered — nothing is left for you to nudge apart. Rendering is deterministic and versioned: re-engrave the same MusicXML and you get an identical page, no silent layout drift between exports. Each job delivers the print-ready engraved PDF, compressed MusicXML for your notation app, and MIDI so you can hear exactly what is on the page.

Same file in, same page out — engraving quality is measured against published editions, not eyeballed.

score.mxlengraved PDFMusicXML (.mxl)MIDIone upload, three deliverables — always the same page from the same file

Use the result like a musician, not a believer

MusicXML conversion is a starting point for editing. The score check exists so you know exactly which bars to trust and which ones you confirmed yourself — use it before the downbeat, not after. And when the notes are verified, the engraver is one click away.

Convert a scoreEngrave MusicXMLTry the score check