Lesson 1.2: Beat Making and Loop-Based Production

Estimated time: 75 minutes. Competencies: computational thinking, collaboration.

Learning objectives

By the end of this lesson you will be able to:

1. Decompose a beat into layers (kick, snare, hi-hat, bass, chords, melody) and describe each as a repeating pattern.
2. Build a 16-bar beat in a loop-based digital audio workstation using pattern, repetition, and variation.
3. Use an AI-assisted feature (loop recommendation, pattern generation, or automatic mastering) and explain what it decided for you.
4. Give a peer structured feedback on the arrangement of their beat.

Warm-up: clap the pattern (5 minutes)

Clap this pattern four times: 1 (rest) and (rest) 3 (rest) and (rest). Now say "kick" on 1 and 3 and "snare" on 2 and 4 while clapping eighth notes with your other hand. You just held three simultaneous patterns in your head. A beat maker does the same thing, but writes each pattern down so a machine can repeat it exactly.

Key ideas

Beats are patterns, and patterns are code

Computational thinking has four moves: decomposition (break the problem into parts), pattern recognition (find the repeats), abstraction (keep the essential, drop the rest), and algorithm design (write the steps). A drum loop is all four at once. You decompose the groove into instruments, notice that the hi-hat repeats every eighth note, abstract the groove into a grid, and sequence bars into a form.

The grid

Loop-based tools such as Soundtrap show time as a grid: bars across the top, instruments down the side. One bar of 4/4 has 16 sixteenth-note cells. A kick on cells 1 and 9, a snare on cells 5 and 13, and hi-hats on every odd cell is the most common pattern in popular music. Everything else is variation on it.

Form is repetition with variation

A 16-bar beat is not sixteen different bars. It is usually one four-bar phrase repeated four times with small changes: a fill in bar 4, a dropped kick in bar 8, a new element at bar 9, a pause before bar 13. Listeners hear the repetition as stability and the variation as interest. Sequencing those changes is algorithm design.

Where the AI is

Modern workstations embed AI in several places: loop recommendation (the tool suggests loops that fit your key and tempo), pattern generation (the tool proposes a drum pattern in a chosen style), and automatic mastering (the tool balances levels and loudness). Each is a decision made for you. Your job in this lesson is to use at least one, notice what it decided, and decide whether you agree.

Activity: build a 16-bar beat (50 minutes)

1. Set up. Open a new Soundtrap project. Set the tempo (try 90 BPM for hip hop, 120 for house, 105 for Afrobeats) and choose a key.
2. Layer 1: drums. Add a drum track. Using the pattern editor or a loop, build a four-bar drum pattern. Write the pattern on paper first as a grid of Xs; that is your decomposition.
3. Layer 2: bass. Add a bass loop or play a simple two-note bassline that repeats every bar.
4. Layer 3: chords or melody. Use the tool's loop recommendation to find a chord or melody loop in your key. Note what it recommended and why you accepted or rejected it.
5. Extend to 16 bars. Duplicate the four-bar phrase three times.
6. Add variation. Make at least four deliberate changes: a fill at the end of bar 4, remove the bass in bar 8, introduce a new element at bar 9, and create a one-beat silence before bar 13. Write these changes as a numbered list; that list is your algorithm.
7. Use one AI feature. Try automatic mastering or pattern generation. Listen with and without it. Record what changed.
8. Export as MP3 and name it Lesson-1-2_LastName_Title.mp3.

Pattern worksheet

Copy this grid into your notes for each drum instrument. Mark an X where the instrument plays.

Create and share

Post in the Lesson 1.2 Gallery:

• Your MP3 or share link.
• Your pattern grid for the drums (a photo of paper is fine).
• Your numbered list of the four variations.
• A rationale of no more than 75 words: what the AI feature decided and whether you kept it.
• Your one-line AI credit.

Reply to two peers using the feedback frame: "I noticed [specific pattern or variation]. It works because [musical reason]. At bar [n] I would try [specific change]."

Resources

• Soundtrap help: pattern beatmaker and loop library.
• Optional: BandLab or GarageBand as alternatives.
• Wing (2006) on computational thinking, for the definitions used above.

Reflection prompts

1. Which of the four computational thinking moves felt most natural, and which was hardest?
2. What did the AI feature change that you would not have chosen yourself?
3. How would you teach the pattern grid to a middle-school general music class without a computer?