Tech Beats Basics

Overview

Students are introduced to how music technology supports composing, recording, editing, and sharing sound. They will explore key hardware and software, then make a short, simple digital music loop.

Learning intentions

• WALT identify common music technology tools used in music production.
• WALT describe how hardware and software work together to create and shape sound.
• WALT create a short digital music pattern using basic editing skills.
• WALT reflect on how technology choices affect the sound and musical effect.

Success criteria

• I can name at least three hardware and three software examples used for music production.
• I can explain (in my own words) what recording, editing, and exporting do.
• I can create a 4–8 bar loop with a clear beat and at least two sound layers.
• I can give one specific improvement for my loop using music-technology vocabulary (e.g., tempo, track, volume, effect).

Curriculum links

• Creating and presenting: students compose and create music using structured processes and technology.
• Musical understanding: students show understanding of how sound and recording/editing choices affect musical outcomes.
• Key competencies: thinking (plan and problem-solve), managing self (track progress), relating to others (collaborate), using language/symbols (accurate descriptions).
• Creative arts learning: using purposeful experimentation and reflection to develop musical ideas.

Lesson structure (50 minutes)

1. 0–5 min: Welcome + unit map

• Introduce “Creating Music with Technology” as a 30-lesson unit. Briefly explain that Lesson 1 focuses on tools and a first small creation.
• Show a simple overview slide with: tools → how sound is made → recording/editing → exporting/sharing.

2. 5–12 min: Technology scavenger talk

• Teacher shows 2–3 real examples (or labelled pictures): audio interface/headphones, microphone (if available), MIDI keyboard/controller, speakers.
• In pairs, students quickly match a tool to what it helps you do (capture sound, control notes, monitor playback, route audio).

3. 12–20 min: Demo—software workflow

• Teacher demonstrates a typical workflow: create project → set tempo → add tracks → choose sounds/instruments → record or step-enter notes → edit (trim/quantise/volume) → add a simple effect (reverb or EQ) → export.
• Students note one “tool” and one “step” they could use later.

4. 20–30 min: Mini creation—build a beat loop

• Students create a 4–8 bar loop using a shared template (same key/tempo options to reduce technical overload).
• Each student adds:
• One rhythmic element (drums or percussion pattern),
• One melodic or harmonic element (simple instrument or sample),
• Basic mixing (volume balance).
• Teacher circulates with quick prompts: “What is your tempo?”, “What changes if you adjust volume?”, “Where do edits happen?”

5. 30–40 min: Editing challenge—make it sound better

• Students improve their loop using two short edits:
• Quantise/tighten timing (or nudge timing),
• Trim/cut to fit cleanly at bar boundaries.
• If time, students add one gentle effect (small reverb or filter) and listen for the difference.

6. 40–46 min: Pair share + success criteria check

• In pairs, students play their loops and use a sentence starter:
• “My loop has a clear beat because…”
• “I changed ____ to improve ____.”
• Peers identify one strength and one question (e.g., “Why that sound layer?”).

7. 46–50 min: Quick reflection + tidy up

• Students complete a 2-minute exit reflection: tool I learned, workflow step I used, and one goal for Lesson 2.
• Save projects with consistent naming; remind students about headphones safety and respectful audio levels.

Resources

• Student devices (laptops or tablets) with the music software already installed
• Teacher device connected to projector/screen
• Headphones for each student (or shared sets if unavoidable)
• Simple software template file (project with set tempo options and a few instrument choices)
• Audio interface and/or microphone (optional, if available)
• MIDI keyboard/controller (optional, for demo)
• Printed or slide “workflow cards” showing: tempo → tracks → record/enter → edit → export
• Speaker/headphone health reminder poster (hearing safety)
• A short teacher-made checklist for students to track progress against success criteria

Assessment

• Formative observation during creation and editing (teacher notes on tool use, workflow understanding, and independence).
• Product check: loop includes clear beat, at least two layers, and completed edits/trimming.
• Short reflection at the end of the lesson to confirm understanding of workflow steps and learning goals.

Differentiation

• Support: provide sentence starters for reflections and a step-by-step workflow card; offer a “starter loop” template that students customise (swap sounds, adjust volume).
• Support: limit instrument choices to 2–3 per student; teacher pre-configures tempo and bar length.
• Extension: challenge students to add one additional layer (bass/synth pad) and one mix change (pan or EQ) plus a brief explanation of why.
• EAL/SEN: allow students to explain understanding by recording a short audio reflection or using diagrams (e.g., “this tool → this effect on sound”); keep instructions in short chunks and model each software step slowly.
• Leadership option: if one student finishes early, they can become “tech helper” for a peer, focusing on workflow steps rather than taking control.