Skip to content

Releases

Patchwerk 1.0.3

Choose a tag to compare

@MattKuebrich MattKuebrich released this 08 Nov 20:47
  • Everything on the web shows the screen the way the unit's panel does (the same look as the emulator with "Match the unit's panel" ticked):
    the module pictures, the screenshots in the README and the reference, the logo and the link preview, and the page's own brand colors,
    its mark and its tab icon. They are made through tools/panel_look.py (a port of the page's look); the firmware's palettes are as they were.
    tools/gen_shots.sh makes the screenshots from the host simulator (tests/scenarios/web_shots.txt, og_shots.txt).
  • The name is written Patchwerk (not all capitals) in the page, README, BUILDING.md, the reference, the cheatsheet and the unit's help text. The
    splash on the unit stays capitals (its large face has only those letters), and patch codes still start with PATCHWERK: so old ones load.
  • The README links to mattkuebrich.com/patchwerk and opens with the page's own description. The reference has pictures for groups, MUTES and
    MUTATE (web/shots/groups.png, mutes.png, mutate.png).
  • update.command (double-click, kept off GitHub): puts the newest patchwerk-v….zip from Downloads into the folder, keeping fmhub.json, then offers to publish.
  • "Match the unit's panel" is also under the emulator (one switch with the palette editor's).

Patchwerk 1.0.2

Choose a tag to compare

@MattKuebrich MattKuebrich released this 08 Nov 04:51
  • The screen shown while a sample (or anything else) is sent over USB is now a still (the five cables, no animation): transfers are
    so quick that the cables flickered. The sound's bank slot and name are still under them.
  • Shorter pad names on the preset banks (808 CHAT ... FM CRASH, BREAK).
  • README.md: the logo on top, and a line that the newer FM-1s (UC25HQ80 flash chip, JEDEC 0xB36014) work too.
  • docs/REFERENCE.md rewritten (shorter, every module with its picture, song, snapshots, metronome, palettes, sample banks).
  • RELEASING.md stays on your computer: publish.command no longer puts it on GitHub.
  • Removed unused files (docs/EXPERIMENTS.md, docs/REMOVED-PALETTES.txt, two unused screenshot scripts, tools/symsize.py, .gitmodules).

Patchwerk 1.0.1

Choose a tag to compare

@MattKuebrich MattKuebrich released this 07 Nov 20:23
  • New preset sample banks: A 808, B 909, C FM drums, D random (eight sounds each; the drum banks run kick, snare, clap, closed hat,
    open hat, tom, cowbell, crash, so pads 1-8 line up; the 808 has no crash and the 909 no cowbell, so their rimshot stands in).
    The web page's "808 + 909 to A+B" and "FM + Random to C+D" buttons load them; about 140 KB on the FM-1 once sent packed.
    The FM drums are from "hizmi - Hybrid Sample Pack 01" (credited on the page and in the README).
  • The screen shown while a sample (or anything else) is sent over USB is redrawn in the current style: the splash's five cables are
    patched in as the transfer goes, with the sound's bank slot and name under them.
  • The firmware file carries its version in the name (patchwerk-v1.0.1.fwsc) on the page, in the repo and on the release.
  • The page links to the GitHub repo (the top bar and the footer).

Patchwerk 1.0.0

Choose a tag to compare

@MattKuebrich MattKuebrich released this 07 Nov 14:15
  • README.md is now short (what it is, try it, install, use, build, credits; the old long text, without its stale intro, is docs/REFERENCE.md).
    fmhub.json, submission/SUBMISSION.md and BUILDING.md are brought up to date (85 modules, the GitHub and Pages links, publish.command).
  • The first release. Everything from the release candidates (rc1-rc208) is in it; the web page, the unit's help and the README describe it.
  • Help on the unit: the headings are a size up and light grey (the highlight color stays on the key names).
  • The release: tools/release.sh takes a version (tools/release.sh 1.0.1) as well as an rc number; the page build also writes index.html (what
    GitHub Pages serves; emulator.html is not committed, it is the same page). RELEASING.md has the steps for GitHub (the repo, Pages, the release, a new version), and publish.command (double-click on a Mac, needs
    the GitHub CLI: brew install gh, gh auth login) does them: builds, commits, pushes, turns on Pages, tags and makes the release.