Beat Calculator in Cubase 13

Yes, I know there have been various other threads on this topic.

But they have all ben closed with a notice of resolved.
I beg to differ, this has not been resolved at all, ignored would be more accurate.
I downloaded the latest update but no difference at all, it’s still not there.

The notion that tap tempo replaces the useful beat calculator function is laughable, it’s virtually impossible to get a truly accurate tempo of a sample of section of music in this way.

I’m seriously thinking of downgrading to an earlier version, there are very few useful improvements in 13 for me.

Very disappointed.



Are you aware of the changes, which were been made from Cubase 13.0.10 to 13.0.20 in this area, please?

I have 13. 0.21 & I can’t see any differences on this issue.

I see there is tap tempo on the transport panel with it’s various modes. None of these replace beat calculator. There’s no way that mouse clicks on tap tempo can ever be as accurate as beat calculator.

Is beat calculator hidden somewhere else?


Have you tried the ‘Tempo Detection’ facility? Sounds more like what you’re describing in your initial post.

I’m familiar with tempo detection, that’s a different thing entirely.

There are many scenarios where beat calculator is useful, here’s just one.

I have a track, that may have a constant tempo or may vary with a tempo track with changes.
I have a sample or sound that I want to add, I would usually import it, check it’s tempo accurately with beat calculator , go into the pool, put the tempo of the sample in, put it to musical mode & hey presto it’s in time with te track. Or I cut it up & use the time stretching object selection tool.

This process doesn’t affect the tempo of the track if I don’t want it to or it could if I chose set tempo to start etc.

But it does.

Tap Tempo

Display only: Displays the tapped tempo without applying any tempo changes.

The Tap Tempo feature gets new override options. In the new Tap Tempo Mode pop-up menu you can find the following options:

Automatic: The same as before (default).

Insert tempo event at selection start

Insert tempo event at last playback start position

Insert tempo event at cursor position

Set project tempo, which Sets the rehearsal tempo if the tempo track is disabled. Otherwise, it changes the initial tempo event of the tempo track.

1 Like

I get that but it doesn’t alter the fact that tap tempo using a mouse can never be as accurate as the beat calculator.


Giving loads of new options for a substitute that is not as good as the original it replaced is not a solution.

I’m not alone here.

You guys should admit that you dropped a bollock here & bring it back.


Note that you can always have “Tap Tempo” assigned to a shortcut. I see Shift+Space as a default:

Now, when it come down to the algorithm used to calculate bpm, I did see threads stating that is not as accurate as the “beat calculator” option, I never checked it, but sure this can be true and in need of an update/rework.

1 Like

@m.c @viramundo is not using the feature in a way that tapping is useful.

@viramundo If you would be specific about what you mean it would be helpful.

Though you didn’t say so explicitly, I understand you to be referring to selecting a range, and getting the bpm it needs to be, such that it ends up at the same tempo as the material your adding it to.

This is the feature that’s missing, Correct?

I will write in the n-th topic since the Cubase 13 update:

The old Beat Calculator consisted of two different items:

  • beat calculator
  • tap tempo

Tap Tempo is present in C13, the actual beat calculator part was removed.
The beat calculator just used a simple formula
Amount of beats in selection * 60[s] / duration of selection[s]
and was a quality of life = speed of work enhancement.

There are workarounds, the fastest being to use a calculator and tap in the numbers yourself. Like we did in the previous century. {sarcasm} I appreciate Steinberg’s attempt at the retro wave. {/sarcasm}

It is just a small feature but to me this is a mindless decision by the responsible Steinberg staff. And I am equally disappointed by how @Martin.Jirsak decided to handle this topic over the last few months. Apparently, Martin, you have never used this function as you displayed absolutely no knowledge of what we others were even talking about. And, even after all my explanations, you’re first reply in this topic is still trying to put a customer on their backfoot.

It is mindblowing to me how Steinberg and a forum moderator & certified Steinberg trainer can display such a high level of ignorance over such a small function.


Yes, assigning it to a shortcut could improve the accuracy.

But it can’t be as accurate as beat calculator.
You’ve you’ve got the human inaccuracy of tapping precisely for a start, there’s no way that can ever be as precise.

Yes, Steve, I think that’s basically what I’m saying.

Bravo Johnny, you put it way better than I did.

Brilliant summary of the usefulness of the Beat Calculator. Let’s live in hope that this function can be restored WITHOUT another paid upgrade if at all…

1 Like

Given that I’m new to Cubase (not DAWs) and that I don’t use loops for anything because I work within a framework where I know the bpm and tempo increases, I’m a bit at a disadvantage in understanding the issue. I’ve also never used beat calculator. BUT…

I did find this earlier (2016) video and thought it might be useful to include here as I’ve had to do the same kind of time shifting in Studio One, Digital Performer, etc.

Does this remotely address the issue or is your situation more related to pulling loops into the project?

Yes, I’m familiar with tempo detection.

That’s fine when you’re starting from from beginning & that’s 1st audio you import.

But when you import various loops & clips it’s not so useful especially bearing in mind it doesn’t even work with clips/loops under 7 seconds in length.

all this has been solved albeit, the old way feels quicker at first and is probably the way your brain likes to think about things.

Now, you just have to do it the opposite way around, select left and right locators to the current length of time to be changed. (say bar 4-16 on the dot) now select an audio, midi event, cycle marker or anything similar that IS the length you desire (you’ll always have this because thats what this task is, obviously you’ve got a location in mind and marked with a start of a part or marker etc) now choose Audio->Advanced->Set Tempo From Event. Before you knock it, Im finding this kind of quicker now im used to it because these commands are script/PLE able and i;ve got a shortcut for it now. Is good.


Unfortunately, this is useless while doing the same with Midi parts freely recorded and tempo detection tools just make a series of tempo track items at various speeds that you need to edit out.

I think we should not hold our breath. It’s obvious they don’t care or they would have put it back in or clearly said they plan too.

Personally reverted to 12, can still use the new plug-ins and keep my workflow but completely sad being a Cubase user since Score in the 90’s and have lost interest in any further versions over such a small basic thing.