m4l patch cpu high when patch closed

    Feb 09 2014 | 5:43 pm
    I have a very large patch that uses udpreceive/send. If the patch is closed (not opened in edit mode) then I get huge spikes in the CPU when sending information to the device through udp. When the patch is opened in edit mode, there is no CPU spike.
    Can anyone shed some light as to why CPU behaves differently in edit mode vs non-edit mode?

    • Feb 09 2014 | 6:25 pm
      Right ive narrowed it down to UDP receive. Simply sending data from one lemur XYpad to udpreceive results in my CPU going from 4% to ~35%
      Anyone know why this is? It also doesnt happen when the patch is opened in edit mode.
      Seems very very strange...
    • Feb 09 2014 | 6:36 pm
      It was lemur causing the problem. For some reason it doesnt like a underscore in my object :/