whitelobster

I am attempting to create an interface using mira that gets activated from within a max for live device and then receives touch input via chrome on the same touch screen machine ableton is running on. Everything is working beautifully EXCEPT ableton's cpu maxes out very quickly when using mira. After a few minutes of running my patch (which worked perfectly in a non-mira implementation) the cpu quickly jumps well above 100% to 140,170 etc and audio begins to deteriorate before all together stopping.

What can I do to make mira run with max for live in a cpu efficient way? My patch has 7 mira multitouch objects each only receiving input from a single finger (originally these were lcd objects but mira doesn't work with pictslider or lcd objects). Could these multitouch objects be causing trouble? I've already deactivated drawing in the patcher window to conserve cpu, is there any other way to make these objects/another facet of mira more cpu efficient? Is there some sort of setting I can turn on to make multitouch a single finger input (perhaps listening for multiple fingers is draining the cpu?)

I've attached the patch below as text and the max for live device is available here

https://drive.google.com/open?id=0B8KDXofhzkB_MFBOdGJtN2V2OEU

I am attempting to create an interface using mira that gets activated from within a max for live device and then receives touch input via chrome on the same touch screen machine ableton is running on.  Everything is working beautifully EXCEPT ableton's cpu maxes out very quickly when using mira. After a few minutes of running my patch (which worked perfectly in a non-mira implementation) the cpu quickly jumps well above 100% to 140,170 etc and audio begins to deteriorate before all together stopping.

I've attached the patch below as text and the max for live device is available here
https://drive.google.com/open?id=0B8KDXofhzkB_MFBOdGJtN2V2OEU

mira cpu optimization with live