I have a handful of MIDI tracks in RealBand 2011, rhythm section and 16th note melody. I want to move the melody track just a tiny bit ahead and behind to demonstrate a melody ahead, with and behind the beat for students to hear at a lot of different tempos.

I use to use Cakewalk to do this and it was very easy. I just can't seem to find how to do this in RealBand. Is this possible?

Just highlight from the 1st note to the last then hold the Ctrl key and drag it back or forward a 16th.

In Midi, for accuracy, you can use Edit > Slide Midi Music in either ticks or milli seconds.

"RealBand 2011"

Not sure if you can drag the tracks like solidrock suggested in 2011 version.

Lyn's suggestion allows you to highlight a section of a track(s) and slide them forward or back. Undo and Save As are your friend here (to keep existing work).

Can anyone tell me what "ticks" are?

thanks LynB!

Lyn a tick is a small portion of a part per quarter note, often labeled PPQN or PQN. Thus if you have your sequencer set at 960 PPQN and move a note one tick then you have moved it 1/960th of a quarter note.

Thanks MarioD! This could work just fine. Does RealBand have a place for this type adjustment (1/960th of a quarter note)?

Options - Resolution

It defaults to 120
However you can easily adjust to 3840 with little issue.

FWIW BiaB uses 120 also.

The higher the resolution, the more accurate any edits can be, whether audio or MIDI.
Also, recorded tracks don't get 'quantized' as much so are a more accurate reference of the performance.
In other words
If an event can happen at a finer resolution, and it doesn't get resolved to a larger chunk of time, the recording can sound much more real.

This can be explained further visually if needed.

Unless you find a reason not to, I suggest setting resolution as high as possible. The only complaint I've ever heard is the math is harder (only because the numbers are larger). The effort (thinking) can be well worth it.

While you can go to 3840, I generally use 960 ticks, which means an 8th note is 480 ticks, a 16th note is 240 ticks, a 32nd note is 120 ticks, and a 64th note is 60 ticks. That's 60 ticks to move around a 64th note a little off the beat, which seems sufficient for me. (Or carry it further that a 128th note, which is extremely rare has 30 ticks of wiggle room).

J'ai enregistré en midi un morceau a partir de mon clavier, avec accompagnement auto. Je voudrais supprimer les pistes d'accompagnement pour modifier ma mélodie (j'ai joué 2 mesures de trop du milieu de l'une au milieu de l'autre et je desire corriger avec Biab puis imprimer pour rejouer convenablement). Je suppose que Biab doit faire cela en quelques clics, mais je ne trouve pas; Merci de m'aid


er.

I have been doing MIDI recording since 1985 and I have never gone over 960 PPQN and in fact that is my default setting in my DAW. I don't know if you can set RB to default at that but others here can help. The only reason to go over that, AFAIK, is when you are doing a 100 or so tracks of a large orchestra as the data stream gets very busy.

No there are VERY important reasons to set it much higher.

Just think about it; the higher the resolution, the more exact the recording and any edits can be.

Example:
Editing audio and you want to splice two tracks together.
Or copy from a zero crossing point to another.

3840 gives you 4X the exactness of grabbing the exact sample that crosses zero as 960.

It's not just a matter of MIDI (which is still important for those who play with 'feel') but critical in audio.

I'll post a couple image examples soon (you can see yourself if you zoom in a ton on the Audio Edit window RB and try to click an exact spot in a wave form. When really zoomed in the actual cursor placement is often beside where you clicked.

It's maths. Like I said I'll post a followup to explain better, but I have to sign off soon.

Picture 1 below shows how exact I can get an edit point at 3840.
The next 2 pictures show my options right and left at 120.

Which will make a cleaner edit?
240 lets the cursor get 1/2 way to the desired spot.
480 lets it get another 'half way' closer (half of the half)
960 gets another half
1920 gets you almost there
3840 gets you as close as you can get in RB.

If you have ever played with loops and samples, getting down to as close of an edit point as you can is very important.
RB audio editing uses the click (resolution) as the edit/start/stop point. Some others do it in milliseconds, and some others do it in actual samples.
Setting RB to as high a resolution as possible harms nothing and does not stress a system. Why not do this?

Understand that if you were recording MIDI and actually hit the note when the cursor was at the position of Picture 1, if you use 120 resolution it will be recorded and played back at the cursor position of Picture 2 or 3 .. which is not as accurate or 'real' of a representation of the performance.