ChoralRoot 0.26.1 is 0.26's firmware, built from source on GitHub and signed: the first ChoralRoot release that
GitHub builds from the tag's source in The Firmware Hub's shared build workflow and signs with a build attestation, so
anyone can check that a package is the one made from this source, and The Firmware Hub can show "Built from source on
GitHub" on ChoralRoot's card. Nothing else changes: the sound, the features and the way your settings, sounds,
loops and favorites are stored are 0.26's, and only the version line reads 0.26.1. 0.26.1 replaces 0.26 as the web
installer's default; updating is optional, and going back to 0.26 changes nothing.
Signed builds (new in 0.26.1)
- Built by GitHub, from the tag. The packages on this release were built on GitHub's own machines by The Firmware
Hub's shared workflow (zvenson/fm1-build), from the source of the tag
v0.26.1, and signed there: each package and app carries a build attestation that names the repository, the tag,
the commit and the build run. They are the same bytes as the maintainer's own build: the sha256s the web installer
checks were committed before the tag, and the release was published only after the signed packages matched them. - The same firmware as 0.26. The code is 0.26's; the version line is the one difference.
Checking a package
With the GitHub CLI:
gh attestation verify choralroot-0.26.1.fwsc --repo Quixotic7/ChoralRootFM1 \
--signer-workflow zvenson/fm1-build/.github/workflows/build.yml
It prints the tag, the commit and the build run; add --source-ref refs/tags/v0.26.1 to require this tag. The same
works for choralroot-0.26.1-1core.fwsc and the two apps. 0.26 and older releases have no attestation: their
sha256s are in SHA256SUMS and the installer's list.
Installing
- The web installer's default is 0.26.1: press Install. Options > Version reads
ChoralRoot 0.26.1. - From 0.26 nothing changes but the version line: your sounds, loops, favorites and settings are all there.
- From 0.25.1 or older this is 0.26's update: 0.26.md says what 0.26 brought (VA and FM6 chords on both
cores, the black background) and what changes from older versions. - A Single core package for FM-1s that have trouble with Dual Core: the web installer's Advanced > Hardware
fallback. Options > Version then readsChoralRoot 0.26.1 1-core.
Going back to 0.26
The installer offers 0.26 under Other versions. Nothing changes: 0.26 is the same firmware and stores everything as
0.26.1 does, so your settings, sounds, loops and favorites stay as they are. Only the version line reads 0.26 again,
and its packages carry no attestation.
ChoralRoot 0.26.1 for the M-VAVE FM-1 (identity FM-1_920).
Install from the browser at https://quixotic7.github.io/ChoralRootFM1/ (Chrome or Edge, the FM-1 connected by USB), or with the command-line installer: python3 tools/fm1_install.py choralroot-0.26.1.fwsc.
choralroot-0.26.1-1core.fwsc is the same firmware on one processor core, for an FM-1 that crashes or freezes with the standard package (the installer offers it under Advanced > Hardware fallback). Settings, sounds and loops stay when you switch between the two.
SHA256SUMS lists both packages and their apps. GitHub built and signed each from this tag's source (The Firmware Hub's shared workflow); check one with gh attestation verify choralroot-0.26.1.fwsc --repo Quixotic7/ChoralRootFM1 --signer-workflow zvenson/fm1-build/.github/workflows/build.yml. The package holds three JieLi AC79 SDK files (Apache-2.0); LICENSE, LICENSING.md and LICENSES.zip carry every licence. Installing firmware is at your own risk.
Full Changelog: v0.26...v0.26.1