traktor does seem to try and workout the most sensible way of processing the data with least conflicts when u stack multiple controls to the same midi input - but does often get it wrong - or at least not do what u wanted.
i had a similar issue with some midimasher code to enable the pseudo postfaderefx mode but i thought the only thing that didn't work in the end was that if the effects unit had to change from group to single then all the other settings got ignored - but on a second press they all worked.
this is what i setup to do that:
Code:
traktor.fx_control{
unit = unit,
mode = "single",
fx = "Gater",
param1 = ON,
button1 = ON,
button2 = OFF,
drywet = 127 - math.floor(vol/2),
active = ON,
deck_a = ON
}
from experiments it seems there's very little (zero) difference in traktor between stacking multiple controls to one midi input or sending traktor a whole bunch of messages within a very short space of time (<3ms) so this should work just as tho u had mapped all those controls to one button etc.
for some reason traktor just ignores everything after the mode=single if the effects unit was in group mode previously. pain in the ass...
in midimasher speak tho what u are doing is something like this that should work with any issues i thought:
Code:
traktor.fx_control{
unit = 1,
fx = "Delay T3",
param1 = 38,
param2 = 72,
param3 = 27,
drywet = 50,
active = ON,
deck_a = ON
}
by "the effect value slowly increases" u mean u have an auto-repeat in button mode to ramp up or down some fx unit value?
Bookmarks