01
Profile the upload
StaveWave checks file type, size, page structure, source quality, and likely recognition difficulty before the job starts.
How it works
From score scan to MusicXML with review evidence.
StaveWave is designed for editable output plus visible uncertainty. The workflow combines source checks, OMR candidates, validation, rendering comparison, and a confidence report.
02
Run recognition candidates
Multiple OMR routes read the page and produce candidate notation data so one engine does not silently decide the whole result.
03
Compare and review
Validation checks and rendering comparisons look for mismatched rhythm, pitch, layout, lyrics, and structural problems.
04
Export with evidence
The job page keeps review notes and warnings visible next to the MusicXML export so the review step is practical.
What checks are involved?
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.
Use the result carefully
MusicXML conversion is a starting point for editing. Use the warning states and review notes to decide where to compare the export against the original score.