A hardware-aware DAW for the Sega Mega Drive.
3 changes since v1.0.0.
Downloads
| platform | portable | installed |
|---|---|---|
| Windows x86-64 | mdd-1.0.1-windows-x86_64-portable.zip |
mdd-1.0.1-windows-x86_64-setup.exe |
| Linux x86-64 | mdd-1.0.1-linux-x86_64-portable.tar.gz |
mdd-1.0.1-linux-x86_64-installer.tar.gz |
| Linux arm64 | mdd-1.0.1-linux-arm64-portable.tar.gz |
mdd-1.0.1-linux-arm64-installer.tar.gz |
| macOS x86-64 | mdd-1.0.1-mac-x86_64-portable.tar.gz |
mdd-1.0.1-mac-x86_64.dmg |
| macOS arm64 | mdd-1.0.1-mac-arm64-portable.tar.gz |
mdd-1.0.1-mac-arm64.dmg |
A portable copy keeps its settings, projects and banks in a userdata folder beside the
executable, so it can live on a memory stick and leaves nothing behind. An installed copy
keeps them under your documents. Both are the same application, and the updater offers
whichever kind you already have.
Checking a download
SHA256SUMS lists every file, and each file has a .sigstore bundle beside it,
SHA256SUMS included. The signature is what proves a download came from this repository: a
checksum on its own only proves the file matches whichever list you read it from.
:::sh
sha256sum -c SHA256SUMS --ignore-missing
cosign verify-blob --bundle SHA256SUMS.sigstore \
--certificate-identity-regexp '^https://github.com/MeguminBOT/md-synth-daw/' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
SHA256SUMS
The same workflow records build provenance, which the GitHub CLI reads:
:::sh
gh attestation verify mdd-1.0.1-windows-x86_64-portable.zip --repo MeguminBOT/md-synth-daw
What changed
The application (1)
- Files The update handover starts detached, and an installed update runs silently
Window, audio and system (1)
- System A Windows release build opens no console, and joins the terminal it starts from
The repository (1)
- Bump version 1.0.1 (missed a crucial fix for updater logic)
Every commit: https://github.com/MeguminBOT/md-synth-daw/compare/v1.0.0...v1.0.1
