Skip to content

Releases: linuxificator/LB_Omnichord

R20260916T110435-SC

Choose a tag to compare

LB Omnichord SuperCollider edition for Linux x86_64, Raspberry Pi aarch64, macOS arm64 and Windows x86_64. The verified VSCO 2 CE sample repository is installed on first launch. Android is not part of this release.

R20260915T234344-SC

Choose a tag to compare

LB Omnichord SuperCollider edition for Linux x86_64, Raspberry Pi aarch64, macOS arm64 and Windows x86_64. The verified VSCO 2 CE sample repository is installed on first launch. Android is not part of this release.

R20260915T180639-SC

Choose a tag to compare

LB Omnichord SuperCollider edition for Linux x86_64, Raspberry Pi aarch64, macOS arm64 and Windows x86_64. The verified VSCO 2 CE sample repository is installed on first launch. Android is not part of this release.

R20260915T162801-SC

Choose a tag to compare

LB Omnichord SuperCollider edition for Linux x86_64, Raspberry Pi aarch64, macOS arm64 and Windows x86_64. The verified VSCO 2 CE sample repository is installed on first launch. Android is not part of this release.

R20260914T180649-SC

Choose a tag to compare

LB Omnichord SuperCollider edition for Linux x86_64, Raspberry Pi aarch64, macOS arm64 and Windows x86_64. The verified VSCO 2 CE sample repository is installed on first launch. Android is not part of this release.

R20260913T004923

Choose a tag to compare

@github-actions github-actions released this 13 Sep 01:04

Linux x64

Download LB_Omnichord.R20260913004923.Linux-x86_64.AppImage and its SHA-256 file.

Raspberry Pi 4 / 5 (64-bit Raspberry Pi OS)

Download LB_Omnichord.R20260913004923.RaspberryPi-aarch64.AppImage and its SHA-256 file. This Pi 4 baseline also runs on Pi 5.
For reliable audio under load, also download LB_Omnichord.R20260913004923.Pi4-Pi5-realtime-setup.sh and its SHA-256 file. Verify the checksum, run the script with sudo, and reboot when requested. The application warns at startup when this tested profile is incomplete.

macOS Apple Silicon

Download LB_Omnichord.R20260913004923.macOS-arm64.dmg and its SHA-256 file. This build is ad-hoc signed, but it is not signed with an Apple Developer ID and is not Apple-notarized. macOS therefore blocks the first normal launch by default.

Installation:

  1. Open the DMG, drag LB_Omnichord.app to Applications, then eject the DMG.
  2. Open Applications in Finder and double-click LB_Omnichord. macOS shows a warning and blocks this first launch; dismiss the warning.
  3. Open the Apple menu, choose System Settings, select Privacy & Security in the sidebar, and scroll down to Security.
  4. Find the message about LB_Omnichord and click Open Anyway. This button is available for about one hour after the blocked launch attempt.
  5. Enter your Mac login password or use Touch ID if macOS asks for confirmation.
  6. When the warning appears again, click Open. macOS saves an exception for this app, so later launches work normally.

This app-specific exception is sufficient; do not disable Gatekeeper or globally weaken Allow applications downloaded from.

Apple: Open a Mac app from an unknown developer

Windows native (experimental)

Download LB_Omnichord.R20260913004923.Windows-x86_64.zip and its SHA-256 file, extract the complete zip, then double-click LB_Omnichord.cmd. Do not use Explorer's Run with PowerShell on the internal run_windows.ps1: the double-click launcher supplies a process-only execution-policy bypass and keeps startup errors visible.

The portable directory contains separate native AMY and Qt frontend executables; it is not a single executable and the extracted files must stay together. Native Windows pointer hardware, audio and MIDI still need physical validation.

Android arm64 (experimental)

Download LB_Omnichord.R20260913004923.Android-arm64.apk and its SHA-256 file, allow installation from this source when Android asks, then install the APK. The package contains a PySide6 frontend and a separate private AMY/Oboe service process communicating through the app-private amy.sock.

This package is CI debug-signed so it can be installed and emulator-tested without a repository signing secret. It is not a Play Store bundle or a stable update channel, and physical touchscreen, speaker, route-change and latency validation is still required.

ESP32-P4 firmware (v1.x and v3.x silicon)

