Platform modules
Built on MusicXML and Score JSON
Each feature page maps back to the same score project model rather than a separate one-off converter.
Module
MusicXML import/export
Connected to the score project workflow.
Module
MIDI import/export
Connected to the score project workflow.
Module
Score JSON snapshot
Connected to the score project workflow.
Module
OSMD preview
Connected to the score project workflow.
Real product example
One score, structured input and reusable output
Captured from a real MusicXML import and OSMD render in the local product. Captured 2026-07-15.
MIDI engraving is a structural draft and remains reviewable in the editor.
Workflow
How this path works
The public page leads into the authenticated app workflow when users are ready to process a score.
Import MusicXML, MXL, MIDI, or Score JSON
Each entry path creates a reusable score project with revisions, assets, and export history.
Normalize into Score JSON
Playback, Jianpu conversion, transposition, correction, and export all operate on the same structured model.
Export without lock-in
Download MusicXML, MIDI, Jianpu text, rendered files, audio, or a Score JSON snapshot for backup and migration.
Product detail
What to expect
Parser provenance
MIDI import is structural
FAQ
Questions about MusicXML converter and MIDI score tools
Practical limits and expected workflow for this score tool.
What input does MusicXML converter and MIDI score tools accept?
Each entry path creates a reusable score project with revisions, assets, and export history.
Can I edit the result after conversion?
Yes. Successful imports become Score JSON revisions that can be corrected, transposed, played, and exported from the score workspace.
What should I check before relying on the result?
Complex engraving from MIDI still needs human review and correction.
Related workflows
Continue with the same score project
These pages use the same MusicXML and Score JSON source instead of sending the score through disconnected converters.