Cubase Pro 14.0.32 Bug Report: Tempo Detection, Virtual Keyboard, and Line Tool Issues

Cubase
1

Hi Steinberg team,

I’d like to report several issues I encountered in Cubase related to tempo detection, virtual keyboard, and line tool behavior.

Issue 1: Tempo Detection & Time Warp Function with Non-44.1 kHz Sample Rates

Issue Summary:
When using the Tempo Detection feature in projects with sample rates other than 44.1 kHz, the Time Warp algorithm fails to properly detect and adjust the tempo when dragging bars forward or backward. This functionality works correctly only at 44.1 kHz sample rate.

Steps to Reproduce:

  1. Create or open a project with a sample rate other than 44.1 kHz.
  2. Use the Tempo Detection feature with Time Warp to adjust bar positions.
  3. Observe that tempo detection does not update correctly.

Expected Behavior:
Tempo Detection and Time Warp should function properly regardless of the project’s sample rate.

Actual Behavior:
Tempo Detection only works correctly at 44.1 kHz; other sample rates cause the feature to malfunction.

Issue 2: Virtual Keyboard Note Output Incorrectness

Issue Summary:
On the Virtual Keyboard, pressing the ‘/’ key does not produce the expected E note. Instead, no sound is generated. Conversely, pressing the ‘;’ key triggers an E note rather than the expected Eb.

Steps to Reproduce:

  1. Open the Virtual Keyboard.
  2. Press the ‘/’ key and observe the output.
  3. Press the ‘;’ key and observe the output.

Expected Behavior:
‘/’ key should trigger the E note, and ‘;’ key should trigger the Eb note.

Actual Behavior:
‘/’ key produces no sound; ‘;’ key produces an E note.

Issue 3: Line Tool Sine Wave Behavior with Variable Tempo

Issue Summary:
When creating sine wave curves with the Line Tool, if the tempo is constant, the waveform aligns correctly with bar or beat divisions. However, with variable tempo (e.g., classical music), the initial bar/beat unit is converted to absolute time units, causing subsequent points to be recorded independent of Musical Time, resulting in inaccurate alignment.

Steps to Reproduce:

  1. Create a sine wave curve using the Line Tool in a project with variable tempo.
  2. Observe how the periodicity is recorded over time.

Expected Behavior:
The sine wave should maintain alignment relative to Musical Time regardless of tempo changes.

Actual Behavior:
After the initial bar/beat reference, points are recorded by absolute time units, disregarding musical tempo.

Thank you for reviewing these issues. I hope this helps improve Cubase’s stability and functionality.

Environment:

Cubase version: [Cubase Pro 14.0.32]
OS: macOS [Sequoia 15.5]

Additional Request Regarding Chord Track Functionality:
In Cubase up to version 13, it was possible to input chords automatically on the Chord Track by pressing the TAB key to move bar by bar. Additionally, clicking on the chord icons allowed users to type chords directly using the TAB key for navigation. These useful features appear to have been removed in recent versions. I would appreciate it if Steinberg could consider restoring this functionality to enhance user workflow.

Best regards,
Mask & Revelation

2

Hi,

I would recommend to make a dedicated thread for every single issue to avoid a mess.

  1. What language is your system set to? Which language do you use in Cubase? What language (keyboard layout) is your computer keyboard set to?
  2. Does it work different way for MIDI CCs?
3
  1. US English
  2. I didnt mention about Midi Cc
4

The issue number one has been there for years and I don’t think it will ever be fixed. In fact, the entire tempo detection feature is completely useless. It often fails detecting tempo even of a steady drum part, not to mention anything slightly more complex.

2 Likes
5

Issue 3: What are you drawing using the line tool?

6

Volume curve automation

7

Hi,

  1. When drawings the Sine, is the Grid set to Bars+Beats?
8

Bar, Beats Sir.

9

Hi,

Does it mean the nodes are not visually aligned with the Grid?

10

yes not musical (grid), on various tempo

11

I made this video to help you understand, and it’s also something that I’ve been publicizing since I was a Cubase 12 a long time ago

12

I made this video to help you understand, and it’s also something that I’ve been publicizing since I was a Cubase 12 a long time ago

13

I made this video to help you understand

14

Hi,

Visualy it’s clearer, if you use the Square tool instead of the Sine.

If I understand you correctly, you would expect, the sine length is always the same, because the Grid is set to Bars+Beats. So if the length of the Sine is 1/2, it will alwas be 1/2, independent on the tempo. But it’s not the case, it’s more time-base, so if you change the tempo, the length remains time-wise but it’s not in sync with the music anymore.

Do I undesrtand you right?

15

“That’s correct — it should function based on musical time, but I was pointing out that it doesn’t behave as expected when there are tempo changes.”

16

Thank you for the video!
Try this, before drawing automation using the sine wave tool, change the Ruler Mode to “Time Linear”.

image
image496×232 10.8 KB

17

I’ve tried that approach, but the issue still persists. Fundamentally, I believe the Line Tool needs to interpret musical time. Currently, it seems to generate its curve based on absolute time rather than musical time, applying the initially defined unit over fixed time intervals rather than adapting to tempo changes.

1 Like
18

It is particularly inconvenient when editing MIDI CC messages from a musical perspective. This is because, musically, it’s far more common to shape classical-style dynamics such as crescendos and decrescendos using period sine waves based on bars and beats, rather than absolute time units. The method you suggested takes an approach fundamentally opposite to one based on musical time algorithms, and even as a workaround, it is difficult to apply effectively.

1 Like
19

You’re right!
I was tricked by how changing Ruler Mode changes the display.

Edit:
I suppose one workaround it to temporarily disable the Tempo Track when drawing the automation.

1 Like
20

There is a traditional Korean proverb that translates roughly as “peeing on your own frozen foot”—a temporary fix that ultimately worsens the problem. I believe such an approach is not suitable for a long-established and respected application like Cubase.

In fact, I have been raising this issue for nearly a decade. There was even an occasion when representatives from Steinberg headquarters visited Korea, and I had the opportunity to speak with them directly about this matter. It’s disheartening that the problem still remains unresolved.

1 Like