Download LB_Omnichord.R20260913T004923.ESP32P4.zip and its SHA-256 file. It expands to a versioned directory containing separate v1/ and v3/ image directories, flashing instructions, and Python flashers for both legacy and current esptool syntax. Use v1 for revision 1.x silicon, including the physically tested v1.3 board; use v3 only for revision 3.x silicon.

Both firmware profiles receive native AMY wire commands through the LP UART at 1,000,000 baud, include Gamma9001, 11 buses, capacity for 1280 reusable-sequence tags, and the physically selected 48 kHz / 128-sample / 2 x 128-frame audio geometry. CI proves compilation and image structure; v3 I2S audio and LP-UART operation still require physical-board validation.

Build provenance

AMY fork release: releases/amy_omnichord_R20260909T140940 at immutable build commit 5e3cd575fc744b9a0cd3e9014030acc7bf4dc5c2.

Each application package has signed GitHub build-provenance and SPDX 2.3 SBOM attestations. The ESP32-P4 firmware and Raspberry Pi realtime setup script each have a separate signed build-provenance attestation. Download an asset and verify it with gh attestation verify ASSET --repo linuxificator/LB_Omnichord; add --predicate-type https://spdx.dev/Document/v2.3 for an application package to verify and inspect its SBOM attestation.

R20260910T235231

Choose a tag to compare

@github-actions github-actions released this 11 Sep 00:07

Linux x64

Download LB_Omnichord.R20260910235231.Linux-x86_64.AppImage and its SHA-256 file.

Raspberry Pi 4 / 5 (64-bit Raspberry Pi OS)

Download LB_Omnichord.R20260910235231.RaspberryPi-aarch64.AppImage and its SHA-256 file. This Pi 4 baseline also runs on Pi 5.
For reliable audio under load, also download LB_Omnichord.R20260910235231.Pi4-Pi5-realtime-setup.sh and its SHA-256 file. Verify the checksum, run the script with sudo, and reboot when requested. The application warns at startup when this tested profile is incomplete.

macOS Apple Silicon

Download LB_Omnichord.R20260910235231.macOS-arm64.dmg and its SHA-256 file. This build is ad-hoc signed, but it is not signed with an Apple Developer ID and is not Apple-notarized. macOS therefore blocks the first normal launch by default.

Installation:

  1. Open the DMG, drag LB_Omnichord.app to Applications, then eject the DMG.
  2. Open Applications in Finder and double-click LB_Omnichord. macOS shows a warning and blocks this first launch; dismiss the warning.
  3. Open the Apple menu, choose System Settings, select Privacy & Security in the sidebar, and scroll down to Security.
  4. Find the message about LB_Omnichord and click Open Anyway. This button is available for about one hour after the blocked launch attempt.
  5. Enter your Mac login password or use Touch ID if macOS asks for confirmation.
  6. When the warning appears again, click Open. macOS saves an exception for this app, so later launches work normally.

This app-specific exception is sufficient; do not disable Gatekeeper or globally weaken Allow applications downloaded from.

Apple: Open a Mac app from an unknown developer

Windows native (experimental)

Download LB_Omnichord.R20260910235231.Windows-x86_64.zip and its SHA-256 file, extract the complete zip, then double-click LB_Omnichord.cmd. Do not use Explorer's Run with PowerShell on the internal run_windows.ps1: the double-click launcher supplies a process-only execution-policy bypass and keeps startup errors visible.

The portable directory contains separate native AMY and Qt frontend executables; it is not a single executable and the extracted files must stay together. Native Windows pointer hardware, audio and MIDI still need physical validation.

Android arm64 (experimental)

Download LB_Omnichord.R20260910235231.Android-arm64.apk and its SHA-256 file, allow installation from this source when Android asks, then install the APK. The package contains a PySide6 frontend and a separate private AMY/Oboe service process communicating through the app-private amy.sock.

This package is CI debug-signed so it can be installed and emulator-tested without a repository signing secret. It is not a Play Store bundle or a stable update channel, and physical touchscreen, speaker, route-change and latency validation is still required.

ESP32-P4 firmware (v1.x and v3.x silicon)

Download LB_Omnichord.R20260910T235231.ESP32P4.zip and its SHA-256 file. It expands to a versioned directory containing separate v1/ and v3/ image directories, flashing instructions, and Python flashers for both legacy and current esptool syntax. Use v1 for revision 1.x silicon, including the physically tested v1.3 board; use v3 only for revision 3.x silicon.

