Replace record mode + Cycle makes Audio Event become invisible during recording

Hi,

There is an issue where the recording Audio Event would turn invisible when Cycle is enabled and the audio record mode set to Replace.

Reproduction sequence :

  • Create an Audio Track and choose any input (no need to record actual audio, the signal can be blank)
  • Set the Locators over a few bars,
  • Enable Cycle,
  • Put the Cursor anywhere within the Locators range,
  • Set the Audio Record Mode to Replace,
  • Hit record and keep the loop going.

Result : When the Cursor reaches the Right Locator, and it loops again, the previously recorded data becomes invisible. It keeps doing that every time it loops until we stop recording.

replace record mode visual issue 1

However, it behaves differently when Audio Events are already present in the range, and when we start recording before or after these existing Events.

When we start recording before the existing Events, when the Cursor reaches the Right Locator and loops for another run, the currently recording Event disappears from the previous loop (same as explained above), except that the Events that were already there before starting recording become visible again. This behavior persists on each loop until you stop recording.

replace record mode visual issue 2

When we start recording after the existing Events, when the Cursor reaches the Right Locator and loops for another run, the currently recording Event will disappear from both the previous loop and the current loop, and will only become visible again when it reaches the first already existing Event, and remain visible until it loops again, etc.

replace record mode visual issue 3

One last thing : Opening / closing Take lanes during the latter iteration makes the invisible Event to “refresh”, but only from the Left Locator to the Cursor position at the time you press the button.

replace record mode visual issue 4

Really weird issue.
It’s the number 41 in the issues list.

Still not fixed with 12.0.40.

1 Like

Can confirm this issue, always wondered, how nobody noticed it.

2 Likes