Marcelo Quinones

I wish you can implement a Record Beats function to record tempo changes in real time by playing beats on a keyboard MIDI controller keys!!! That will basically make a breeze to adjust tempi from digital audio to synchronize it with the measure/beats of a empty MIDI sequence in order to make a MIDI sequence out of a nice syncronized audio file on top effortlessly!

2 step procedure. Step 1 will be Recording or inserting MIDI or Audio. Step two will be recording the tempo and or fine tuning the tempo changes depending of it is MIDI or audio.

I respectfully disagree. It is not the same. In MOTU you can record the tempo track while you listen to the MIDI or audio recording and the software will make the appropriate changes and recordings in real time not after you recorded all the beats and then tell the software to process be “fit to improvisation”. It is really real time tempo recording.

I’ve been using Cakewalk since 1990. The fit to improvisation is not the same as record a tempo track in real time. Look at this feature from MOTU’s DP 10. It is non-existent in Cakewalk: (This text below was taken from MOTU’s DP 10 Owners Manual-All rights reserved for the authors and creators of the software and manual as well) ”Tap Tempo is Digital Performer’s real-time tempo control feature. Tap Tempo lets you slave Digital Performer to a tap entered from any MIDI controller before, during, or after the recording of your sequence. You can ‘conduct’ an existing sequence by tapping the tempo, complete with accelerandos, ritards, and rubato passages; Digital Performer will follow precisely. More importantly, you can record your tap into the Conductor Track for use in subsequent playback and recording. Tap Tempo can be used during virtually any stage in the creation of a sequence. For example, if you have acoustic music on tape, two completed tracks in Digital Performer, and three more Digital Performer tracks to record, you can ‘teach’ the two existing tracks to follow the prerecorded music. Your remaining tracks will be recorded into a sequence that has all of the temporal nuances of the prerecorded music. Preparing for Tap Tempo The following are general points to consider when preparing to use Tap Tempo sync. Establish a meter When slaving to Tap Tempo, Digital Performer must know how many of your taps to group as one measure. Before recording or playing back a passage in Tap Tempo mode, make sure you’ve entered the correct meter using the Change Meter command (Project menu>Conductor Track>Change Meter). Establish a metronome click value Your taps correspond to the current metronome click value, specified using the Change Meter command. For example, the tempo of a 4/4 passage can be tapped and expressed in whole notes, one tap per measure, or in sixteenth notes, sixteen taps per measure. Each tap becomes a tempo change event, so the smaller the click value, the higher the resolution of the resulting tempo map. Choose a tap source You can use any standard MIDI event as your tap source. Digital Performer will interpret this MIDI event as a tap whenever it occurs on the specified input channel. If you plan to record music while slaved to Tap Tempo, choose a combination of MIDI event and channel that won’t be needed in the musical passage. For example, let’s say you’re tapping C3 on a controller keyboard, transmitting on channel 1. The result? Any other C3’s transmitted on the same channel will not be recorded. Again, this is only true for C3’s transmitted on channel 1. C3’s transmitted on other channels will be recorded normally. Note that although pitch bend and controller events are acceptable as tap sources, the most common controls for sending them (wheels, joysticks) make reproduction of a single, specific value difficult. For example, to define your tap you enter a pitch bend value of 392 using a pitch bend wheel. To slave Digital Performer, you’ll need to generate values of 392 or higher — you send a 392 value by going precisely to it, but also by going past it. That much is easy, but remember that Digital Performer will treat only the events with 392 values as taps. All other values sent by your mod wheel will be recorded and interpreted as normal pitch bend events. This makes bend and controller events less practical tap choices than events with precise triggers or more limited values, such as a note or a Controller #64 (sustain pedal) event. MIDI beat input data Source Choose the MIDI device you will be tapping from in the menu provided. Event Specify the MIDI event you wish to use as a tap. Tab to the Event box or click in it, then enter a MIDI event from any MIDI controller connected to the specified port (play a note, tap a sustain pedal, etc.). The event appears, highlighted; click on the highlighted event if you wish to change it. You can use any standard MIDI event as a tap source. Countoff beats Specify the number of times you wish to tap as a countoff. The default number of sync countoff beats is four, but the countoff can be any number between 1 and 127. If you enter a number outside this range, the computer will beep when you click the OK button and the number will be highlighted. If this happens, click on the highlighted value and enter a new one. Using Tap Tempo mode After you have made the Tap Tempo settings as needed, follow the steps explained in “Using Tap Tempo” on page 959.

Hey! There is something else very important that I still need Cakewalk to implement. I mean, when I want I to make an accelerando, ritardando, rallentando, etc., I need the specific function of recording a tempo map with my MIDI keyboard or computer keyboard by tapping the keys and recording a natural tempo change. It is still missing in Cakewalk and in other software is being implemented for many years (since the late 80’s by MOTU Performer). Any ideas? To Cakewalk by Bandlab: Please elevate and upgrade the features of Cakewalk comparable to other professional DAW’s like Digital Performer.

Thank you!!

Thank you!!! Any comments about the DRUMSPLI.CAL malfunction in Cakewalk?

No. Didn’t know it exists...any tutorials?

Remember that I sent a request for you to work with Real Time Tempo Track recording to make tempo recording more natural and better to adapt to record better and more accurate tempo tracks along with digital audio.

Please fix a bug that is being around for a while when trying to use the CAL drumspli.cal to split percussion or drum track notes into multiple individual tracks with Cakewalk Bandlab 2019.7. It doesn't split the tracks correctly... The CAL that I sent will separate all GM drum set from one single track to multiple tracks and generate the drum sound names for every track automatically. It was working in previous versions of Cakewalk but not in the latest versions. Please fix it. DRUMSPLI.CAL