Ruoxi Jia

I'm working on a motion tracking project.

The area boundaries in space are set according to the two axis’s values, which is determined with "if... then 1 else 0" object. I want to use 1/0 to control midi on/off.

My problem is that the "1" or "0" outputs look to be constant from the output end (int value or toggle box). But the "1" and "0" are actually flashing so for example the "midi on" command is flashing and won't work. I think it is because the motion values are refreshing and changing all the time.  Is there a easy way to make them constant? 

I've attached the maxpat in this post. Sorry there are a lot of objects in it. The problematic objects are marked as red. 

data-smothing

Can you be more specific? I've just attached my maxpat to this post.

Please, next time, can you provide only the relevant part of your patch that clearly expose your problem?

Also, you don't need to attach the patcher file, just use the 

Source Audio meant that you should check the object named "change", which filters out repetitions.

You might also search for 'hysteresis' which is basically a moving threshold, like so: output will go from 0 to 1 if input go above 70 but then output will go from 1 to 0 only if input goes under 50. This will prevent the output from alterning between 0 and 1 too frequently.

Thanks for reminding. I cannot re-produce the problem here because the system is connected to sensors so I thought it was better to show the whole process for understanding. Will make the patcher cleaner next time.

The [change] object is helpful for this problem. Thanks for the insights!

if you reduce unneeded objects, it is easier to detect mistakes.

you make a lot of comparisons, and need to receive all 9 input

values frequently to reflect current sensor states.

Setting that correctly on sender side is another factor.

Data smothing