Partitur
Download

Changelog

What changed.

Newest first, in plain words. The same list is CHANGELOG.md in the source; releases also carry their notes on their download page.

Unreleased

  • Partitur's own GPUs are paused. Until every model they would run may be offered for credits, central takes no runs for them (jobs.partitur_rigs, off by default) and the app doesn't offer them or show credits. Rigs you connect to your account work as before, free.
  • Ready for the law, too. Terms of use, with the contact point and the way to report illegal content the Digital Services Act asks for; a privacy policy that now covers the app, accounts and Partitur central in full; the Impressum names the contact point. The app links both when you create an account and in Settings → About, and lists the licences of every library and font it includes.
  • Lyrics stay yours. Lyrics transcribed on a GPU run go only to whoever asked; they are a copy of the song's words and are no longer shared with everyone who has the same song.
  • Deleting an account takes everything. Its setlists, the names it gave songs and its feedback go with it, and the account download now carries setlists, feedback and rigs.
  • Every release carries its source code, the exact commit its installers were built from.
  • The website publishes itself, locked down. From main (and once a day, for new releases) it is built and uploaded to Cloudflare Pages, free; every page comes with strict security headers: scripts only from the site (each inline one by its hash), connections only to the site, GitHub and central, no framing, HSTS. The deployment guide adds how to keep central safe at home on the free plan (tunnel, firewall, rate limits, encrypted off-site backups).
  • Partitur has its address: getpartitur.com. The website's links, sitemap and sharing previews use it, the song search and the beta form talk to central at api.getpartitur.com, and central's example configuration (mail, passkeys, the website's origins), its Caddy and Cloudflare Tunnel files and the deployment guide are set up for it, DNS and mail records included.
  • No more freeze when the window goes behind (Windows). With the HUD on, Partitur's whole window stopped answering ("Not responding") as soon as another window came in front: the HUD's window was made where Windows can't finish making it. It, and the tray panel, are now made beside the window. A stuck Partitur also says so while it is stuck now, not only at the next start: a small question asks whether to restart it (you come back where you were, with your song) or keep waiting, and goes by itself if Partitur comes back. And the note after a crash could take the window down as it closed; it no longer can.
  • Why it froze. Every freeze and hang report now says what held Partitur up: the click or key just before it (by the button's name, never what you typed), what ran that long (a click's handler, a timer in the studio by its function, drawing a page, a studio call), how the window's process and the computer were while it hung (running code without a break, waiting, out of memory, busy with something else), and for the app's own main thread, the command it ran and where it was stuck. The report's summary ends with the most likely cause; "Why it was held up" in the report shows the rest. Settings counts a new report at once.
  • Freezes, caught and prevented. A window that stops answering is noticed after 20 s (on Linux sooner, when WebKit itself says its page isn't responding) and asks whether to reload, with the song coming back where it was; if it comes back by itself, its report says for how long. Shorter freezes are noted too, with what Partitur was doing, without asking anything. And a whole class of them is gone: everything that reads the disk, the registry or other programs (checking a file on a sleeping drive, the Explorer menu switch, ending the engine's setup) now runs beside the window instead of holding it up.

  • Back where you were after a crash. Partitur now reopens the song you had open, paused where it was, after it crashed, after the computer restarted under it, or after its window had to be reloaded; a note in the corner says what happened, with the report one click away, instead of a dialog at the start. The window is watched: one that stops answering for half a minute asks whether to reload it, and one whose web process crashes reloads by itself. A crash in native code now says which (a segmentation fault, an access violation), a stall of the app's main thread is reported, a restart of the computer no longer counts as a crash, and two crashes in a row right after starting make the next start a safe one (the HUD, MIDI and Link, the band room, hands-free and the media keys wait until you turn them back on). One page that breaks no longer takes the window with it. Only crashes that took Partitur down are mentioned, once; the same crash again is one report with a count, one already sent isn't sent again, and old reports go after two weeks.
  • Crash reports. When Partitur stops (an error in its code, a crash in the parts of the system it uses, or a window that can't draw), it keeps a report: where it happened and the last things it did, without song names, file paths or addresses. At the next start it shows the report and sends it with one click, or quietly every time if you choose that (Settings → Updates and about); beta testers are told it helps most. A page that breaks shows a way back instead of an empty window, Partitur now keeps a log you can open from Settings, and logging out no longer counts as a crash. Central groups the reports by what crashed for the people fixing it.
  • "Open in Partitur" in Windows 11's first menu. Right-click songs in File Explorer and Partitur sits with the other apps' commands, not under "Show more options", and opens the whole selection with one launch. It needs a signed build (a code-signing certificate in the release workflow, or a development certificate for your own computer); unsigned builds keep the classic item. Settings → On stage → HUD is calmer too: grouped, with a corner picker, and only the switch while it's off; every switch now also turns with a click on its name.
  • Settings and Account, one page at a time. Both now have a numbered index on the left, grouped (Everyday, Playing, This computer), where each entry shows its state in a few words ("Graphite · less motion", "Sharing, sync on", "2.4 left"), and one page open beside it instead of a dozen blocks side by side. "Find a setting" (or /) finds any setting by what it does, the command palette opens any page by name, the account overview's tiles open their page, and sharing and sync are in Account too. The open page is remembered.
  • Open with Partitur, done properly. Select ten songs and open them: the first opens, the others join the library and are analysed in the background. On Windows, Partitur now appears in Windows' Settings → Default apps, its own button opens that page on Partitur, audio files it opens get a score-page icon and their own type names, and "Open in Partitur" stays in the right-click menu however many files are selected. On Linux, "Open with" passes the file (it started the app without it before). On macOS, Partitur is offered for exactly the types it opens, Ogg, Opus, Matroska and WebM included. A song opened from the file manager on the first launch opens at once; the introduction waits. Every platform now covers AAC, CAF, MKA and WebM too.
  • DAW plugin (CLAP, VST3). The song's chords, sections, bars and beats follow the DAW's playhead, read from the analysis Partitur already made. It follows the song open in the app or any song from the library, maps the timeline by seconds (as recorded) or by beats (warped to the DAW's tempo), shows letters or Nashville numbers, transposes, and can play the chords as sample-accurate MIDI. Builds for Linux, macOS and Windows.
  • Song clock cards. A song's clock as a picture to share: square (1080 × 1080) for posts, or a story (1080 × 1920) with a key to reading it, on score paper or graphite, with the cover art as the record's label. Saved as a PNG or copied. The website makes the same cards.
  • Hands-free page turns. Turn your head (or open your mouth) and the page turns: the next section, the next song of a set, the next page of the score. A half-minute calibration learns your own turns. The camera's frames stay on the computer, and the camera is on only while page turns are.
  • The written score, aligned. Open a MusicXML, MXL or MIDI file next to the recording. Partitur lines it up with the recording bar by bar, the Score tab engraves it, and the bar playing lights up.
  • Chords for DJ software. rekordbox and Serato cues carry the chord, key changes and chord changes can become cues, Serato gets the key, and there is a Traktor export (NML) with the key and cues.
  • Shared setlists. A setlist shared with the band through Partitur central: a join code, who may edit, placeholders for songs a member doesn't have yet.
  • The band room. The song on the band's phones over the local network, with no app and no account. Two QR codes: one to read along (chords, words or a chart, in each phone's own instrument key and capo), one for a remote.
  • Nashville numbers wherever chords show, printable number charts, and a lyrics prompter in stage mode (words as they are sung, chords above them).
  • Send feedback from the app, with the diagnostics shown in full before they go, and a beta update channel next to the stable one.

  • Partitur central: beta sign-ups with double opt-in, feedback, shared setlists and the song clock gallery.
  • How to build, install and test the desktop app against a central (docs/test-install.md).

  • Website: a scene for every section, more music drawn from the demo song, and a song search; it tells one song's story from the first bar to the coda.
  • Partitur central: the website may search song names from the browser.

  • The website: a static site that shows Partitur and gets it installed: the installer for the visitor's computer first, install steps as the download starts.
  • Play along with other gear: Ableton Link, MIDI clock, MIDI controllers and pedals, and an OBS stream overlay.
  • Watch folders, Open with Partitur, dragging files out of the window, a translucent tray panel, and faster decoding.
  • Finding songs on Partitur central, comparing against any song, stage mode, gig sheets, collections, a practice log, and playing along with a score.
  • The HUD: small plates over games and other apps (chord, beat, section, song, run) with global keys, a chord lane and a stream look, transpose and capo, setlists, media keys, and faster starts.

  • Run the models on this computer: the app sets up its own analysis engine where the hardware allows it, and shows progress and time left everywhere.
  • Rigs people connect to their account, with live telemetry, pairing and job timings.
  • The window is the app's own, with a splash while it starts; a tray with its own themed panel; notifications with progress.
  • Faster starts and a smaller download; a measured performance report.

  • The desktop app for Windows, macOS and Linux (Tauri 2), with installers, auto-update, and the studio of the website inside it.
  • Partitur central: accounts (passwords, passkeys, Google), song knowledge shared by content key, libraries that sync, credits and GPU jobs.
  • The command line: login, logout, credits, submit and bundle; partitur fleet serves central's GPU queue from a rig.
  • Track identity: embedded tags, cleaned titles and cover art.
  • The analysis engine on a workstation: CUDA pins, sequential stages with model eviction, a single-GPU rig profile, an exact port of the All-In-One model's NATTEN operations.