SyMusOMRcodename is the product of a long-running research program in end-to-end visual understanding that is general-purpose. Our primary engine applies that work to music: it interprets an entire page as a connected spatial and musical system, then writes a structured score locally on supported Apple devices.
End-to-endCompact modelPrivate by designOn-device
A simplified view: each training example contains a score image and its corresponding text sequence. Visual features, musical relationships, and sequence generation are learned jointly and implicitly by the architecture; no segmentation masks, bounding boxes, or other symbol-level image annotations are supplied.
How it works
One learned visual-to-music pipeline
During training, each example supplies only two things: a score image and its corresponding output sequence, written in a human-understandable grammar designed to map cleanly to MusicXML. No segmentation masks, bounding boxes, or symbol-level image annotations are provided.
Pixel imagethe only visual input
Visual encodingfeatures learned implicitly
Relationshipsstructure learned implicitly
Music decodingMusicXML-compatible grammar
Editable scorerendered and edited on device
First, the visual encoder learns what evidence is useful. It is never given pixel labels that identify staff lines, noteheads, stems, beams, rests, clefs, accidentals, or barlines. End-to-end sequence training teaches it to form useful visual features implicitly from the page.
Next, the architecture learns musical and spatial relationships. A dot can be a duration mark or visual noise; a curved mark can connect notes or belong to another symbol; and a notehead can participate in a chord, voice, beam group, and measure simultaneously. Those relationships are not supplied as a separate annotation layer - they emerge because the model must generate the correct music sequence.
Finally, the music decoder writes the corresponding grammar sequence. The sequence is human understandable and MusicXML compatible, and the app converts it into an editable score where pitches, durations, voices, staves, clefs, meters, and supported changes can be reviewed and corrected.
It “takes its time” for a reason
A dense page contains more relationships to resolve and more events to write. Runtime therefore tends to follow musical complexity - staff count, polyphony, symbol density, and layout changes - rather than a single fixed delay.
Research foundations
Relational memory and positional structure
SyMusOMR grows from approximately ten years of research and development in multimodal understanding, including more than five years focused on a general-purpose vision-language Transformer architecture.
Relational reasoning
Music notation is relational: the meaning of a mark depends on what surrounds it and how it connects to other marks. Relational recurrent neural-network research helped establish ways for memory representations to interact through attention.
Connect local evidence across a page
Represent multiple simultaneous relationships
Resolve ambiguity through context
Hierarchical position
Our PRISM research explores positional representations that remain useful beyond the lengths seen during training. In music, position is not only left-to-right: events also belong to staves, measures, voices, systems, and nested groups.
Relative rather than purely absolute structure
Multiple positional axes
Better support for long and dense sequences
The goal is not to bolt a music-specific parser onto a generic recognizer. It is to let one architecture learn how visual structure becomes musical structure.
10+
years of research and development behind the broader approach
5+
years developing the multimodal vision-language direction
1
compact, integrated engine from image understanding to score output
The year counts and architecture names are project-history descriptions supplied for this beta overview; technical publications will provide fuller implementation details.
Our philosophy
End-to-end, synthetic-first, and private by design
The engine is trained from programmatically paired score images and output sequences - not human-drawn segmentation masks, bounding boxes, or symbol-level labels. It is also designed to avoid collecting users' scores and to keep inference local whenever the supported device can perform it.
End-to-end learning
The learning signal is the final image-to-sequence correspondence. Visual features and musical relationships are learned implicitly, without masks, boxes, keypoints, or other human-annotated image labels.
Synthetic-first training
Score images and their exact grammar sequences are generated together from notation rules and rendering systems. The engine does not depend on a manually annotated score-image corpus or on private user uploads.
No score upload required
Recognition is designed to run locally on supported iPhone, iPad, and Mac hardware. A page need not be sent to a cloud recognition service.
Compact deployment
The model is engineered for practical on-device memory, compute, and energy budgets rather than cloud-scale general-purpose deployment.
Why synthetic data? Music notation has combinatorial structure. Programmatic generation produces both the image and its exact target sequence while varying clefs, keys, meters, voices, chords, tuplets, handwriting-like fonts, page geometry, perspective, blur, lighting, and noise. No human has to draw masks, boxes, or symbol labels for those examples. Creating and validating such annotations is time-consuming work that is often labor-intensive, tedious, repetitive, and underpaid.
Why end-to-end? The only learning target is the corresponding music sequence. Traditional OMR pipelines can fail cumulatively when an early staff-removal, segmentation, or symbol-classification mistake constrains every later stage. Here, useful features and relationships are learned together from the final image-to-sequence objective, allowing distant context to help when local evidence is uncertain.
Why on-device? Local inference gives the musician direct control over the source image and avoids making recognition contingent on registration, network access, or recurring cloud processing.
Privacy boundary for beta testers
The recognition workflow is designed so that score images can remain on the device. Testers should still follow the app's beta-reporting instructions before voluntarily attaching any diagnostic image to feedback.
How the approach differs
Adaptability over brittle rules
Because the model learns relationships and structured output jointly, improvements can generalize across notation, page layout, image quality, and device conditions instead of requiring one handcrafted fix per symbol.
Scene-level understanding
The model considers the page as a visual scene and document, not a bag of disconnected symbols. That enables it to use staff context, spacing, repetition, and neighboring measures to disambiguate marks.
A growing notation vocabulary
Future versions can learn additional notation types while preserving the same core architecture. The roadmap includes text, chord symbols, lyrics, tablature, dynamics, expressions, articulations, and special noteheads.
Robustness through variation
Training intentionally varies camera perspective, rotation, lighting, scanner artifacts, fonts, handwriting-like rendering, score density, and staff configuration so that the model learns the underlying relationships.
Musician-centered output
We do not label pixels: no segmentation masks, bounding boxes, or other human-annotated image labels are part of the training objective. The model goes directly from a page image to a human-readable, MusicXML-compatible sequence, which the app turns into a score that can be auditioned, edited, corrected, and exported.
Our long-term vision is an engine that becomes more versatile without giving up privacy, compactness, or a coherent end-to-end design.
Evaluation note. Internal testing includes public-domain scores from sources such as IMSLP, as well as controlled synthetic test sets. Performance varies with notation coverage, page quality, density, and whether a feature is inside the current beta vocabulary; testers should not interpret strong results on one score type as a guarantee for every score.
Representations in superposition
Many features, one shared representational space
The prism is a visual metaphor for a compact model separating and recombining overlapping evidence: appearance, musical identity, and position can share internal directions rather than occupying one dedicated unit each.
What “superposition” means here
In mechanistic-interpretability research, superposition describes a network representing more useful features than it has individually available dimensions, by placing partly overlapping features in shared directions. Sparse features can coexist efficiently, although overlap can also create interference that later computation must resolve.
In our image-and-positional computational framework, overlapping is intended in two related senses. Spatially overlapping evidence can arise when visual marks, staff geometry, and nested positional scopes occupy or influence the same region—for example, a notehead may simultaneously belong to a chord, voice, measure, staff, and system. Probabilistically overlapping evidence means that a continuous internal state can retain weighted support for several candidate features, relations, positions, or continuations before later computation resolves them into a discrete music sequence.
The continuous-reasoning work below provides a related computational perspective: continuously valued chain-of-thought states can track multiple candidate traces in parallel rather than committing immediately to a single discrete path.
Interpretive note: this is a conceptual lens for understanding distributed representations, not a claim that either cited work directly establishes the internal mechanism of SyMusOMR. Spatial overlap, probabilistic overlap, and feature superposition are related but not interchangeable ideas; determining the model’s actual feature geometry requires dedicated mechanistic analysis.
Technical report forthcoming
A fuller technical report is in preparation and will partially describe the architecture, positional framework, image-to-sequence objective, and the intended relationship among spatial, probabilistic, and representational overlap. Once released, that report should replace this beta insert as the primary technical citation.
Suggested interim citation:
Symphony Pro Research (symphonypro.net), SyMusOMR Project. “Many Features, One Shared Representational Space: Superposition in Image and Positional Representations.” In How the MusicOMR Engine Works, beta documentation insert, revision 2026-07-30.
References and terminology
Further reading
The sources below motivate parts of the research direction. “SyMusOMR,” “Prismatic,” and “PRISM” are project or research codenames in this overview and do not imply that every mechanism in the cited work is reproduced unchanged in the beta engine.
1
Relational recurrent neural networks
Adam Santoro et al., 2018. Introduces a Relational Memory Core using multi-head dot-product attention so memory slots can interact during sequential reasoning.
Position as Probability: Self-Supervised Transformers that Think Past Their Training for Length Extrapolation
Philip Heejun Lee, 2025. Introduces PRISM, a probabilistic relative-position mechanism designed for length extrapolation beyond the training horizon. We apply the architecture to the problem of generalizating logical and algorithmic rules by learning end-to-end from observations.
Nelson Elhage et al., 2022. Uses small synthetic models to study how sparse features can be represented in overlapping directions when feature count exceeds representational dimension.
Continuous Chain of Thought Enables Parallel Exploration and Reasoning
Halil Alperen Gozeten, M. Emrullah Ildiz, Xuechen Zhang, Hrayr Harutyunyan, Ankit Singh Rawat, and Samet Oymak, 2025. Studies continuously valued chain-of-thought states that can track multiple reasoning traces in parallel, with the attainable parallelism linked to embedding capacity.
This overview describes the philosophy and user-visible behavior at a high level. It omits proprietary implementation details and should not be treated as a complete scientific specification or benchmark report.