Transport Playing

A global logic signal reflecting whether Bitwig's application transport is currently playing.

What it does #

Transport Playing outputs high while the main transport runs and low while it is stopped. It lets a patch explicitly mute, reset, hold, or change behavior according to transport state.

Controls and ports #

Control	Label	Official description
out	Out	High-logic state if the application's transport is playing; low-logic if it is stopped

Practical uses #

• Mute self-running generators when playback stops.
• Use a transition detector to reset counters or capture state when the transport starts.

Things to know #

• The signal describes the application transport, not whether audio is audible or the Grid engine is processing.
• Count-in, pre-roll, arranger/launcher behavior, and export may expose different transport transitions.
• The similarly matched Transport LFO Nitro body consumes this state but is not the output-only module.

Technical details #

No Nitro implementation has been confirmed for this visible module. The behavior is described conservatively from module metadata and editorial research.

The visible contract is the host boolean out = is_transport_playing ? 1 : 0. grid/lfo/transport_module confirms that Bitwig supplies an isPlaying value to Grid DSP, but it is a complete transport-phase generator and not this terminal's implementation.

Open questions #

• Measure start/stop edge sample, count-in, pre-roll, looping, launcher, bounce/export, audio-engine stop, and project switching.

Version and sources #

Checked against Bitwig Studio 6.0.6. This page combines Bitwig's module metadata, the existing Grid course and guides, and Nitro analysis where the mapping is strong enough to support a technical statement.

Related material #

• Grid Modules course reference

Return to Bitwig Grid Modules or the Grid Modules course lesson.