The project tempo is set to the default 120 PBM. But the actual tempo of the material is about 1/2 that I think. I created my MIDI part and input my taps. Since the DAW tempo was 120 and my music is about 60 PBM, I guess I was inputting taps in 2/4 time. No problem. So when I select the āMerge tempo from tappingā option, I select 1/4 notes as my taps. It then always says āTempo out of range.ā And the resulting tempo is half of what it was ā quite slow ā and my taps arenāt lining up anywhere close to the grid.
It may help to put the tempo track at a rough approximation of the songās tempo before you get started - the closer the better in my experience, to help Cubase out.
I ultimately found that my tapping didnāt give results as good as I wanted (I tapped āwith emotionā rather than strictly on the beat), and that I needed to do the audio warp thing anyway to tidy things up afterwards. So, nowadays I just go straight to the audio warp.
I guess then that since I didnāt bother setting the project tempo to something even close to my actual tempo Iām screwed
I suppose I could export the audio of each track, start a new project with a tempo closer to what Iām actually doing, then re-import the audio, and go from there
I was busy today, but tomorrow Saturday Iām going to take another look at it. My gut tells me the problem is that my project tempo = 120 BPM is too far from my actual tempo as defined by my taps ( ca 60 BPM) and the app canāt handle it. I bet my workaround will, uh, work
Doug, it doesnāt matter what the fixed tempo was set at. I think you may be tapping 1/8 notes. I just opened a project, in Cubase 5.5 which I donāt think will matter, and tapped 1/4 notes, merged it to the tempo track then did the ā1ā of every bar. Both worked just fine. I chose in the dialogue ābegin at bar startā and ā1 barā for the 1 count and 1/4 for the 1234 tapping. Both worked fine.
One thing you will have to do is all your previously recorded tracks will all have to be in linear time base mode so when you change the tempo, it will not alter their positions. This is the button on every track in the arrange window that has a note sign and when you click it, it will change to a clock sign. You want to see the clock.
After you merge tempo from tapping, your midi event taps will not be in line with the grid. If you turn your click track on, that should be beeping in sync.
I found it is best to do 1 bar taps because it makes tempo track editing easier, but if there is excessive tempo drift within the bar, youāll have to do 1/2 or 1/4.
Oh. I thought that was the whole point of doing this. I donāt need a click, I can easily play along with whatās already recorded just by feel. But I wanted to output a score of one of the tracks, and having a rough semblance of grid was the only way to do this without massive editing/tweaking.
Who would need/want a click for a piece that is rubato?
I am tapping 1/4 notes, at least as I define the tempo of the tune (whether itās 4/4 or 2/4, Iām still tapping on every beat). I donāt understand what you mean by āIā¦then did the ā1ā of every bar.ā
Also, didnāt know all the other tracks needed to be in linear mode. I donāt think the manual says anything about it? But I think THATāS my problem here, because when I do this function, it IS changing their positions, significantly
When I wrote that I did 1/4 note tapping ā1ā-ā2ā-ā3ā-ā4ā per measure. The other way was ā1ā pause 234 per measure ā2ā pause 234. and so onā¦
Does that make sense?
I think you figured it out though that the time base was most likely your problem.
What I meant by that was, the midi event you made to create a tempo trackā¦ That midi tempo tap event, once you merge tempo with it will no longer work as a click. It will be out of sync. Donāt know why, but that is just my experience with it. There may be a way to keep it, but I donāt know.
Edit: just to add. I have no idea how this will affect a score. I did it in a project full of audio files.
Oh! That is whatās throwing me off ā the tapping part isnāt lining up with the grid and itās not in sync with the audio, eitherā¦ I didnāt think to check the click. I bet itās working afterall
i find if you start with a fresh Cubase project and do the merge tempo from tapping, that the āout of rangeā eror doesnāt occur. Dunno why.
And this is useful for fixing audio files that are unsteady tempo-wise:
Open a new CPR and import the audio fileā¦
define the tempo of the file/project based on tappingā¦
bounce the audio file (which I believe sets the tempo as part of the definition for the file?)ā¦
change the file to musical mode in the audio poolā¦
adjust the tempo of the project per tasteā¦
export the mix
import the mixed file into my original project