Both firmware profiles receive native AMY wire commands through the LP UART at 1,000,000 baud, include Gamma9001, 11 buses, capacity for 1280 reusable-sequence tags, and the physically selected 48 kHz / 128-sample / 2 x 128-frame audio geometry. CI proves compilation and image structure; v3 I2S audio and LP-UART operation still require physical-board validation.

Build provenance

AMY fork release: releases/amy_omnichord_R20260909T140940 at immutable build commit 5e3cd575fc744b9a0cd3e9014030acc7bf4dc5c2.

Each application package has signed GitHub build-provenance and SPDX 2.3 SBOM attestations. The ESP32-P4 firmware and Raspberry Pi realtime setup script each have a separate signed build-provenance attestation. Download an asset and verify it with gh attestation verify ASSET --repo linuxificator/LB_Omnichord; add --predicate-type https://spdx.dev/Document/v2.3 for an application package to verify and inspect its SBOM attestation.

R20260910T191823

Choose a tag to compare

@github-actions github-actions released this 10 Sep 19:36

Linux x64

Download LB_Omnichord.R20260910191823.Linux-x86_64.AppImage and its SHA-256 file.

Raspberry Pi 4 / 5 (64-bit Raspberry Pi OS)

Download LB_Omnichord.R20260910191823.RaspberryPi-aarch64.AppImage and its SHA-256 file. This Pi 4 baseline also runs on Pi 5.
For reliable audio under load, also download LB_Omnichord.R20260910191823.Pi4-Pi5-realtime-setup.sh and its SHA-256 file. Verify the checksum, run the script with sudo, and reboot when requested. The application warns at startup when this tested profile is incomplete.

macOS Apple Silicon

Download LB_Omnichord.R20260910191823.macOS-arm64.dmg and its SHA-256 file. This build is ad-hoc signed, but it is not signed with an Apple Developer ID and is not Apple-notarized. macOS therefore blocks the first normal launch by default.

Installation:

  1. Open the DMG, drag LB_Omnichord.app to Applications, then eject the DMG.
  2. Open Applications in Finder and double-click LB_Omnichord. macOS shows a warning and blocks this first launch; dismiss the warning.
  3. Open the Apple menu, choose System Settings, select Privacy & Security in the sidebar, and scroll down to Security.
  4. Find the message about LB_Omnichord and click Open Anyway. This button is available for about one hour after the blocked launch attempt.
  5. Enter your Mac login password or use Touch ID if macOS asks for confirmation.
  6. When the warning appears again, click Open. macOS saves an exception for this app, so later launches work normally.

This app-specific exception is sufficient; do not disable Gatekeeper or globally weaken Allow applications downloaded from.

Apple: Open a Mac app from an unknown developer

Windows native (experimental)

Download LB_Omnichord.R20260910191823.Windows-x86_64.zip and its SHA-256 file, extract the complete zip, then double-click LB_Omnichord.cmd. Do not use Explorer's Run with PowerShell on the internal run_windows.ps1: the double-click launcher supplies a process-only execution-policy bypass and keeps startup errors visible.

The portable directory contains separate native AMY and Qt frontend executables; it is not a single executable and the extracted files must stay together. Native Windows pointer hardware, audio and MIDI still need physical validation.

Android arm64 (experimental)

Download LB_Omnichord.R20260910191823.Android-arm64.apk and its SHA-256 file, allow installation from this source when Android asks, then install the APK. The package contains a PySide6 frontend and a separate private AMY/Oboe service process communicating through the app-private amy.sock.

This package is CI debug-signed so it can be installed and emulator-tested without a repository signing secret. It is not a Play Store bundle or a stable update channel, and physical touchscreen, speaker, route-change and latency validation is still required.

ESP32-P4 firmware (v1.x and v3.x silicon)

Download LB_Omnichord.R20260910T191823.ESP32P4.zip and its SHA-256 file. It expands to a versioned directory containing separate v1/ and v3/ image directories, flashing instructions, and Python flashers for both legacy and current esptool syntax. Use v1 for revision 1.x silicon, including the physically tested v1.3 board; use v3 only for revision 3.x silicon.

Both firmware profiles receive native AMY wire commands through the LP UART at 1,000,000 baud, include Gamma9001, 11 buses, capacity for 1280 reusable-sequence tags, and the physically selected 48 kHz / 128-sample / 2 x 128-frame audio geometry. CI proves compilation and image structure; v3 I2S audio and LP-UART operation still require physical-board validation.

Build provenance

