Backbeat Forge Changelog
This is the changelog for Backbeat Forge. Our development philosophy is simple: we ship desktop software that solves a specific problem reliably.
We release new features when the industry outgrows the current workflow. We ship fixes when we break something. We adapt when the underlying platform changes, such as a new network stack, OS security policy, or protocol specification. This page documents those improvements, fixes, and adaptations.
We try to avoid pushing updates just to bump the version number. If the build you are using is stable and the changelog does not mention a fix or feature you care about, it is safe to skip the release.
The entries here prioritize changes that affect real use: installers, license activation, import and export behavior, offline work, report handoff, data-format compatibility, performance, and error handling.
If you are deciding whether to upgrade, start with the items that match your workflow and then install the newer build when the fix or feature matters. If you hit a regression, contact support with the current version, target version, operating system, and reproduction steps. To get the latest build, visit the download entry.
-
0.1.9 — 2026-08-10
- MIDI and PDF export now react immediately to a valid Professional license instead of reopening the license window with stale startup permissions.
- Advanced drum-score editing and groove-aware quantization use the same refreshed license state, keeping all paid workflows consistent.
- License refresh is now verified across the complete six-feature Professional toolset, including both export paths, while Community startup behavior remains unchanged.
-
0.1.8 — 2026-07-26
- The installed application imports an exact full mix, runs HTDemucs drum separation and transcription, and binds the resulting score and stems to that source.
- The desktop workbench keeps separation progress readable, lays out score and evidence panels more reliably, and packages the ONNX Runtime resources required by the HTDemucs path.
- Windows installer acceptance also observes analysis progress and model status before retaining the score and separated-stem evidence.
-
0.1.7 — 2026-07-22
- Direct installer builds keep website checkout, license-key import, and online activation; Store builds hide web checkout and use native purchase and account restore.
- A native Store purchase offer is exposed only when its add-on is explicitly marked as published; unpublished add-ons remain restorable for existing owners but cannot start a new purchase.
- After a successful native purchase, the desktop runtime refreshes the Store entitlement and returns the updated license state. This code path has not yet completed real-account Store transaction acceptance.
- Local drum separation restores bounded multi-core CPU inference, removing the fixed single-thread regression without re-enabling the high-memory ORT graph optimization.
-
0.1.6 — 2026-07-17
- Drum-stem separation now uses the dedicated HTDemucs FT drum model pipeline and reports distinct decode, model-verification, model-loading, inference, and finalization stages.
- Store-distributed builds now use native entitlement and restore flows, while direct Community Edition builds keep their existing local and online activation surface.
- Added product-owned App Store and Microsoft Store packaging metadata, including bundled ONNX Runtime resources for the macOS store build.
-
0.1.5 — 2026-07-11
- Added versioned
.bforgeprojects so edited drum notation, onset sensitivity, quantization, mixer settings, and workspace state can be saved and reopened without analysing the audio again. - Hardened project recovery and packaging with source fingerprints, missing-audio fallback, safe asynchronous saves, and verified bundled HTDemucs drum-separation resources.
- Exposed the three supported source paths directly in the command bar: full mix, isolated drum stem, and drum MIDI performance import.
- Kept project, source, transcription, playback, and mixer commands visible at the supported 1040 × 700 minimum window size.
- Prepared the first public Community Edition release for Windows and Linux with canonical packages, checksums, and a product-specific release handoff.
- Added versioned
-
0.1.0
- Added full-mix and isolated drum-stem inputs.
- Added local drum separation and signal-driven onset classification.
- Added editable five-line drum notation with a score surface that follows the application's Light or Dark theme, a floating stem mixer, and PDF and General MIDI export.
- Added Community, Professional, and Team licensing.
Release context
How to read Backbeat Forge release notes
Backbeat Forge is a local drum-transcription workbench for turning a full mix or isolated drum stem into readable, editable five-line drum notation with PDF and General MIDI delivery.
Use this page to decide whether a release changes the exact workflow you rely on. Installer fixes, activation fixes, export behavior, local file compatibility, and evidence/report output matter more than a version number by itself.
-
Workflow areas to watch
- Audio and drum-stem transcriptionAnalyze an isolated drum stem directly or separate drums from a full mix before detecting and classifying performed hits with visible confidence.
- Real five-line drum notationReview measures, percussion clef, normal and X noteheads, rests, stems, beams, accents, ghost notes, open hats, and kit-piece placement in an editable score.
- PDF and General MIDI deliveryExport the corrected current draft as a printable multi-page PDF drum chart or channel-10 General MIDI for a DAW or notation application.
-
Upgrade decision
Backbeat Forge updates should be evaluated against the local tasks the product is meant to protect. If your current build is stable, upgrade when the notes mention a feature, platform fix, or defect that affects your work.
- Drum detection
- Five-line score viewing
-
Related pages
Before installing a new Backbeat Forge build, confirm the current download, license path, and support channel so rollback or activation questions have the right product context.