A smaller playing field
An eight-bar loop can support a remarkable amount of procrastination. Change the snare, audition another bass, open a different synth, and the arrangement can remain exactly where it was an hour ago. A session with fewer available moves can make each choice easier to hear.
MusicTech’s October 6 My Forever Studio feature on Kaelin Ellis is framed around video games and nostalgic gear. Borrowing that premise, the exercise here uses the bounded space and repeatable actions of a game, with equipment you already know.
The target is a rough arrangement with an audible change of intensity. A DAW will do. A sampler or sequencer that can save different patterns can also work, provided you have a way to record the result. There is no particular vintage instrument to track down before starting.
Define the next move
Before opening the sound browser, write one sentence about the track’s immediate job. Perhaps a verse needs to make the chorus feel bigger, or a rhythm needs to carry a minute without another instrument arriving. Choose something you can judge by listening.
Then set a boundary for this pass. Keep the same tempo and harmony, for example, while you work on density. Use sounds already loaded in the project. Give yourself a fixed period of time if that helps, but avoid spending the session managing a complicated points system.
A workable objective might read: build a sparse section and a fuller section from the same loop, with one convincing transition between them. That leaves room for taste. It also tells you what to put on the timeline when you sit down, instead of presenting you with an empty project and several thousand presets.
Assign the voices
Make a compact palette of musical roles. Start with a rhythmic anchor and a low part, then choose one foreground sound. Add a supporting texture only if it has a specific job. This is a temporary limit for the session, so keep any existing tracks you mute available for later.
A role can contain more than one sample. A drum kit does not need to become a single hit to satisfy an arbitrary rule. The useful restriction is on competing ideas: if a new part arrives, decide where it belongs and whether something else should step back.
Before loading another instrument, try a register change or a shorter note. Transpose the foreground phrase up an octave and listen to whether its notes become easier to follow over the bass. Undo it if the higher register makes the phrase feel thin. Leaving rests can expose a rhythm that was already doing useful work underneath.
There is no requirement to use chip sounds. An acoustic recording can serve the exercise just as well as a synth. Save the palette so the next session begins with playable material.
Write intensity states
Borrow the idea of music changing state as activity changes. Take the same short passage and make a low-intensity version, then a busier version. Keep the tempo and the length of the harmonic cycle fixed while you work. Those common dimensions make it easier to move between the versions.
For the quieter state, remove selected drum hits or lengthen the gaps in the lead. For the busier state, restore some motion. A higher countermelody may provide enough lift without adding more low-frequency material. Work with the sounds already in the palette.
Compare the two sections at roughly similar playback levels, then restore their intended dynamics. The temporary level match helps you hear whether the fuller passage gains useful movement as well as volume. Listen for new parts obscuring the main phrase.
Now place the versions next to each other on the timeline. Let a sustained note cross the boundary, or leave a brief gap before the fuller passage. Check the tail of any reverb at the join. You are testing whether the listener can follow the change, including the awkward half-second where one section becomes another.
Keep recoverable checkpoints
Save a version before changing the arrangement. Give it a name that records the decision, such as `sparse-verse` or `open-chorus`. Use your system’s project-copy or versioning function if available, and keep the associated audio organized with the project. An experiment should not require an afternoon of file hunting to recover.
A short stereo export is useful, too. It gives you something to compare without reopening every instrument. Keep the transition in the export. The awkward join may be the problem, even when both sections sound convincing on their own.
Change one musical variable for the next pass. Shorten the bass notes, for instance, and leave the sound itself alone. Then compare. If you change the patch and the rhythm at once, you make the result harder to diagnose.
Keep the previous version until you have made that comparison. A note beside the new version might read: try the shorter bass under the fuller drums. That is enough information to resume the experiment without replaying every abandoned variation.
Turn the map into a track
Once the two states and their transition work, build a rough full-length arrangement. Reuse sections where repetition feels appropriate. Leave a placeholder for a missing vocal or instrumental passage instead of opening another library to fill every empty space.
Listen from the start without touching a control. Make a short note at the moment your attention drops or the next section feels premature. Work on that point first. If the second repeat drags, try shortening it before adding another layer. If a transition rushes past, give the outgoing phrase enough room to finish and listen again.
The limits can loosen after this pass. An extra instrument may be exactly what the song needs. Keep the rough arrangement and try that addition in a new version. Export a reference that plays from the opening through the final section, including any untidy transition. Put the next-edit note beside the project so tomorrow’s session starts at a specific bar.
Written by Marvin Cavanaugh
Comments
No comments yet.