Hi, despite Myo being discontinued, it is still a relatively nice and usable option for continued use. I noticed I was getting relatively high CPU usage (>60%) from MyoMapper.
On a local build, I removed the GUI interface showing current pitch yaw and roll values and now average 5-12% CPU usage. Mileage may vary.
The other issue I'm looking for help with is when MyoMapper is unfocused (Ableton or max msp is in the forefront) - eventually Myomapper stops transmitting values. From debugging, the Myo Api is still transmitting values that are processed.
Meanwhile , timerCallback() isn't running and will only update when I refocus on MyoMapper or move any other window.
I'm using Mojave, but pretty sure this issue extended to older OS's.
Hi, despite Myo being discontinued, it is still a relatively nice and usable option for continued use. I noticed I was getting relatively high CPU usage (>60%) from MyoMapper.
On a local build, I removed the GUI interface showing current pitch yaw and roll values and now average 5-12% CPU usage. Mileage may vary.
The other issue I'm looking for help with is when MyoMapper is unfocused (Ableton or max msp is in the forefront) - eventually Myomapper stops transmitting values. From debugging, the Myo Api is still transmitting values that are processed.
Meanwhile , timerCallback() isn't running and will only update when I refocus on MyoMapper or move any other window.
I'm using Mojave, but pretty sure this issue extended to older OS's.