hello.
most likely not a bug but me not understanding what's going on.
here's what happens.
i have a knob with a custom midi assigned to send sysex (delaytime on a machinedrum)
everything works fine, except for one thing, the custom midi doesn't stop sending the sysex, wether i move the knob or not.
this leads to two things:
the parameter can't be edited on the machinedrum because the sysex took over.
a steady flow of sysex makes the machinedrum unresponsive and sometimes crashing.
what did i do wrong and how can i fix this?
thanks in advance,
martin
isn't it the way that midiout should not send data while i'm not moving the knob? the trigger of the knob is set to x
did i find a bug? (sysex)
-
- Liine Staff
- Posts: 285
- Joined: 01 Oct 2010 11:06
Re: did i find a bug? (sysex)
Hello Martin,
Most likely there is an object constantly moving (with physics enabled) or a script coded in a way to continuously send data. Please send a short example JZML to support@liine.net
Thanks,
Nick
Most likely there is an object constantly moving (with physics enabled) or a script coded in a way to continuously send data. Please send a short example JZML to support@liine.net
Thanks,
Nick
Re: did i find a bug? (sysex)
Hello Nick,
i had another look at how i build my knobs and realized that my way of thinking may be way too complicated.
my knobs each had a custom midi, an expression and a script and still didn´t work as supposed.
now there´s only a knob and a script with:
seems way more straightforward and works and can be customized further with more variables.
thanks for joining in and the offer to help.
cheers,
martin
i had another look at how i build my knobs and realized that my way of thinking may be way too complicated.
my knobs each had a custom midi, an expression and a script and still didn´t work as supposed.
now there´s only a knob and a script with:
Code: Select all
On Expression x
midiout(0, {0xF0, 0x00, 0x20, 0x3C, 0x02, 00, 0x60,0 ,x*127, 0xF7});
thanks for joining in and the offer to help.
cheers,
martin