AMY fork release: releases/amy_omnichord_R20260909T140940 at immutable build commit 5e3cd575fc744b9a0cd3e9014030acc7bf4dc5c2.

Each application package has signed GitHub build-provenance and SPDX 2.3 SBOM attestations. The ESP32-P4 firmware and Raspberry Pi realtime setup script each have a separate signed build-provenance attestation. Download an asset and verify it with gh attestation verify ASSET --repo linuxificator/LB_Omnichord; add --predicate-type https://spdx.dev/Document/v2.3 for an application package to verify and inspect its SBOM attestation.

R20260909T185035

Choose a tag to compare

@github-actions github-actions released this 09 Sep 19:12

Linux x64

Download LB_Omnichord.R20260909185035.Linux-x86_64.AppImage and its SHA-256 file.

Raspberry Pi 4 / 5 (64-bit Raspberry Pi OS)

Download LB_Omnichord.R20260909185035.RaspberryPi-aarch64.AppImage and its SHA-256 file. This Pi 4 baseline also runs on Pi 5.
For reliable audio under load, also download LB_Omnichord.R20260909185035.Pi4-Pi5-realtime-setup.sh and its SHA-256 file. Verify the checksum, run the script with sudo, and reboot when requested. The application warns at startup when this tested profile is incomplete.

macOS Apple Silicon

Download LB_Omnichord.R20260909185035.macOS-arm64.dmg and its SHA-256 file. This build is ad-hoc signed, but it is not signed with an Apple Developer ID and is not Apple-notarized. macOS therefore blocks the first normal launch by default.

Installation:

  1. Open the DMG, drag LB_Omnichord.app to Applications, then eject the DMG.
  2. Open Applications in Finder and double-click LB_Omnichord. macOS shows a warning and blocks this first launch; dismiss the warning.
  3. Open the Apple menu, choose System Settings, select Privacy & Security in the sidebar, and scroll down to Security.
  4. Find the message about LB_Omnichord and click Open Anyway. This button is available for about one hour after the blocked launch attempt.
  5. Enter your Mac login password or use Touch ID if macOS asks for confirmation.
  6. When the warning appears again, click Open. macOS saves an exception for this app, so later launches work normally.

This app-specific exception is sufficient; do not disable Gatekeeper or globally weaken Allow applications downloaded from.

Apple: Open a Mac app from an unknown developer

Windows native (experimental)

Download LB_Omnichord.R20260909185035.Windows-x86_64.zip and its SHA-256 file, extract the complete zip, then double-click LB_Omnichord.cmd. Do not use Explorer's Run with PowerShell on the internal run_windows.ps1: the double-click launcher supplies a process-only execution-policy bypass and keeps startup errors visible.

The portable directory contains separate native AMY and Qt frontend executables; it is not a single executable and the extracted files must stay together. Native Windows pointer hardware, audio and MIDI still need physical validation.

Android arm64 (experimental)

Download LB_Omnichord.R20260909185035.Android-arm64.apk and its SHA-256 file, allow installation from this source when Android asks, then install the APK. The package contains a PySide6 frontend and a separate private AMY/Oboe service process communicating through the app-private amy.sock.

This package is CI debug-signed so it can be installed and emulator-tested without a repository signing secret. It is not a Play Store bundle or a stable update channel, and physical touchscreen, speaker, route-change and latency validation is still required.

ESP32-P4 firmware (v1.x and v3.x silicon)

Download LB_Omnichord.R20260909T185035.ESP32P4.zip and its SHA-256 file. It expands to a versioned directory containing separate v1/ and v3/ image directories, flashing instructions, and Python flashers for both legacy and current esptool syntax. Use v1 for revision 1.x silicon, including the physically tested v1.3 board; use v3 only for revision 3.x silicon.

Both firmware profiles receive native AMY wire commands through the LP UART at 1,000,000 baud, include Gamma9001, 11 buses, capacity for 1280 reusable-sequence tags, and the physically selected 48 kHz / 128-sample / 2 x 128-frame audio geometry. CI proves compilation and image structure; v3 I2S audio and LP-UART operation still require physical-board validation.

Build provenance

AMY fork release: releases/amy_omnichord_R20260909T140940 at immutable build commit 5e3cd575fc744b9a0cd3e9014030acc7bf4dc5c2.

