---

Teacher Guide for Drum Sequencer Prompts

---

1. Kick It Off

Student Prompt:
“Turn on the Kick drum only at steps 1, 5, 9, and 13. This is called a four-on-the-floor beat. Press play and listen—why do you think this pattern is so common in dance music?”

Teacher Notes:

• This pattern repeats every 4 steps, which helps students see how music often relies on loops.
• Emphasize regular repetition as a concept in both coding and rhythm.

Extension Questions:

• “If each step is like one ‘slot’ in an array, which indices are being set to true for the Kick row?”
• “What would happen if you shifted the kicks to steps 2, 6, 10, 14 instead?”

---

2. Backbeat Challenge

Student Prompt:
“Add the Snare drum on steps 5 and 13. What happens when you combine this with the Kick pattern from Prompt 1? How does the rhythm feel different?”

Teacher Notes:

• Introduces layering and conditional thinking: certain beats trigger one sound, others trigger another.
• This is similar to writing multiple if statements in code.

Extension Questions:

• “If the Kick pattern is one loop and the Snare is another loop, how do the loops work together?”
• “Can you describe the Snare placement as a rule (e.g., ‘play every 8 steps starting at step 5’)?”

---

3. Hi-Hat Groove

Student Prompt:
“Turn on the Hi-Hat for every single step (all 16). Now experiment: try turning off every other Hi-Hat. How does changing the spacing affect the energy of the beat?”

Teacher Notes:

• This shows how changing step intervals changes rhythm, like changing loop increments in code.
• A full row = for (i=0; i<16; i++), every other = for (i=0; i<16; i+=2).

Extension Questions:

• “What coding concept matches turning on every step vs. every other step?”
• “If you wanted every 3rd Hi-Hat, how would you describe that as a rule?”

---

4. Remix Mode

Student Prompt:
“Click ‘Randomize’ and listen to what the sequencer creates. Then make one change to improve the groove. What do you notice about how small changes affect the whole pattern?”

Teacher Notes:

• Randomization connects to probability and randomness in code (Math.random()).
• Students learn that debugging (making one change at a time) is part of coding.

Extension Questions:

• “In coding, what function would generate random true/false values for each cell in the array?”
• “How do you decide if the pattern sounds ‘good’? How is that similar to testing/debugging a program?”

---

5. Tempo Test

Student Prompt:
“Set the BPM to 80 and press play. Now change it to 160. What stays the same about your pattern? What changes? How does tempo affect the feel of the music?”

Teacher Notes:

• Links coding to real-world math: BPM → milliseconds per step.
• The pattern (array) doesn’t change, but the timing function does.

Extension Questions:

• “If the tempo is 120 BPM, how many milliseconds is each 16th note? What about 80 BPM?”
• “In code, which variable would you change to adjust playback speed while keeping the same array?”