Skip to content

MIDI Mapping Issue on MPC One (Hakai v3) - Q-Link Numbering Changes Across Screens #73

@Gakogit

Description

@Gakogit

Hi ,

I’m facing a MIDI mapping issue with my MPC One (Hakai v3 firmware) and I’m looking for some advice or feedback from anyone who has dealt with this.

Setup:

MPC One running Hakai v3
Faderfox EC4 MIDI controller (16 encoders)
Goal: Control all 16 Q-Links simultaneously, just like on the MPC X/SE, without needing to switch pages on the MPC.

What I’ve done so far:

Following TheKikGen Guide, I accessed the MPC via SSH and edited:
the MPC.settings file
the MIDI Learn file

Example of my Q-Link mapping in the XML file:

The Problem:

The Q-Link numbering (Target_control) changes dynamically depending on which screen/page is active on the MPC:
In Screen Mode, Q-Links seem to be assigned horizontally.
On other pages (like Program Edit or Mixer), the assignments change vertically or shift completely.

What I really want is to control specific parameters in the Sample Edit page, especially Start / End points and Zoom, but I want to keep the Qlink configuration of the other pages

As a result, my physical mapping on the Faderfox stops matching the parameters when I navigate through different screens.

My Question:

Has anyone figured out a way to lock or stabilize the MIDI mapping to Q-Links in standalone mode despite the screen-dependent behavior?
Or is there any alternative way to map directly to fixed internal parameters (filters, envelopes, mixer levels, etc.) without relying on Q-Links?

What I really need is to have 16 hardware knobs always mapped and usable, no matter which screen the MPC is on.

I’m open to any workaround, even involving a MIDI translator or external script if necessary.

Thanks a lot in advance to anyone who reads and replies! 🙏
Honestly considering returning the Faderfox if this turns out to be impossible technically.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions