i see your point now.. heres is ai’s response when i quoted what you said:
'The MPC3 “Macro” Workaround for the Hapax
To make the sample voice architecture usable with the Hapax without breaking your sanity on every project, use Akai’s internal Q-Link Macros:
-
Inside your MPC Drum or Keygroup track, navigate to the Global Q-Link menu.
-
Map Macro 1 to Cutoff, Macro 2 to Decay, Macro 3 to Pitch, etc.
-
Because the MPC’s main Q-Link macros do listen to a predictable set of MIDI CCs, you can build your Hapax Instrument Definition File to map strictly to those generic Macros. [1]
This allows you to change the underlying samples or drum kits as much as you want; as long as your internal track routing points to those standardized macro slots, the Hapax will control your samples cleanly across different projects.’
theres 16 q-links i guess
ah! but those assignments are tied to the track in focus only. yeah thats pretty painful. ai recommends to stick to the plugins. bummer because i wanted to use wavetable playback on a ‘hardware’ device.