Arturia MiniLab 3

Behaviour Every control was processed twice device_MiniLab3.py:115

This is the headline defect. event.handled already defaults to False, so setting it to False was a no operation. Every button and knob the script consumed was then handed to FL Studio's own MIDI handling for a second pass. That is where doubled transport hits and jumping knob values come from.

if _processor.ProcessEvent(event):
    event.handled = False

if _processor.ProcessEvent(event):
    event.handled = True

Flipping that flag alone would swallow every CC on the port, including the mod wheel and anything the user assigns by hand. Three call sites were changed so the answer is honest. Dispatch() now reports False for a key it does not own, OnCommandEvent passes the inner result up instead of dropping it, and OnWheelEvent claims the event only when it actually forwarded to Analog Lab.

def Dispatch(self, event):
    key = self._transform_fn(event)
    if key not in self._dispatch_map:
        return False
    callback_fn, filter_fn = self._dispatch_map[key]
    if not filter_fn(event):
        return True
    result = callback_fn(event)
    if result is None:
        return True
    return bool(result)

The harness holds that line in both directions. An unmapped CC 22 stays available to FL, CC 106 Stop is consumed, a V Collection pitch bend still forwards, and a pitch bend on an ordinary channel still reaches FL so bends keep working.

Behaviour Three plugins fell out of the list MiniLab3Plugin.py:68

Three missing commas. Python joins adjacent string literals, so 'BASSDRUM' 'Fruit kick' 'MiniSynth' became the single entry 'BASSDRUMFruit kickMiniSynth'. Knob feedback never engaged for BASSDRUM, Fruit kick or MiniSynth, because the name test could never match.

'BASSDRUM'
'Fruit kick'
'MiniSynth'
'PoiZone',

'BASSDRUM',
'Fruit kick',
'MiniSynth',
'PoiZone',

Behaviour Debug print on every refresh MiniLab3Plugin.py:887

SetParamValue carried a bare print(param, value). PluginParamReturn calls it eight times per OnRefresh, so it flooded the FL Studio script log continuously while a stock plugin was selected. Removed, and the byte is clamped in the same pass.

Behaviour Wrong unpack in the knob refresh branch MiniLab3Process.py:494

The branch unpacked two values from a function that always returns three, and passed the event object where a CC number belongs. Dead in the shipped mapping, live the moment CC 29 is routed differently.

KNOB_HW_VALUE, mapped = MiniLab3Plugin.Plugin(event, 0, 1)

parameter, value, mapped = MiniLab3Plugin.Plugin(event.data1, event.data2, 0)
KNOB_HW_VALUE = MiniLab3Plugin.KNOB_HW_VALUE

Behaviour Tempo read as sliced digits MiniLab3Navigation.py:246

getCurrentTempo returns BPM multiplied by a thousand. The old code chose two or three characters off the front of the string, so 99.5 BPM displayed as 995 BPM. Now it divides and rounds.

tempo_str = str(round(mixer.getCurrentTempo(0) / 1000))

Behaviour Snap mode 2 showed stale text MiniLab3Navigation.py:275

The snap table has no entry for mode 2, so the lookup returned None, and a None line leaves the previous text on screen. The display then reported the wrong snap mode with no sign anything went wrong. It now falls back to a labelled value.

Behaviour Channel name sanitising device_MiniLab3.py:79

Sync() called getChannelName without checking for a selection, and rebuilt the string one slice at a time inside a loop that constructed a fresh range object per character. Replaced with a guarded single pass that maps anything above ASCII to a question mark.

active_index = channels.selectedChannel(1)
if active_index != -1 :
    channel_name = channels.getChannelName(active_index)
else :
    channel_name = ''
channel_name = ''.join(c if ord(c) < 128 else '?' for c in channel_name)