A cross-platform Flutter application designed for editing presets on the Expert Sleepers Disting NT module. It provides an intuitive interface for managing algorithms, parameters, and mappings on your Disting NT device.
- Comprehensive Preset Management: Easily load, save, and create new presets.
- Detailed Algorithm Editing: Access and modify all parameters for each algorithm in your preset. Some algorithms feature custom UI views for a more specialized editing experience.
- Advanced Parameter Mapping: Configure CV, MIDI (including a CC detection helper), and I2C mappings for dynamic control over your sound.
- Visual Routing Analysis: Understand the signal flow within your presets with a clear graphical representation.
- Performance Mode: View and interact with all your mapped parameters on a single screen, with real-time updates from MIDI/I2C (CV changes provide offsets and are not currently reflected in real-time on sliders).
- Specialized Editors: Benefit from dedicated UI components for certain parameter types, such as an intuitive BPM editor for tempo-related parameters.
- MCP Server: Includes a built-in MCP (Model Context Protocol) server (on desktop platforms) for integration with external tools and AI-driven workflows. See the Model Context Protocol website for more details on MCP.
- Offline Data Management: Synchronize and manage algorithm metadata for offline use or when the Disting NT is not connected. Features incremental sync and improved algorithm rescan UX.
- Drag & Drop Installation: Install preset packages by simply dragging and dropping them onto the load dialog (desktop platforms).
- Cross-Platform: Runs on Windows, macOS, Linux, iOS, and Android.
| Platform | Minimum Version |
|---|---|
| macOS | 10.15 (Catalina) |
| iOS | 15.6 |
| Android | API 24 (7.0 Nougat) |
| Windows | 10 |
| Linux | Ubuntu 20.04 LTS+ |
- Download the latest release for your platform from the GitHub Releases page (or TestFlight for iOS).
- Install the application.
- Connect your Disting NT to your device via USB.
- Launch
nt_helper, select the MIDI input/output ports for your Disting NT, and connect.
For detailed instructions, troubleshooting, and a full feature list, please refer to the project website documentation.
If the app does not show a window, nt_helper writes an early startup log that can be shared with the developer:
- Windows:
%LOCALAPPDATA%\nt_helper\logs\nt_helper_startup.log - macOS/Linux:
~/.nt_helper/logs/nt_helper_startup.log
On Windows, if that file is not created at all, the failure is likely occurring before nt_helper's native entry point runs (for example, a missing system runtime or loader error).
The Disting NT does not need to be connected for the app window to open. After the UI starts, the same log records MIDI device discovery/autoconnect attempts and will say when the saved Disting NT MIDI ports are not visible. In Flutter CLI output, Lost connection to device refers to the macOS/Windows app process used by flutter run, not to the Disting NT hardware.
- v1.39.0+77: Added incremental sync and improved algorithm rescan UX
- Drag & Drop Support: Preset packages can now be installed via drag-and-drop on desktop platforms
- MCP Enhancements: Simplified server implementation, improved connection stability, and added CPU usage monitoring
- Algorithm Matching: Added fuzzy category matching for better algorithm discovery
- Routing Improvements: Enhanced real-time routing data queries from hardware
Contributions, issues, and feature requests are welcome! Please feel free to check the issues page.
This project is open source.
The application includes an MCP (Model Context Protocol) server with 6 tools for AI-assisted preset creation:
| Tool | Purpose |
|---|---|
search |
Find algorithms by name or category |
show |
Inspect preset, slot, parameter, routing, CPU, or screen |
new |
Create a new preset with optional algorithms |
save |
Save the current preset to the device |
add |
Add an algorithm to the preset |
edit |
Modify preset, slot, or parameter values/mappings |
Most tools use target to specify what they operate on (e.g., target: "algorithm", target: "slot").
See docs/mcp-api-guide.md for detailed documentation.