|
|
Post by swurveman on Feb 25, 2018 8:34:14 GMT -6
Often, I have bands that want to record the same song at different tempos inside the same project window. Is there a way to set up Cubase, so that when I adjust the tempo on the Transport Bar of the second take of the song at a different tempo than the first take, it doesn't effect the tempo/grid relationship of the first song?
This is something I have never quite fully understood and would appreciate anybody's information/feedback
|
|
|
|
Post by popmann on Feb 25, 2018 12:09:06 GMT -6
No. Logic can. I mention because I thought that was a kind weird option to have multiple tempo maps for the same material.
But, the easy way to achieve that is not to use "takes", but simply use the project timeline linearly. Tempo track at 100bpm at the beginning , set it to change to 102bpm or whatever at the 6min mark(where the song is under that obviously) and put a marker there. You can literally toggle from one to the other with the NumPad's direct marker access.
You're likely trying to solve a problem you are causing--by forcing a musician to choose which computer tempo is "right".....have them play the song without a click like they do every night. You can easily map it after if you need it mapped.
|
|
|
|
Post by drsax on Feb 26, 2018 13:30:44 GMT -6
No. Logic can. I mention because I thought that was a kind weird option to have multiple tempo maps for the same material. But, the easy way to achieve that is not to use "takes", but simply use the project timeline linearly. Tempo track at 100bpm at the beginning , set it to change to 102bpm or whatever at the 6min mark(where the song is under that obviously) and put a marker there. You can literally toggle from one to the other with the NumPad's direct marker access. You're likely trying to solve a problem you are causing--by forcing a musician to choose which computer tempo is "right".....have them play the song without a click like they do every night. You can easily map it after if you need it mapped. Yeah - with cubase this is the way to do what you’re asking. The tempo track is also useful for time signature or tempo changes in a single song. Or for ritards and accelerandos |
|
|
|
Post by swurveman on Feb 26, 2018 16:26:11 GMT -6
No. Logic can. I mention because I thought that was a kind weird option to have multiple tempo maps for the same material. But, the easy way to achieve that is not to use "takes", but simply use the project timeline linearly. Tempo track at 100bpm at the beginning , set it to change to 102bpm or whatever at the 6min mark(where the song is under that obviously) and put a marker there. You can literally toggle from one to the other with the NumPad's direct marker access. You're likely trying to solve a problem you are causing--by forcing a musician to choose which computer tempo is "right".....have them play the song without a click like they do every night. You can easily map it after if you need it mapped. Thanks popman. So, do you have any advice of what to do retroactively? I recorded in Musical track time base and when I changed the tempo at the start of the second song, the 1 of the beat of the kick drum (for example) is not on the 1 of the bar of the grid. I'd like to quantize the drums, but the hits are way off due to the grid alignment. So, I'm not sure what, if any, I can do from a quantization aspect. Also, when you record without a click, how do you align the 1st and 3rd beat of the kick drum (2 and 4 of the snare etc) to start the song to the grid so that you can quantize all the drums like in this tutorial? |
|
|
|
Post by swurveman on Feb 26, 2018 16:27:57 GMT -6
No. Logic can. I mention because I thought that was a kind weird option to have multiple tempo maps for the same material. But, the easy way to achieve that is not to use "takes", but simply use the project timeline linearly. Tempo track at 100bpm at the beginning , set it to change to 102bpm or whatever at the 6min mark(where the song is under that obviously) and put a marker there. You can literally toggle from one to the other with the NumPad's direct marker access. You're likely trying to solve a problem you are causing--by forcing a musician to choose which computer tempo is "right".....have them play the song without a click like they do every night. You can easily map it after if you need it mapped. Yeah - with cubase this is the way to do what you’re asking. The tempo track is also useful for time signature or tempo changes in a single song. Or for ritards and accelerandos Thanks drax. If you have any thoughts about my follow up questions to popman, I'd appreciate your feedback. |
|
|
|
Post by popmann on Feb 26, 2018 19:03:31 GMT -6
No. Logic can. I mention because I thought that was a kind weird option to have multiple tempo maps for the same material. But, the easy way to achieve that is not to use "takes", but simply use the project timeline linearly. Tempo track at 100bpm at the beginning , set it to change to 102bpm or whatever at the 6min mark(where the song is under that obviously) and put a marker there. You can literally toggle from one to the other with the NumPad's direct marker access. You're likely trying to solve a problem you are causing--by forcing a musician to choose which computer tempo is "right".....have them play the song without a click like they do every night. You can easily map it after if you need it mapped. Thanks popman. So, do you have any advice of what to do retroactively? I recorded in Musical track time base and when I changed the tempo at the start of the second song, the 1 of the beat of the kick drum (for example) is not on the 1 of the bar of the grid. I'd like to quantize the drums, but the hits are way off due to the grid alignment. So, I'm not sure what, if any, I can do from a quantization aspect. Also, when you record without a click, how do you align the 1st and 3rd beat of the kick drum (2 and 4 of the snare etc) to start the song to the grid so that you can quantize all the drums like in this tutorial? I don't quantize anything-certainly not audio. I align nothing to grids. But, the basic principle remains that you need to tempo map the existing audio BEFORE manipulating it at all....to do that, you need the audio in linear timebase. You can actually put them into that mode after, retroactively. You can use the auto detect to pick up the tempo from transients, but, in the end, I always found it quicker to set the bar lines (letting the app subdivide for a musical grid)....using the Warp tool. You want the bar lines defined--not smaller subdivisions....but, you need to make sure it's the musical PULSE--not where some transient is. Musical mode is not useful for audio to me in unless that audio was BOTH cut to a click track and that tempo is specified in the file in the pool. Unless it fits both those criteria, as you've found--all it does is move start times of regions, which isn't terribly useful. |
|
