By Wul
Sat Jul 23, 2022 7:53 am
I’ve previously posted about a midi controller bug in 2.11. Regarding strange keys triggering different functions of the Mpc one, when an external keyboard is connected via midi and the control field is highlighted.
I have now seen why this is happening. I have been monitoring the Mpc.settings file, in that file there is two lines which are not usually there,
Reason I say that is that on kikgens GitHub he suggests adding these two lines so as to enable global controller mapping for standalone.
I.e.
<VALUE name="MidiLearnEnabled" val="1"/>
<VALUE name="MidiLearnPreviousMapping" val="(your xmm full path file name)"/>
Now these two lines are present in 2.11 , sometimes first line is set to 0 , sometimes it 1 and the path to the .xmm file is a random preset controller, different everytime . Even if I change the value of the first line and add a different path, it gets overwritten every time.
The result is the random results I describe, and only when a midi keyboard/controller is attached.
Now the cynic in me wonders if this is intentional.
A bit like what apple do when they bring out a new model.
I have now seen why this is happening. I have been monitoring the Mpc.settings file, in that file there is two lines which are not usually there,
Reason I say that is that on kikgens GitHub he suggests adding these two lines so as to enable global controller mapping for standalone.
I.e.
<VALUE name="MidiLearnEnabled" val="1"/>
<VALUE name="MidiLearnPreviousMapping" val="(your xmm full path file name)"/>
Now these two lines are present in 2.11 , sometimes first line is set to 0 , sometimes it 1 and the path to the .xmm file is a random preset controller, different everytime . Even if I change the value of the first line and add a different path, it gets overwritten every time.
The result is the random results I describe, and only when a midi keyboard/controller is attached.
Now the cynic in me wonders if this is intentional.
A bit like what apple do when they bring out a new model.