How to remap controls? Some bugs report

[Potreba]

Hi. I've noticed omission of numbered track select button. Judging by the videos ( I do not own force), it's impossible to copy or delete tracks, unless threre are these buttons. Also sometimes led feedback and qlinks get stuck and unresponsive. Also 'shift' button makes qlink go in small increments. It means qlinks 1-4 could go from 0-127 in single turn, while 5-8 takes 15 turns to go from 0-127. Another critical omission for my application is crossfader. I could think of few ways to implement this: 1. Use some some button for pads, so it would emulate launchpad - the harder you hit, the faster it transitions between values. It is essentially 16 levels of crossfader with some interpolation applied (or not). 2. Use button combo + data encoder. 3. Use external controller. So is there a way to remap these controls?

[Potreba]

It turns out, that map_force.conf is quite easy to modify! So I've made some changes to + / - mapping and playstart button. Now its launching scene 1 and browsing clip matrix up and down. I'd move launch/notes to some other button too when I'll figure out better layout. WIth playstart and - its quite easy to imitate the way ableton's launch scene/move down works. Along with disk streaming I was able to program 70 + scenes and couple GB worth of audio to play back perfectly.

[Potreba]

##################################################

MPC LIVE to FORCE mapping

################################################## [Map_LIVE_FORCE_ButtonsLeds]

QlinkKnobsShiftMode is used to simulate eight or sixteen qlinks knobs.

when holding shift, an offset is added to the knob id.

Authorized value are 0 (disabled) 1 (enabled)

Note : parameters are always prefixed by "p"

_p_QlinkKnobsShiftMode=1

Columns pads

SHIFT_BANK_A=COLUMN_PAD1 SHIFT_BANK_B=COLUMN_PAD2 SHIFT_BANK_C=COLUMN_PAD3 SHIFT_BANK_D=COLUMN_PAD4 BANK_A=MUTE BANK_B=SOLO BANK_C=REC_ARM BANK_D=CLIP_STOP

Knobs

QLINK1_TOUCH=QLINK1_TOUCH QLINK2_TOUCH=QLINK2_TOUCH QLINK3_TOUCH=QLINK3_TOUCH QLINK4_TOUCH=QLINK4_TOUCH

Qlink 5 to 8 are simulated with the shift key

QLINK5_TOUCH=QLINK5_TOUCH QLINK6_TOUCH=QLINK6_TOUCH QLINK7_TOUCH=QLINK7_TOUCH QLINK8_TOUCH=QLINK8_TOUCH

Common buttons

MENU=MENU PLAY=PLAY SHIFT_PLAY=NOTE SHIFT_PLAY_START=LAUNCH STOP=STOP REC=REC MAIN=MATRIX SHIFT_MAIN=MASTER NOTE_REPEAT=ARP COPY=COPY ERASE=DELETE TAP_TEMPO=TAP_TEMPO SHIFT_TAP_TEMPO=SHIFT_MUTE_PAD5 FULL_LEVEL=SELECT SHIFT_FULL_LEVEL=EDIT 16_LEVEL=CLIP SHIFT_16_LEVEL=MIXER UNDO=UNDO

REDO

SHIFT_UNDO=SHIFT_UNDO SHIFT_STOP=STOP_ALL PLAY_START=LAUNCH_1 SHIFT_MENU=LOAD OVERDUB=SAVE PLUS=UP MINUS=DOWN QLINK_SELECT=KNOBS SHIFT_PLUS=RIGHT SHIFT_MINUS=LEFT

[Potreba]

Upon further testing I've found that LED feedback for pads and bank buttons often fails. Unfortunately I'm incompetent to know why it fails, but I think it was present before my modifications to conf file.