Each Live scene can carry its own tempo and time signature, settable via OSC

AbletonOSC’s Scene API exposes /live/scene/get/tempo, /live/scene/set/tempo, /live/scene/get/tempo_enabled, /live/scene/set/tempo_enabled, and equivalents for time_signature_numerator and time_signature_denominator. When a scene has its own tempo enabled, launching that scene (/live/scene/fire ) automatically changes Live’s global tempo to the scene’s value. This is how multi-section sets encode different section tempos — each scene acts as a section marker that carries its transport settings. A visual host subscribed to /live/song/start_listen/tempo will receive the tempo change automatically when the scene fires.

Examples

Encode a 140 BPM section: /live/scene/set/tempo 2 140.0, /live/scene/set/tempo_enabled 2 1. When scene 2 fires, Live’s tempo jumps to 140. Subscribe to tempo changes in the visual host: /live/song/start_listen/tempo.

Assessment

A set has three scenes: 120 BPM intro, 140 BPM main, 90 BPM outro. What OSC messages configure scene 1 (index 1) as the 140 BPM main section? What does the visual client receive when scene 1 is launched?