Continous tempo tracking - good or bad practice?


    Jul 22 2021 | 12:43 pm
    Hi! I'm very new to Max for Live so please forgive my ignorance. I'm making a device that continuously tracks the Ableton project tempo, calculates some stuff from that and then controls two instrument rack macros. This is done continuously so as I raise or lower the tempo by dragging the mouse the macro knobs move accordingly. Is this bad practice or CPU draining? Should this be initiated with a button click which checks the tempo and then performs the calculations and then controls the macro parameter knobs? Thanks!

    • Jul 23 2021 | 7:43 am
      Why don't you do it the way you want and test it ? Button would not give you realtime performance. But you can at least insert change object to avoid recalculations if tempo does not change and if you experience CPU overloads or similar limit the speed or something. At the end it depends what this calculations control, and how CPU intensive it is.
    • Jul 24 2021 | 10:44 am
      Thank you, I'll research the change object!