Hi,
I’m running into a workflow-blocking issue with the MiniFreak hardware ↔ MiniFreak V link.
Desired workflow
- Use the hardware to explore sounds.
- When I like something, record the generated ARP/SEQ MIDI notes into the DAW.
- Then use MiniFreak V to continue playing that MIDI clip.
- Build multiple layers, each on its own track, each with its own MiniFreak V instance and preset.
- Use the hardware surface to control whichever instance I’m currently working on.
The problem
On the hardware:
- Utility → MIDI Settings
- Local Control = ON
- ARP/SEQ set to send MIDI notes (so generated notes are transmitted over USB)
In this state, everything works correctly:
- When ARP/SEQ is playing, the DAW receives the generated MIDI notes (confirmed in Snoize MIDI Monitor).
However:
As soon as I click “Link to MiniFreak” in MiniFreak V:
- The hardware stops sending ARP/SEQ-generated MIDI notes.
- The DAW only receives the notes I’m actively holding.
- The Utility → MIDI settings appear to be overridden.
- Even if I manually restore the hardware MIDI settings, ARP/SEQ notes are still not transmitted.
- The only way to restore ARP/SEQ MIDI output is to:
- Unlink
- Power-cycle the hardware
This happens:
- In Ableton Live 12 Standard
- In MiniFreak V standalone
- So it does not appear to be DAW-specific
System
- macOS Tahoe 26 (M1 MacBook Air)
- Ableton Live 12 Standard
- MiniFreak firmware: 4.0.1.2229
- MiniFreak V: 4.0.2.6369 (arm64)
- Snoize MIDI Monitor used to confirm actual MIDI output
Question
Is this expected behaviour when linked?
Or is this a known bug where the link process overrides the hardware’s ARP/SEQ MIDI transmit setting?
If this is by design, what is the recommended workflow for:
- Recording ARP/SEQ-generated MIDI from hardware
- Then using MiniFreak V instances to build layered arrangements
- While still using the hardware as the controller surface?
Thanks in advance.