Rests and silence in RTTTL: using pauses well
The p in an RTTTL string is easy to ignore, but rests shape your phrasing, cost bytes just like notes, and are how you stagger motors in a multi-motor arrangement.
For a long time I treated rests as leftovers. Whatever silence the converter put in, I left in, and whatever it didn't, I didn't miss. Then I tried to squeeze the opening of a march onto a whoop, ran out of room, and noticed that a big chunk of my string was p.
So this is a post about nothing. Literally.
How a rest is written
In RTTTL a rest is the letter p with a duration in front, like a note without a pitch or an octave. 4p is a quarter rest, 8p an eighth, 2p a half. Leave the duration off and it uses the default from the header. A dot works the same as on notes, so 4p. is a dotted quarter rest. (The RTTTL guide for musicians covers the rest of the syntax, pun not intended.)
call:d=8,o=5,b=140:c,e,g,p,c,e,4a
That p in the middle is an eighth of silence between the two halves. Take it out and the phrase runs together into one blob. Put it in and it sounds like a question and an answer. Musically that's the main job of a rest: it gives a phrase room to breathe. A short tune with no gaps at all tends to sound rushed to me, even at a slow tempo.
Rests aren't free
On Bluejay a rest costs about the same as a note, roughly two bytes out of a 128-byte budget. (The byte budget post explains where that comes from.) So silence eats into your ~62 notes.
The converter counts them the same way. Its "max notes per output" limit counts every token in the string, and a p is a token. Set the cap to 62 on a song with lots of space in it and you'll get fewer actual notes than you expected. That one caught me out the first time.
Some ways to spend less on silence:
- Merge rests.
4p,4pis two tokens,2pis one. The converter writes each gap as a single rest, but hand-edited strings often end up with doubles. - Don't end on a rest. Trailing silence does nothing, the tune just stops anyway. The converter already trims it, but strings you've typed or pasted from elsewhere often have one.
- Cut the intro. Plenty of MIDI files start with a bar or two of nothing (or of drums you've deselected), and that becomes a leading rest. Use the time window to start right on the first note.
The "skip very short rests" option
MIDI files are full of tiny gaps. A pianist lets go of one key a hair before pressing the next, and the file records it. If every one of those became a p, a simple melody would turn into note, rest, note, rest, burn through the budget and sound choppy on top of it.
That's what the "Skip very short rests" checkbox is for. It's on by default and drops rests shorter than a 64th note, so legato notes stay joined the way they were played. I leave it on nearly always. The only time I switch it off is for very staccato material where I want every gap, and even then I usually end up tidying it in the editor instead.
Rests for staggering motors
This is where rests get fun. When you split a song across motors, every motor starts at the same moment, the instant the battery goes in and the ESCs power up. So if you want a voice to come in later, the only way is to start its string with a rest:
m1:d=8,o=5,b=120:c,e,g,c6,4e6
m2:d=8,o=5,b=120:2p,c,e,4g
Motor 2 waits a half note, then enters. That's how canons and call-and-response arrangements work on a quad, and the Pachelbel post leans on it heavily. The converter does this for you when a track starts later than the others. It's still worth knowing the leading rest is there, because it costs bytes on that motor. A voice that waits four bars to come in has spent part of its budget doing nothing.
Something I'm not sure about: how tightly separate ESCs stay together over a long piece. They start together, near enough, and over the few seconds of a typical startup tune I haven't heard them drift. I wouldn't bet on it for a long, tightly interlocking arrangement, though.
Next on my list
I've been wondering whether a deliberate pause right before the last note, a held breath basically, makes a startup tune feel more like a "ready" signal. Something like c,e,g,4p,2c6. My first go felt a bit dramatic for a toothpick. I might try it on the 7-inch instead, where dramatic is kind of the point.