AbletonOSC exposes per-track output meter levels, enabling audio-reactive visuals driven by individual track energy

The Track API includes /live/track/get/output_meter_level (both channels averaged), /live/track/get/output_meter_left, and /live/track/get/output_meter_right. These return the current peak level of the track’s output signal as a float. Combined with the start_listen pattern, a client can subscribe to meter changes on any track and receive amplitude values to drive visual parameters — for example, mapping a kick drum track’s level to a visual intensity, or a bass track’s level to a colour gradient. This is a lighter-weight alternative to FFT-based audio-reactivity: the LOM meter values are already computed inside Live per output buffer, requiring no extra routing.

Examples

Subscribe to kick drum track (track 0) meter: /live/track/start_listen/output_meter_level 0 — updates push to /live/track/get/output_meter_level with params (0, level). Combine multiple tracks (kick, bass, melody) as a poor-man’s multi-band audio-reactive signal.

Assessment

What is the advantage of using AbletonOSC’s meter listeners over routing audio from Live to an external FFT analyser for audio-reactive visuals? Name one limitation of the meter-level approach compared to FFT.