Let’s go back to 80’s and use the pocket calculator 
Formula:
(Amount of beats of selection * 60) / Duration of selection = BPM
You’ll have to count the beats.
The duration of the selection can be read if the ruler is switched to Seconds.
Yes, we’re back to manual. Only the tears are real.
Damn, I was choosing Cubase for years because of the features this program had over the rest of the DAWs on the market. ONE of them was actual way of defining the tempo of a project just simply by tapping it with a spacebar, NOT changing the project tempo. And now Steinberg ignores the votes for the return of the Beat Calculator, thought this is one of the most necessary features - to actually detect tempo of a project, when you receive it in multitrack. The other thing about the inserts in Inspector. Damn, I have no excuse for that. Why not just add an OPTION to CHOOSE as it was given in the mixer window. For those who want 1 god damn insert and a whole empty window - let 'em choose the option, but the way it works now is just awful. I could swallow the design… I can really try to take it as it is now, though it is ugly as ****, but why removing the features that worked properly?
Steinberg, please bring back Beat Calculator.
Honestly this and new GUI are holding me back from Upgrading Nuendo. For me, it`s not about some new shiny plug in you decide to include in a new version which brings me literally nothing but about having the trusted set of tools I use on regular basis. Apart from that, if you want to be really innovative: open your API for User generated scripts (there is a new thing called generative AI, one can build scripts with, you know…) And integrate text based audio editing. This would be innovative. Destroying GUI and retiring Beat Calculator is not.
But you know what… if Steinberg would open its API to user generated scripts like ReaScripts API in Reaper, this feature could be probably implemented with a few lines of code, some clever user would write and post for free. Oh wait… Pro Tools implemented its Scripting SDK exactly for that reason as well. And honestly with the help of Chat GPT/ GitHub Copilot it was never THAT easy to write and understand some basic code.
For all beat calculator fans out there.
I opened a new post with detailed description why the current ways to detect tempo don not replace the beat calculator functionality but I framed it slightly different.
Please make some noise over there so Steinbergians understand why we are missing the old beat calculator so much
link?