MFL tool sending multiple changes

[LittleWiggler]

With the help of a few folks here I have a MaxForLive utility that allows me to send Program Changes via continuous controller.

I have attached the device text at the bottom of this message.
Ableton Live 9.7 and MFL 730.

This worked well with the tools I had at the time, but I have a different guitar processor and it is not able to ignore redundant PC changes.

Example: Lets say I have CC 65 set for the MFL device. This will take a CC and convert it to a Program Change. Let's start with CC value of 10. A few measures in I change the CC value to 30. The first bars with CC 10 work as expected, and only one PC is sent at the beginning. When it gets the new CC value of 30, the device changes the patch to 30 as expected, but it then keeps sending the patch change at what appears to be a random interval. When it goes back to CC value 10 it works as expected.

The midi would look something like this:
30 --------
10 ----| |----

I would expect 3 events to happen here - a patch change at the start (val 10), one change to 30, than later back to 10. Instead I am getting the first patch change to 10, then when it starts with val 30 it starts sending a patch change at some interval, then when back to val 10 a single change.

Is there a way to suppress the sending of duplicate Patch Changes? And why does it only happen with values that are different from the starting value?


----------begin_max5_patcher----------
769.3ocyWtziaBCD.9bVo8+fE8ZZjMrjG6s18Tu06qVsxAbR7JvNx1Py1U8+
d8Cf.oPfDwF0CwPFO1d7mmY7vG2e2Du07CDoG3QvyfIS9PKYhUlQxjRAS7Rw
GhRvRqhdLxu3qeyaZQeJxAkUdBMmLSsiJiI4zHRkBa3LECmRrJ8MAEm.9NOI
tpeVVJkkPT1YGUJkFa0WuRecdkp7LkVQ066INS1aMls0aJvixTkO.uTahcCv
NyA0sGI821o.AmAKkuGqh1QYaeUPhTt4GsXV3Tf+bsRfEqLsnkyffWri3O2e
m4o9wzAytHdZJwXqmBubzLz3QrPu1YP0dciX6Zqfia+KFKqBM.IX4HfEqqi1
TMpUtt4XQECZq+dg.B0seiwYYSBG2s6he09WPj5iLrhxY0XfudKaffuEBVOD
TnAB8xsvEcNjZKUic0drPiBEQ7JggWmPZzoDmSheEqTB55LE43axBjWxbCSS
xH7Mkxq5n9JjwnJo5c2hT5EzPiRNhZqSJKmJomXiMzPtiKTm6nsg1Ib11VUt
P2B2siubM9eckRKkFS09DiWfoeuAlCOJbNz5AgBLOdXwmY1omd5K.EGDwY4D
gx75OE7s5iHvS6zYfIOVMjDJiDwyXptigZWkNPK3GJbBM5Bh5C5CwcDPiVZy
mEZCnQPKUC7qGd1RRSCgh3IbgaNfyBlZZdvzpaPMFd8iVz4SvFZsEzpNsk+I
Uwn66uea5U65621AyX56ifKGam+t3fPapjQDCvyeqT+WHc4XZo0OJH7SjRlL
k5j1xQrrufd.UwuZk9MrBAWb8fzc0MBB+jIIkMdX7LUAcNJgtdJE3BJ6FRt0
zdWwoe6gcVMcbB5j7LQTocW7QAfZ4CiIREkUkN74ik.VWqcz3XBqQRmXpzTQ
kkWvtOLGrcgFhc4++oYEb6MK3fNFu87xfB+dsK3sGXC5fzZXnq1vJhOw62qK
2SVL0NaRmC6MW0Nym59Ok49uKggmfXp+mWaw7vBchBkNKQlvkF6vx4lx2sKn
t4u.659u7C
-----------end_max5_patcher-----------

[chapelier fou]

Not sure i got it,
but you seem to send the midi messages twice indeed. Try this :

<pre><code>
----------begin_max5_patcher----------
811.3ocyXtzaiBCD.9L4WgE6UZDFBAZusaOs216UUUNfahq.ajwvltU8+95G
.kjBMjDZTNDCL90Led7L14sYV1qXawE1f6.O.rrdalkkVjRfU82V1YnswonB
cyro3+xV8hsioJAdqPKNkTgmK1PJRvUjXbS8jDcsxdbyxFYOynBJJCqq4mbB
JE7KVZRS04HQ7FBc8SbbrvnYvv4AN.ukycc.g2pJ8bm6Bdry.VP9md.gxJpE
SKyHzTrPq2vODxJEMR8qkVHdM0nOMZgoQhWywFUvdEht11AXSnhlGfGUs88Y
yTENijewrrLrZL1CfUv4vdnVvoSsa7TTCFFo.lutDFMIXy8yX6DHg1kQNvpV
UOfUHdqM1S0c3BrEV4bbgDnHAgQ6X8dRaUZ925osdsqCLni0OnaVP3P8nyDs
Ga9LvxQbogHv7mvTzJCk5GldC4wobydNkgTNZM.GUgSdBIDbxpRA9i2Jp4bM
nUjLsDydtQbi7tJVJit9Kn8NssXCiKFaiarAXO0URIhV2F2dZ.gVQJHMDyTu
1wp4wQ5kMP7pLRBQR7d7r7N8cbdtt5fSdKTOVDNgQpllsbCE7496+APv.wLZ
ElKTu9GNasbIAb+FYbO7cM8HkPwwrRpnqm6N6.6sEc235e.9B9s.kRhOv1aX
TfhtA5s2PWe8dV3A1eGn6C71g5yNKOv1kmiZiuhowrTF2Lmty8cTEKTkxhtS
22wJ7.t64qy52aGdFt6QQmu2t2kmEb4D02ATftmKJfglrMASHJ7F+QTTILNs
Ck7EAIkQlK5iV9mww4b0zxjnEVGybZBSFcjzp9WmC0sqjIGmDZeddmMKgZGu
ESIJgiGke5vv5oWmrXu6Vns.k7coWAqjG2LZ0dWfksFQBtPPnsweenMQM3CC
cCIIAS6F7HgTnN4kFyt8tJdLZSvUk1r3pRa7upzF3Uk13d0nMpqLcP0QkDrC
A+toi2XTmKDdbGCdtfKWiPc7uXZyxw.G3IpNlzEn7b4sOJpGSslHSq9h4jzg
N5OITym5SEYywp6JZZ+BsDDWlfTHyNVxM4r1FY9emryXIXNsjTesR4L+9r+C
dqJa5A
-----------end_max5_patcher-----------
</code></pre>

[LittleWiggler]

Thanks for looking at it, unfortunately what you posted did not work (it is not sending any Program Changes).

Where would I look to see that messages are being sent multiple times?

[chapelier fou]

it's always good to make use of the print object to monitor what's going on in the Max window.