Tech Setup Workspace

Overview

Lesson 3 of 30 in the unit “Creating Music with Technology” focuses on building a reliable, safe music production workspace. Students will install required software components (as directed by the teacher), connect basic hardware, and configure settings for smooth recording and playback.

Learning intentions

• WALT set up a music production workspace that is organised, safe, and ready to create.
• WALT install and check required software components for this unit.
• WALT connect and test hardware (headphones/microphone or MIDI controller) to ensure audio works correctly.
• WALT use basic file management so projects are easy to find and share.

Success criteria

• I can follow step-by-step setup instructions to install or update the required software without missing key steps.
• I can connect hardware correctly and confirm I can hear audio through the correct output.
• I can create a project file, name it correctly, and save it in the agreed folder structure.
• I can troubleshoot common issues (no sound, wrong input/output, muted tracks) using a checklist.

Curriculum links

• Music achievement focus on creating music and using technology to support musical outcomes.
• Critical thinking in solving a practical problem (setup troubleshooting) and improving outcomes.
• Digital literacy through safe, responsible use of devices and organising digital files.
• Communication by explaining what is working and what needs fixing using clear audio/setting descriptions.

Lesson structure (50 minutes)

1. 0–5 min: Welcome + goal check

• Teacher models what “a ready workspace” looks like (audio routing, project folder, settings).
• Students share one device they’ve used for music (phone, headphones, controller) and what usually goes wrong (e.g., “no sound”).

2. 5–12 min: Workspace rules and safety

• Quick routines: headset safety (volume checks), cable management, power/plug etiquette, and respectful device handling.
• Teacher introduces the setup checklist students will use at each station.

3. 12–22 min: Software installation/update (guided)

• Teacher demonstrates the exact steps for installing/updating the required software (or confirming it is already installed).
• Students follow their own checklist: open the software, sign in if needed, and confirm the project/audio settings screen loads.

4. 22–32 min: Hardware connection (teacher model + student connect)

• Teacher shows how to connect headphones and the correct input device (microphone or MIDI controller) and where those choices appear in settings.
• Students connect their hardware and complete a “Pass/Needs help” test: play a demo sound and confirm the output device is correct.

5. 32–42 min: Create and save a starter project

• Teacher prompts students to create a new project, set the sample rate/tempo defaults as instructed, and save in the shared folder with a consistent naming format (e.g., StudentName_ProjectLesson3).
• Students add one short sound placeholder (a beat loop or a test note) to confirm the audio engine works, then save again.

6. 42–48 min: Troubleshooting clinic (pair support)

• Using a mini-problem card, students troubleshoot common issues (muted track, wrong input/output, no audio, software not detecting hardware).
• Each pair must record what they changed and whether it worked.

7. 48–50 min: Exit reflection

• Students write one “I can” statement about their setup and one question/next step for tomorrow.

Resources

• Teacher setup checklist (printed or digital) with step order and quick screenshots described verbally
• Student devices (laptops/tablets) with admin rights or pre-arranged teacher permissions
• Required music software installer/update instructions (offline or school-provided if needed)
• Headphones for each student (with a quick volume reminder)
• Microphones and/or MIDI controller (as available for the class setup)
• Extension cables/adapters and labelled ports (USB, audio interface input, headphone out)
• Shared class folder structure for lesson projects
• Troubleshooting problem cards (no sound, wrong output, mic not detected, device not recognised)
• A short “demo audio” file or built-in test tone within the software (no hyperlinks needed)

Assessment

• Formative observation: teacher checks each student can complete software launch, hardware test, and correct saving of a project.
• Checklist completion: students mark each setup stage as “done” or “needs help” and note one troubleshooting action taken.
• Exit reflection: teacher reads whether students can articulate the key working parts (output device, saved file location, correct settings).

Differentiation

• Support: provide a printed “next step” strip for students who need slower pacing; pair students with a reliable helper; allow teacher-led setup for one device connection at a time.
• Support for SEN/learning needs: reduce steps to “minimum viable setup” (software open + audio output correct + save project) before adding extras.
• Extension: students who finish early adjust a setting within safe boundaries (e.g., buffer/latency option if appropriate, or test recording level) and document the change.
• EAL: sentence starters for troubleshooting (“I can’t hear sound because…”, “The output is set to…”, “When I changed it, it worked.”); encourage pointing to the on-screen setting names.