Skip to content

What’s new in scanned music import

How Flat for Education turns PDFs and photos of sheet music into editable scores: model versions, what is recognized, what got fixed.

The same engine powers Opuscan and the OMR API. This page lists the changes as they reach Flat for Education.

All changes

In September

24 smaller changes
7 August·Improved·

A new model version with support for implicit tuplets

A new version of our in-house model now powers every PDF and photo import, with a focus on how tuplets are printed on the page.

  • Implicit tuplets are now supported. Engravers usually print the small "3" or "6" over the first triplet or sextuplet of a passage only, and leave the groups that follow unmarked — the player is expected to carry the pattern on. Those unmarked groups are implicit tuplets: played as tuplets, with nothing printed to say so. They are very common in 19th-century editions, studies and variations. Scanning now reconstructs them from the rhythm of the bar, instead of dropping notes to make the bar fit its time signature.
  • Fewer tuplets invented out of thin air. The model used to mark ordinary beamed groups as triplets even when no number was printed above them, and those numbers showed up in your score. It now writes a tuplet only where one is actually printed on the page.

Also in August

16 smaller changes
24 July·Improved·

A new model version focused on notation fixes

An improved version of Flat's in-house model now powers every PDF and photo import, in particular:

  • Multi-voice passages with shared rests and invisible rests are now supported.
  • Barlines and repeat endings (voltas) are now placed correctly within measures.
  • Beams are recognised more reliably.
  • Time signatures drawn across several staves, as on orchestral scores, are now recognised.
  • Fixed some chord symbols that were exported to MusicXML with a non-standard chord type.
15 July·New·

Import a PDF or photos into an editable score, with a review step

Importing sheet music from a PDF or a photo has a new flow on the web app, built on Flat's in-house recognition engine. It replaces the previous PDF import for everyone.

  • Pick the pages you want. Upload a PDF or several photos, then keep only the pages that contain the music. Each page you keep uses one credit.
  • Follow the recognition as it runs. A progress bar shows where the scan is, page by page, and you can keep using Flat while it works.
  • Review before the score is built. When the engine is unsure about an instrument, it asks you to confirm the title and the instruments it detected, with the part names printed on the page shown next to each one. When every instrument is certain, this step is skipped.

Available in Flat and, for teachers and administrators, in Flat for Education. The new flow comes to the iOS app in the coming weeks.

10 July·New·

OMR is now available as a developer API

Flat's OMR engine is now available programmatically through the developer API. Send PDFs or photos, follow recognition progress, review the detected instruments, then import the result as an editable score in a Flat library or export MusicXML or MIDI. It's the same in-house model that powers PDF and photo import in the editor, now available at scale for your own apps and workflows.

The dedicated OMR API (v2.24.0) builds on the background PDF import added to score creation in v2.23.0: ask for task support when importing a file and poll the task until the score is ready. See the API changelog for the details of both releases.

Also in July

8 smaller changes
23 June·Improved·

Sharper page analysis for complex layouts

We've improved how scanning reads the layout of a page. Imports of PDFs and photos now produce cleaner, more accurate scores, especially on complex layouts:

  • Dense pages now split correctly. Pages with many short systems stacked on top of each other are no longer merged together - each system is detected separately.
  • Better on orchestral and large-ensemble scores. Multi-staff instruments such as piano and organ, and large scores with many staves, are recognised more reliably.
  • Wide, landscape, and booklet layouts. Landscape pages no longer clip the left edge (which could cut off clefs), and multi-page and booklet scans are handled correctly.
  • Fewer stray detections. Spurious elements near page footers and margins are no longer picked up as music.
15 June·Improved·

A more accurate model

Every PDF and photo import is now processed by Flat's own in-house model. This release is a major new version focused on transcription accuracy: musical correctness (the notes, rhythms, ties, and accidentals that determine whether a score is right) improves across every test set, with the largest gains in:

  • Dynamics: +39%
  • Fermatas, articulations, ties, accidentals: +30 to 37%
  • Note durations: +22%
  • Slurs, dotted notes, rests, staff and voice assignment: +14 to 20%

Text, dynamics, and layout placement are also more precise: lyrics, chord names, and dynamics attach more reliably to the correct notes, including on complex layouts such as piano grand staves and parts with clef changes.

1 June·New·

Our own AI model starts rolling out

We're rolling out Flat's own AI model for PDF and photo import, designed and trained in-house to replace the third-party engine used at launch. Owning the technology end to end lets us push accuracy further, broaden what we recognise, ship improvements far faster, and align results with Flat's own notation format so imports fit naturally into the rest of the product. This first release already reads much more of your music:

Broader notation coverage. Newly recognised:

  • Chord symbols, properly encoded with their musical meaning as editable chords, not just plain text
  • Measure repeats and rhythm slashes
  • Tempo and metronome markings (with BPM)

Lyrics and text in more languages. Lyrics, rehearsal marks, and other text are recognised in Latin-script languages by default, plus Japanese, Korean, and Chinese.

Truer to the original layout. Imports now follow the source score's layout much more closely, matching the number of measures per line, systems per page, and overall structure. This makes a real difference on large, complex scores such as orchestral works and multi-staff instruments like piano. It also supports more page formats, including landscape pages that weren't supported before.

Also in June

8 smaller changes

Looking for something older?

Older updates are written up on the Flat blog, release by release.