Check Local Control in Utility → MIDI. Set it to ON when you expect the MicroFreak keyboard to play its own sound engine directly. Local Control OFF is intentional only when an external sequencer returns the notes.
Do this first
- Open Utility, then MIDI.
- Find Local Control and set it to ON for direct playing.
- Play one key and confirm the MicroFreak’s sound engine responds.
- If you are using DAW MIDI echo, decide whether Local Control OFF is needed to prevent double triggering before changing it again.
Diagnose it
Does the keyboard transmit MIDI but the MicroFreak itself stays silent?
Yes: Local Control may be OFF; set it to ON for direct playing.
No: Check the audio path, preset level and any external MIDI routing separately.
Is a DAW or sequencer echoing MicroFreak notes back to it?
Yes: Local Control OFF can prevent double triggering; verify the returned MIDI route before relying on it.
No: Use Local Control ON for normal local performance.
Expected result
With Local Control ON, a played key reaches the MicroFreak sound engine directly.
Why this works
Arturia states that Local Control OFF leaves the keyboard transmitting MIDI but disconnects it from the sound engine, which can make the instrument appear dead.
Still stuck?
Recheck the physical MIDI direction and the exact source device setting. If this behavior differs on your hardware, keep the model/revision and setup details for a correction report.
All MicroFreak fixesSources & review
Last desk review: . Documentation does not replace a physical hardware test.
- MicroFreak User Manual, version 5.0.1 · Arturia
Sections reviewed: User Manual 5.0.1, §17.4 About Local Control.