ScanSing: sheet music to MusicXML

What is in a recognised score: title, composer, key, time signature, tempo, duration, and per part its name, range (lowest/highest note), clefs and lyrics. key is the signature as printed; keyName and mode say major or minor as the engine reads it off the music (e.g. 'E minor'; mode null when it cannot tell). Cheaper than reading the MusicXML; nothing is recognised again.

A link to the score as a MIDI file (one track per part) to listen to or rehearse with; optionally one part and transposed. Repeats are played once.

A short-lived link to the score engraved as sheet music to print or view: a PDF of every page, or PNG pages. Works on any recognition: the original, one from label_notes (its names are engraved under the notes), and optionally one part, transposed or labelled on the way. The score is laid out anew from the MusicXML, not drawn over the scan. Nothing is recognised again, no pages are charged.

The MusicXML of one part (or a few) of a recognised score, e.g. the alto line of a choir piece. Part names are in describe_score.

Whether a part (default: the whole score) lies within a range, a singer's voice, an instrument's compass, a kalimba's tines, and how to make it: lowest/highest are its notes now, fits every transposition that puts them inside low…high, nearest first, with the key it lands in (empty: no shift fits). Pass a shift's semitones to transpose_score. Nothing is recognised again, no pages are charged.

A short-lived link to the MusicXML, MIDI or MP3 that opens without a key: give it to the user to open in a browser, MuseScore, Sibelius or a DAW. It lives as long as the recognition (about an hour). labels names each note in the MusicXML. An MP3 is the same MIDI rendered; it has no tempo of its own.

The MusicXML of an earlier recognition, a slice at a time (or saved to a local file). With labels, each note's name is written under it (see label_notes); no pages are charged.

Status and summary of an earlier recognition.

A one-off URL to upload a local file to and have it recognised, for when the file is on the user's machine and this server is remote. Run the returned command in a shell on that machine (with the file's path in place of FILE): it uploads the file, waits for the recognition (seconds to minutes) and prints its summary with id. Then use get_musicxml, describe_score etc. with that id. The URL works once, within 15 minutes; for another file ask for another link. Not for a file attached to the chat: pass that to recognize_sheet_music as attachment.

Pages this key has used and has left this month, and its plan. Shared keys (plan owner/shared) have no quota and report nulls.

The kind and page count of a file, without recognising it or charging pages. Use it to pick pages for a long PDF or to check the quota (get_usage) first. Calls the ScanSing API, see https://scansing.app/mcp/.

A new recognition whose MusicXML has each printed note's name written under it as a lyric line of its own, as method books print it for beginners: a chord is named top to bottom, sung words stay where they are. letters and solfege-fixed name the pitch; movable-do, degrees and kalimba count from the key's tonic. The returned id is the labelled result (use it with export_score for a printable PDF, extract_part, transpose_score…); the original labelledFrom stays as it was. Nothing is recognised again, no pages are charged.

Recognize a PDF or image of sheet music and return its MusicXML with a summary (pages, parts, measures, warnings). Give exactly one of url, attachment, file_base64 or path. A file on the user's own machine (a remote server cannot read it, and a PDF is too big for base64): use get_upload_link instead. Calls the ScanSing API, see https://scansing.app/mcp/.

The MusicXML moved to another key: by semitones (-2 = a tone down) or to a key (nearest direction; give both to choose the octave). Notes are respelled for the new key signature; chord symbols move too.