observing track states - should I worry about resources?

    Mar 11 2012 | 3:40 am
    I'm re-configuring the functionality of my (2) launchpads: the top 5 rows work as normal clip triggers, the bottom three are: arm - select track - stop all clips.
    I'd like the 'arm' and 'select track' to light up the respective buttons but it means I'll need 16x observe objects to observe which tracks are armed and also to observe the 'selected track' does that sound like a lot of overhead?
    what would be a good way for me to measure the impact of implementing this? Live's CPU meter?

    • Mar 11 2012 | 8:03 am
      No, you should be fine. There's very little overhead for on/off objects. I've done a lot more than that with plain-jane API objects without taking any hit.
    • Mar 11 2012 | 10:42 pm
      Thanks amounra!! very helpful :-)