RePitch 2 (ARA / Cubase 13) shows “No audio detected” and the main pitch view is blank

Cubase
,
1

Hi, I’m experiencing an issue using RePitch 2 as an ARA Audio Extension in Cubase 13 and would appreciate your help.

## Symptoms

- When I apply RePitch 2 as an ARA Audio Extension directly to an audio event, the main editor area (pitch/notes analysis) stays blank and I get “No audio detected” in the center. (please see attached screen shot)

- The overview waveform at the bottom is visible and matches the selected event/track audio.

- I cannot do manual pitch edits because the central analysis view is empty, but auto scale-correction seems to affect the audio by ear (so processing may be running while the main view fails to populate).

- Repro: Happens in an existing project, but works normally in a new project.

## Preconditions / Confirmed

- RePitch 2 is NOT used as a VST insert (ARA Extension only).

- I’m applying it to the event, not as a track-level extension.

- The target material is a clean, standalone single audio file: I first created it via Bounce Selection, and there are no edits or automation on that track/event.

-–

## Technical details (additional)

- OS: Windows 11

- DAW: Cubase 13.0.55 Build 328 (x64)

- RePitch 2: 2.0.76 (latest)

- Audio (Pool): WAV / 48.000 kHz / 24-bit / mono

- Project setup: 48 kHz sample rate (matches the file)

-–

## Question

- Are there any known cases of this behavior, and do you have recommended troubleshooting steps or workarounds (settings, workflow, cache/analysis reset, etc.)?

DAW_SC
DAW_SC1920×1041 279 KB

2

Did you add the RePitch extension by right clicking on the clip or via the track header? If the former, that may explain why the track header is showing no extension. The clip itself clearly shows the extension icon in the upper right.

As for the work window UI problem, I vaguely remember having this issue at one point, but don’t recall how I worked around it. Best guess would be something that forced creation of a new audio file, or maybe even just moving the clip to a different track (which wouldn’t create a new audio file, but might help if there is some issue in connection to the track in question). For forcing creation of a new audio file, things I can think of that I might have tried would include bouncing the clip as it stands, trimming the clip a little (e.g. shortening ends and adding brief fades) then bouncing, or rendering in place (which would also put it on another track).