Each application package has signed GitHub build-provenance and SPDX 2.3 SBOM attestations. The ESP32-P4 firmware and Raspberry Pi realtime setup script each have a separate signed build-provenance attestation. Download an asset and verify it with gh attestation verify ASSET --repo linuxificator/LB_Omnichord; add --predicate-type https://spdx.dev/Document/v2.3 for an application package to verify and inspect its SBOM attestation.

R20260909T164448

Choose a tag to compare

@github-actions github-actions released this 09 Sep 17:21

Linux x64

Download LB_Omnichord.R20260909164448.Linux-x86_64.AppImage and its SHA-256 file.

Raspberry Pi 4 / 5 (64-bit Raspberry Pi OS)

Download LB_Omnichord.R20260909164448.RaspberryPi-aarch64.AppImage and its SHA-256 file. This Pi 4 baseline also runs on Pi 5.
For reliable audio under load, also download LB_Omnichord.R20260909164448.Pi4-Pi5-realtime-setup.sh and its SHA-256 file. Verify the checksum, run the script with sudo, and reboot when requested. The application warns at startup when this tested profile is incomplete.

macOS Apple Silicon

Download LB_Omnichord.R20260909164448.macOS-arm64.dmg and its SHA-256 file. This build is ad-hoc signed, but it is not signed with an Apple Developer ID and is not Apple-notarized. macOS therefore blocks the first normal launch by default.

Installation:

  1. Open the DMG, drag LB_Omnichord.app to Applications, then eject the DMG.
  2. Open Applications in Finder and double-click LB_Omnichord. macOS shows a warning and blocks this first launch; dismiss the warning.
  3. Open the Apple menu, choose System Settings, select Privacy & Security in the sidebar, and scroll down to Security.
  4. Find the message about LB_Omnichord and click Open Anyway. This button is available for about one hour after the blocked launch attempt.
  5. Enter your Mac login password or use Touch ID if macOS asks for confirmation.
  6. When the warning appears again, click Open. macOS saves an exception for this app, so later launches work normally.

This app-specific exception is sufficient; do not disable Gatekeeper or globally weaken Allow applications downloaded from.

Apple: Open a Mac app from an unknown developer

Windows native (experimental)

Download LB_Omnichord.R20260909164448.Windows-x86_64.zip and its SHA-256 file, extract the complete zip, then double-click LB_Omnichord.cmd. Do not use Explorer's Run with PowerShell on the internal run_windows.ps1: the double-click launcher supplies a process-only execution-policy bypass and keeps startup errors visible.

The portable directory contains separate native AMY and Qt frontend executables; it is not a single executable and the extracted files must stay together. Native Windows pointer hardware, audio and MIDI still need physical validation.

Android arm64 (experimental)

Download LB_Omnichord.R20260909164448.Android-arm64.apk and its SHA-256 file, allow installation from this source when Android asks, then install the APK. The package contains a PySide6 frontend and a separate private AMY/Oboe service process communicating through the app-private amy.sock.

This package is CI debug-signed so it can be installed and emulator-tested without a repository signing secret. It is not a Play Store bundle or a stable update channel, and physical touchscreen, speaker, route-change and latency validation is still required.

ESP32-P4 firmware (v1.x and v3.x silicon)

Download LB_Omnichord.R20260909T164448.ESP32P4.zip and its SHA-256 file. It expands to a versioned directory containing separate v1/ and v3/ image directories, flashing instructions, and Python flashers for both legacy and current esptool syntax. Use v1 for revision 1.x silicon, including the physically tested v1.3 board; use v3 only for revision 3.x silicon.

Both firmware profiles receive native AMY wire commands through the LP UART at 1,000,000 baud, include Gamma9001, 11 buses, capacity for 1280 reusable-sequence tags, and the physically selected 48 kHz / 128-sample / 2 x 128-frame audio geometry. CI proves compilation and image structure; v3 I2S audio and LP-UART operation still require physical-board validation.

Build provenance

AMY fork release: releases/amy_omnichord_R20260909T140940 at immutable build commit 5e3cd575fc744b9a0cd3e9014030acc7bf4dc5c2.

Each application package has signed GitHub build-provenance and SPDX 2.3 SBOM attestations. The ESP32-P4 firmware and Raspberry Pi realtime setup script each have a separate signed build-provenance attestation. Download an asset and verify it with gh attestation verify ASSET --repo linuxificator/LB_Omnichord; add --predicate-type https://spdx.dev/Document/v2.3 for an application package to verify and inspect its SBOM attestation.