Playback, Markers and A/B Compare

Playback

• Space — play / pause, like the Play button above the timeline. After you open a file or edit, Play renders the new preview first and starts when it is ready; press it again to cancel. Preview in the chat panel renders without playing. The mix you are playing is held in the preview cache, so switching to the Graph or Transcript tab and back does not lose it; if the file has gone anyway, it is rendered again once.
• L — toggle loop; playback loops the selected region.
• Click the waveform — jump to that position.
• Ctrl+scroll or +/−/0 — zoom the waveform in/out/reset.
• Drag on the waveform — select a range (for range export, loop playback and agent context).

Markers and Selections

Markers annotate points and regions; the agent can refer to them by name.

• Ask the agent to add markers: mark the verse start at 0:30.
• Drag on the waveform to select a region; the agent gets it as context.
• Use Esc to clear the selection.
• The label lane — the lane under the tracks is where you name chapters and regions yourself. Double-click empty space in it, type a name and press Enter (Esc cancels); clicking the ruler opens the same name box. Double-click a label to rename it, drag it to move it (a region keeps its length), right-click to delete it. Each is one history step. Labels stay with the audio when an edit shifts time (a cut, trim, inserted silence, paste, speed change or stretch), and the agent can export them as Audacity label text, or import some.

A/B Compare

Compare any two session nodes and play both.

1. Ask the agent: compare the current version with the one before the reverb, or right-click a node in the Graph view and choose “Compare with…” to compare it, as B, with the current version.
2. The A/B compare bar appears at the top. Toggle between A and B to hear each.
3. Click Accept B to make the B node the new session head, or close the bar (×) to keep the current head.

Both versions are rendered into the project's preview cache, so a version you have just played is not rendered again. They stay there while the bar is open, even when the two together exceed the cache's 1 GiB (an hour-long mix does); closing the bar clears it back down.