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.
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.
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.
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.
@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.
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.
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…
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?
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.
Personally I never went 13. There were three issues why: Graphic design, VSTi undo gone, Beat Calculator gone.
They worked on the graphical stuff and I took that off my personal list of reasons why not to update to 13.
VSTi undo - looks like this will not come back for a long time. Somebody has hinted at underlying technical issues and that usually means 10 years or more in the Steinberg cosmos.
Beat Calculator - if they want to send us back to the 80’s maybe the next step will be to remove audio tracks from the program and tell us to use tape machines instead.
It is the first time since the 90’s that I seriously started to look at the competition in case I feel the need to move away from Cubase.
I feel you. Although I personally don’t feel they improved the GUI enough to my personal satisfaction. To me it’s an eyesore where everything is presented with the same intensity. Another dealbreaker is the introduction of static icons in the Mix Console that inhibits seeing I/O names et al if the channel width is small.
