Sera / Tazenqor

SERA / TAZENQOR

Your score.
Your intent.
Inspectable edits.

SeraEdit turns language-guided MusicXML editing into structured proposals, explicit checks and separately reviewable revisions.

Explore working examples Discuss an evaluation →

A published software record. An accepted paper.

Accepted in SoftwareX · 15 October 2026

SeraEdit: Scoped and Validated Language-Guided MusicXML Editing

Author
Yuan Gao / 高源
Journal
SoftwareX
Status
Accepted for publication

A research-software contribution on source-bound, scoped and validated MusicXML editing. The software archive below is a separate, citable research artifact; its DOI is not the journal article DOI.

R1 source & evidence ↗Source repository ↗

Acceptance date confirmed by the author. The final journal citation will be added after online publication.

From a request to a reviewed revision

  1. Describe the editSelect measures, staves or events and specify what must stay unchanged.
  2. Inspect the proposalReview a structured ScorePatch and the intended changes.
  3. Check the boundariesValidate score structure, protected content and the source version.
  4. Review the revisionMake the musical decision and inspect a separate MusicXML revision in a notation application.

A real editing interface

SeraEdit local-rule proposal view showing four pitch changes, validation and a protected scope.
Author-supplied screenshot, 3 October 2026. A local-rule transposition proposal on a synthetic score; click to inspect the full image.

Current capabilities

Scoped edits

Address a measure, staff, voice or event rather than rewriting the entire score.

Source-bound proposals

A source fingerprint identifies the score version a patch was prepared for.

Validation & rejection

Inspect structural checks and refusal reasons before accepting a revision.

MusicXML exchange

Use a separate revision with notation software. Compatibility depends on the score and host version.

Working with notation software

MusicXML is the exchange boundary. The documented MuseScore demonstration is a bounded integration example, not a partnership or compatibility certification. Sibelius integration is not represented as completed.

What to evaluate next

Bring a small set of permitted scores and editing tasks. We can discuss target-edit accuracy, changes outside the requested scope, preservation of constraints and the manual correction required.

Plan a technical conversation