From scan to editable score
Upload a score image or PDF. StaveWave reads the notation, builds MusicXML, then checks the result before export.
Scan to MusicXML
Scan sheet music and export editable MusicXML.
Upload scanned sheet music, convert it to MusicXML, and get a confidence report explaining the OMR, validation, and release-gate results.
Optimized for scan sheet music to MusicXML, scanned sheet music converter, image to MusicXML, sheet music scan app workflows with reviewable MusicXML output.
Scan to MusicXML benefits
Clear upload checks
StaveWave validates file type, size, and image quality signals so source problems are surfaced early instead of becoming confusing conversion output.
No hidden reduced path
Required checks must run for a verified export. If something blocks conversion, the job shows a real error state.
Processing stack
The recognition and validation layers behind each export.
StaveWave shows the recognition engines, specialist passes, validation checks, and quality gates involved so users can see what checked the score before trusting the MusicXML.
OMR engines
Recognition engines read the score and create MusicXML candidates.
Audiveris, homr, and oemer each try the notation independently. StaveWave compares their outputs and keeps disagreements visible instead of treating one reading as automatically correct.
Review checks
Review checks compare the source page with the rendered result.
Visual, corpus, and notation checks inspect weak spots, compare source evidence against rendered MusicXML, and flag suspicious measures or repair candidates.
Specialist checks
Specialist checks look for notation mistakes that matter in editing.
Focused passes review pitch, rhythm, text, structure, articulation, and style so the output is easier to clean up in Sibelius, Dorico, MuseScore, Finale, or another editor.
Quality gates
Release gates decide whether the export is ready or blocked.
Validation, consensus, visual comparison, audio checks, plausibility scoring, and audit evidence must run. If a required component fails, the job reports a blocking error.
Workflow
How StaveWave analyzes the upload.
Capture the score
Use a clean scan with sharp staff lines, readable symbols, and minimal skew.
Upload to StaveWave
Submit the scan and let StaveWave prepare pages, compare recognition candidates, and validate the MusicXML.
Review and export
Download MusicXML after checking the measures and warnings surfaced by the review report.
Questions
What to know before uploading.
These answers match the structured data search engines receive for this page.
What scan resolution works best?
300 DPI or higher produces reliable results for most printed scores. 600 DPI is useful for dense notation or small print. Scans below 200 DPI often lack the contrast needed for accurate staff and symbol detection, and the review report is more likely to flag measures as uncertain.
Can it read handwritten scores?
StaveWave is optimised for printed notation. Handwritten scores vary widely in legibility—some clean handwritten manuscripts process well, but irregular note heads, ambiguous accidentals, and non-standard spacing increase recognition errors. If handwriting is involved, review the report carefully before using the MusicXML.
How do I scan a bound book or collection?
Flatten the page as much as possible to reduce skew and shadow near the spine. For public beta, use an original PDF or a flat, high-resolution scan of the full page. StaveWave accepts multi-page PDFs up to the beta page limit, so you can combine individual page scans into one file before uploading.
What notation apps can use the output?
The exported MusicXML can be imported by any notation application that supports the standard, including Sibelius, Dorico, MuseScore, Finale, and similar editors.
Ready to convert