Markus Fuchs

i am having problems with filtering and forwarding Midi CC#/value pairs to a couple of Dials that i have in my patch. I am using a "match CC# nn" function in front of every dial and set "CC#" to the corrsponding dials CC number (eg "match 71 nn"). But this does not work properly as it doesnt seem to respect the order of values eg: 2 dials, one CC# 55 and two CC# 71, i am monitoring the values and at first everthing is ok but when CC# 71 Val 55 is incoming which is supposed to set dial 2 to 55 it also sets dial 1 to 71.

So something is obviously wrong. I was under the assumption that the match object respects the order of incoming pairs but it doesnt seem to do it. This is the patch i am working on where things go wrong (bidirectional midi dials), though the described behaviour only comes up when the dials are connected bidirectionally (meaning they output midi and receive midi) but since i am pretty new i assume i have done something fundamentally wrong with the match function:

i am having problems with filtering and forwarding Midi CC#/value pairs to a couple of Dials that i have in my patch.  I am using a "match CC# nn" function in front of every dial and set "CC#" to the corrsponding dials CC number (eg "match 71 nn"). But this does not work properly as it doesnt seem to respect the order of values eg: 2 dials, one CC# 55 and two CC# 71, i am monitoring the values and at first everthing is ok but when CC# 71 Val 55 is incoming which is supposed to set dial 2 to 55 it also sets dial 1 to 71.
So something is obviously wrong. I was under the assumption that the match object respects the order of incoming pairs but it doesnt seem to do it. This is the patch i am working on where things go wrong (bidirectional midi dials), though the described behaviour only comes up when the dials are connected bidirectionally (meaning they output midi and receive midi) but since i am pretty new i assume i have done something fundamentally wrong with the match function:

distributing-midi-ccs-to-dials

there is a value pair of 71 55 coming from a ctlin object to a match object with "match 55 nn", why is the output of the match object 55 71 ? And how can i prevent it to work that way and make it only let value pairs through when 55 is the first value?

That is supposedly the last issue i have before i can start making awesome Reason templates with Push support and bidirectional Midi everywhere (on Push, on Ableton dial, with automation and in Reason - tweak somewhere and everything gets updated - that part is already working).

I just don't seem to understand the match object because this is all new for me.

Ok, do i read it right that when 55 78 hits a "routepass 55" then i get 55 78 at its rightmost outlet and when 78 55 hits it nothing gets through? Will try out later (not at my computer) but thx again for pointing me in the right direction, there is just so much stuff in there and i just have opened the can of worms :-)

Strike, it works now with a set of 32 Controllers on Reasons Malstroem Synthesiter and is a breeze to control via Push. It was the left outlet of the routepass that did the trick. Now i have alot of work to do, since there are a shitton of devices in Reason. And i need to find out how to name banks in the Push remote scripts but that is secondary.

Thank you again, this was awesome help :-)

Distributing Midi CCs to Dials