Plugins

Since 1.0.0 battuta is a host: the editor proper — tiles, caret, selection, undoable commands, the score on disk — and, around it, features that attach through declared extension points. A plugin’s code is not even loaded until something it declared happens (a key you press, a view you open, a file type you import), so a plugin you never use costs nothing.

The Plugins tab

battuta menu → 🌣 shortcuts → plugins. Every plugin in this build is listed with a switch and a state:

State	Means
ready	on, code not loaded yet — it will load the first time you use it
active	on and running
off	you turned it off
failed	it could not be registered or started; the reason is shown

What “off” does

Turning a plugin off deactivates it immediately, without a reload:

its keys leave the shortcut editor and the on-screen keyboard;
its panels close and its menu and status-bar items disappear;
the document does not change — plugins keep nothing in your score except what commands wrote into the MEI, and those are ordinary undo steps.

The switch is remembered across restarts. If you had rebound one of its keys, the rebind comes back when you turn the plugin on again.

Plugins in this build

Plugin	Provides	Off removes
Folder view	The 📁 side panel: the scores in a folder you opened, sub-folders in place, open tabs marked and unsaved ones starred, click to open, ✎ or F2 to rename in place, + score and + folder to make new ones — and live file watching, which also announces a change to a score you have open. Desktop app only. See Folder view.	The 📁, the panel, and the watching. The folder it remembers is kept for when you turn it back on; your scores are untouched — the names you gave and the scores and folders you made stay, and nothing else was ever written.
Pitch reference	The 🎙 bottom panel: load a recording of the score and see its pitch traced over every measure and over the whole file, with the written notes on the same axis — where the take is sharp, flat, early or late; play the take, or the written notes through MIDI, from one playhead that follows the caret. Detected in the editor, nothing uploaded. See Pitch reference.	The 🎙, the panel and the traces; an analysis in progress stops. The alignment it remembers per score is kept for when you turn it back on; the score is untouched — it only ever reads.
PDF reference	The 📄 bottom panel: load a score’s PDF with its OMR annotation files and see each measure’s scan above its tile — matched by id, or in order — and the caret’s system in a strip that follows it; on a PDF — or page images — without annotation files, systems, measures and staves drawn by hand on a zoomable page, kept and exportable. Rendered in the editor, nothing uploaded. See PDF reference.	The 📄, the panel, the scans and the room above the measures. Nothing about your score changes — it only ever reads.
Format converters	Everything beyond MEI: MusicXML (plain and zipped), ABC, Plaine & Easie and Humdrum convert to MEI as they open, arriving as new unsaved tabs; export MIDI (written score), Humdrum kern and Plaine & Easie in the battuta menu. See Files.	Those extensions from the open dialog and those three export rows — the open dialog lists `.mei` alone. Verovio’s ~13 MB Humdrum build is never downloaded. Scores you already imported are ordinary MEI and are untouched.
Harmony lanes	Chord symbols above the staff and Roman numerals below, from the status bar’s lane box: type at the caret, tab completes, enter commits and advances. See Harmony and lyrics.	Both lanes and their rows in the lane box. The harmony already in your scores is untouched — it is ordinary MEI.
Lyrics lane	`l` at a note, or lyrics (verse 1, l) in the status bar’s lane box: type syllables under the staff, space/enter advances to the next note, `-` hyphenates a word across several. See Harmony and lyrics.	The key, the lane and its row in the lane box. Syllables already in your scores are untouched — they are ordinary MEI.
On-screen keyboard	The 🎹 panel: a two-octave piano, sticky alt/shift latches, the digit pad and one button per action, generated from your live bindings. See The on-screen keyboard.	The 🎹, the panel, and the “on-screen piano” MIDI input. Nothing else changes — the panel only runs the editor’s own actions.
Playback	The page-view transport row: play/pause, stop, the speed select, the MIDI box and its transpose, the progress bar and the readout — plus export playback MIDI in the battuta menu. See Playback.	The row (page view has none), the export entry, and any sound or MIDI port it had open. Tone.js and the 2 MB sampled piano are never fetched. Your score is untouched — playback only reads it.
Reflection cycle	`shift` + `r` on a block: the serial forms of the selection — inversion, retrograde, retrograde inversion, back to the original. See Arranging.	The key, its row in the shortcut editor, and its caption on the on-screen keyboard. Scores you edited with it are unchanged — the forms are ordinary notes.