Home
// Digital Technology - Year 9 & 10 //

BEAT LAB

Over the next 10 tracks your label will code raw sound into a finished song - synths, drums, melody, effects and a full arrangement, all written by hand in the browser. No samples, no shortcuts. Then you drop it live on Release Day.

🎛️ Code-Built Sound
🥁 Original Beats
🎨 Canva Cover Art
🎤 Release Day
Your Studio
💻
Coding Platform
Beat Lab Studio is built into this page, just below the rubric. Type or paste your code, or press Load into Studio on any code box, then press Run. Nothing to download, nothing to install.
🧠
AI Assistant
copilot.microsoft.com - ask it "How do I do X in Tone.js?" whenever you're stuck.
⚠ AI can invent Tone.js methods that don't exist - always test what it gives you and check it actually runs.
🎧
Your Studio Rig
Your laptop's built-in speakers work, but headphones are strongly recommended so you can actually hear your own mix over 20 other producers' beats. The built-in mic is fine for any voice recording you want to add.
🥁
Sound Library
Your core toolkit: Tone.Synth (single notes), Tone.PolySynth (chords), Tone.MembraneSynth (kick drums), Tone.NoiseSynth (hi-hats/snares). Full cheat sheet in Track 01.
🎼
Music Theory Cheat Sheet
Notes run A to G, BPM (beats per minute) sets your tempo, and a "bar" is a group of beats. You don't need to be a musician - the cheat sheet in Track 04 covers everything you need.
🎤
Release Day Rules
Every producer performs their finished track live to the class through the studio speakers. The class votes across categories - Best Beat, Best Melody, Best Mix and People's Choice.
// Primary Objective

Compose, code and mix an original track from raw sound synthesis to a polished release - then prove it live on Release Day.

Synthesize your own sounds by writing code, not by dragging in pre-made samples
Structure a full song arrangement with a real intro, build, drop and outro using Tone.js scheduling
Mix your track using real audio effects and balanced levels, not just raw output
Iterate using peer feedback and a remix pass so your final release beats your first draft
// Marking Key & Rubric
Criteria Demo Tape
(0-1)
Studio Ready
(2-3)
Chart Ready
(4)
Platinum
(5)
Score
Technical Coding Program doesn't run, needed heavy teacher support Successfully triggers notes and loops using Tone.js code you wrote Multiple layers (drums, melody, effects) run together reliably on the Transport Code is clean and deliberate, shows real understanding of timing, scheduling and routing / 5
Composition & Creativity No clear structure, feels random or unfinished Has a recognisable beat and melody that fit together Clear song structure (intro/build/drop/outro) with a genuine creative idea Original, polished composition with a distinct creative voice / 5
Mixing & Polish No effects used, levels clash or clip At least one effect applied, levels reasonably balanced Deliberate mixing choices - filtering and reverb used to shape the sound Professional-sounding mix, cover art and presentation support one cohesive vibe / 5
Release Day Did not perform, or track was not release-ready Performed for the class, met the brief Performed fully, gave and used peer feedback well Outstanding performance, helped other producers, clear ownership and reflection / 5
Total / 20
Scroll sideways to see every column
Beat Lab Studio
1 Type, paste or Load your code
2 Press Run to hear it
3 Press Stop to silence it
Ready
Examples Turn Layer on, load Drums and Run, then load Bass and Run again. Keep stacking parts from the same theme so the tempo and key match.
💡 How to play multiple beats at once

Way 1 - Everything in one code box

  1. Give every layer its own instrument. One synth can't play two notes at the same instant.
  2. Give every layer its own name. Two lines that both say const synth is an error, so use names like kick, hat, bass.
  3. Give every layer its own Tone.Sequence or Tone.Loop ending in .start(0).
  4. Start the clock once, at the very bottom, with Tone.getTransport().start();. Every layer follows that one clock, so they stay in time.
const kick = new Tone.MembraneSynth().toDestination();
const hat  = new Tone.NoiseSynth({ volume: -14 }).toDestination();

const kickBeat = new Tone.Sequence((time, hit) => {
  if (hit) kick.triggerAttackRelease("C1", "8n", time);
}, [1, null, null, null, 1, null, null, null], "8n").start(0);

const hatBeat = new Tone.Sequence((time, hit) => {
  if (hit) hat.triggerAttackRelease("16n", time);
}, [null, 1, null, 1, null, 1, null, 1], "8n").start(0);

Tone.getTransport().start();

Way 2 - Layer mode (jamming)

  1. Press Layer: Off so it says Layer: On.
  2. Press Run. Your first beat starts playing.
  3. Replace the code with another part and press + Add Layer. It joins in on the beat, on top of what's already playing.
  4. Press Stop to silence every layer. Turn Layer off to go back to normal, where Run replaces everything.

Layer mode is for trying ideas. For your final track, get every part into one code box (Way 1) and Save it, because Save only keeps what's in the box right now. Each theme in Examples has a Full track option that shows all of its parts in one box.

Console
Press Ctrl+Enter in the code box to Run. With Layer on, Run adds your code on top of what's playing. Save downloads your code as a .txt file, Open loads one back in.
Runs in your browser. Nothing you type leaves this computer.
Uses Tone.js v15.1.22 (MIT License, Copyright (c) 2014-2020 Yotam Mann).
Track List
Week 1
01
🎚️ Studio Orientation
▾
// TRACK OBJECTIVEBeat Lab Studio open and Run pressed. At least 3 different notes played and heard through Tone.Synth.
  • Scroll up to Beat Lab Studio, just below the rubric. You'll see a box with two lines of code already in it, a big Run button, and a Console underneath
  • Press Run and listen. Browsers block sound until you click something, so pressing Run is what switches it on - there's nothing else to unlock
  • Learn what a synthesizer actually is: code that generates a sound wave in real time, instead of playing a pre-recorded sample
  • Try Tone.Synth(), the simplest instrument in Tone.js - one voice, one note at a time
  • Play different notes by changing the note name in triggerAttackRelease (e.g. "C4", "E4", "G4") and listen to how the pitch changes
  • Try changing the duration ("8n", "4n", "2n" = eighth, quarter, half note) and notice it changes the length of the note, not the pitch
  • Put on your headphones and experiment - the goal today is noise, not music yet
💡 HintIf you hear nothing, check your headphones are plugged in and the volume is up, then look at the Console under the code box. A red message there means there's a typo in your code, and it tells you what it found.
💡 Using the code boxesEach track gives you a code box to try. Click Load into Studio on the code box and it replaces what's in the studio box, then press Run. (Copy still works if you'd rather paste it in yourself.) Save downloads your code as a .txt file and Open loads it back in next lesson.
// ASK AI"I'm using Tone.js in the browser for the first time. What's the difference between Tone.Synth, Tone.AMSynth and Tone.FMSynth in simple terms?"
// The code already in your studio box
const synth = new Tone.Synth().toDestination();
synth.triggerAttackRelease("C4", "8n");
02
🕐 Finding the Beat
▾
// TRACK OBJECTIVEA working loop running at a chosen BPM, started and stopped reliably from the Transport.
  • Learn what BPM (beats per minute) means and how it sets the speed of everything you build from here on
  • Use Tone.getTransport() - the master clock every Tone.js project runs on
  • Build your first Tone.Loop: a block of code that repeats automatically on a set beat, instead of you triggering every note by hand
  • Change the loop's interval ("4n", "8n", "16n") and hear how it changes the feel from a slow pulse to a fast pattern
  • Change Tone.getTransport().bpm.value and hear the same loop speed up or slow down without changing the code at all
  • Save your file with a loop running at a BPM you like - this becomes your track's tempo going forward
💡 HintStart slow. A loop at 200 BPM sounds like chaos until you can actually hear what it's doing at 90-100 BPM first. Get the pattern right, then speed it up.
// ASK AI"In Tone.js, what's the difference between Tone.Loop and Tone.Sequence, and when would I use one over the other?"
// A steady pulse that keeps playing on its own
const synth = new Tone.Synth().toDestination();

const loop = new Tone.Loop((time) => {
  synth.triggerAttackRelease("C3", "8n", time);
}, "4n").start(0);

Tone.getTransport().bpm.value = 100;
Tone.getTransport().start();
// LEVEL UPAdd a second synth and a second Tone.Loop that plays a different note (try "G3") at "2n" so two rhythms run at once. Use a separate synth for each loop, because one synth can't play two notes at the same instant, and give the new one { volume: -12 } so the two together don't distort. Then find a BPM where both sound good together and note it down.
Week 2
03
🥁 Build a Drum Kit
▾
// TRACK OBJECTIVEWorking drum pattern combining kick and hi-hat, with at least one deliberate rest.
  • Meet two new instruments: Tone.MembraneSynth (a punchy low kick drum sound) and Tone.NoiseSynth (a hiss, perfect for hi-hats and snares)
  • Build a Tone.Sequence - a pattern of hits laid out in a list, instead of one repeating note
  • Code a basic 4-step kick pattern, then layer a hi-hat pattern on top using a second Sequence
  • Experiment with rest steps to leave gaps - silence is part of a good beat, not a mistake
  • Adjust each instrument's volume so the kick doesn't drown out the hi-hat
  • Save your drum pattern - you'll build your melody on top of it in Track 04
💡 HintA drum pattern that hits on every single step usually sounds worse, not better. Real beats have gaps. Try removing a hit or two and see if it actually grooves harder.
// ASK AI"How do I use Tone.Sequence in Tone.js to play a repeating drum pattern with rests (silent steps) in it?"
// Kick + hi-hat pattern running together
const kick = new Tone.MembraneSynth().toDestination();
const hihat = new Tone.NoiseSynth({ volume: -12 }).toDestination();

const drums = new Tone.Sequence((time, step) => {
  if (step === "kick") kick.triggerAttackRelease("C1", "8n", time);
  if (step === "hat")  hihat.triggerAttackRelease("16n", time);
}, ["kick", "hat", "hat", "hat"], "4n").start(0);

Tone.getTransport().start();
📤 Submit via ConnectYour Track 03 drum pattern file (or a link/recording of it playing)
// LEVEL UPAdd a snare. Create a second Tone.NoiseSynth, add a "snare" step to your pattern and place it on the 2nd and 4th beats. Does it sound like a real beat yet?
04
🎹 Melody & Scales
▾
// TRACK OBJECTIVEA chord progression and a short original melody, both built from the same scale, playing alongside your Track 03 drums.
  • Music theory basics: you don't need to read sheet music, but every melody uses a scale - a set of notes that sound good together
  • Use the cheat sheet below to pick notes that won't clash
  • Meet Tone.PolySynth - it can play more than one note at once, which a single Tone.Synth can't do
  • Build a 4-chord progression using PolySynth and a Sequence, layered on top of your Track 03 drum pattern
  • Write a short melody line (4-8 notes) over the top using a second, separate synth
  • Adjust your melody until it sounds intentional, not random - repetition is your friend
🎼 Music Theory Cheat Sheet
C Major scaleC4, D4, E4, F4, G4, A4, B4, C5 - any combination of these will sound "in key" together
Simple chord shapesC major = C4+E4+G4, A minor = A3+C4+E4, F major = F3+A3+C4, G major = G3+B3+D4
BPM guide70-90 = chill/lo-fi, 100-120 = pop/house, 140+ = drum and bass/energetic
💡 HintIf your melody sounds wrong, check every note is actually from your scale. One note outside the scale is usually the whole problem, not your rhythm or your sequencing.
🔍 Google Image Search"C major scale piano notes diagram"
// ASK AI"Give me a simple 4-chord progression using notes from the C major scale, written as Tone.js chord arrays like ["C4","E4","G4"]"
// A 4-chord progression with a melody on top
const chords = new Tone.PolySynth(Tone.Synth, { volume: -12 }).toDestination();

const progression = new Tone.Sequence((time, chord) => {
  chords.triggerAttackRelease(chord, "2n", time);
}, [
  ["C4", "E4", "G4"],
  ["A3", "C4", "E4"],
  ["F3", "A3", "C4"],
  ["G3", "B3", "D4"]
], "1n").start(0);

const lead = new Tone.Synth({ oscillator: { type: "triangle" }, volume: -10 }).toDestination();

const melody = new Tone.Sequence((time, note) => {
  if (note) lead.triggerAttackRelease(note, "8n", time);
}, ["E4", "G4", "A4", "G4", "E4", null, "D4", "C4"], "8n").start(0);

Tone.getTransport().start();
// LEVEL UPChange the type of the melody synth from "triangle" to "sine", "square" or "sawtooth". Each has a different personality. Pick the one that fits your track and write one sentence on why.
Week 3
05
🏗️ Song Structure
▾
// TRACK OBJECTIVEA planned song structure with at least an intro and a build-up section coded and tested.
  • Learn the basic shape almost every track follows: intro, build, drop (or chorus), outro
  • Use Tone.Part to schedule exact notes at exact times, instead of a repeating pattern
  • Plan your structure on paper first: which section is drums only, which section brings in the melody, where the "drop" (the big moment) happens
  • Code your intro section (drums only, quiet), then schedule your chords and melody to come in a few bars later
  • Use a filter sweep or volume rise in the bars before your drop to build tension (bonus tie-in with Track 06)
  • Test your structure end-to-end - does it actually feel like it's building to something?
💡 HintThe "boring" intro is doing real work. If your drop hits in the first 2 seconds, there's nothing to build up to. Give your intro at least a few bars of just drums before anything else comes in.
// ASK AI"How do I use Tone.Part in Tone.js to schedule specific notes at specific times, rather than using a repeating Sequence?"
// Schedule an exact intro build-up
const synth = new Tone.Synth().toDestination();

const intro = new Tone.Part((time, value) => {
  synth.triggerAttackRelease(value.note, value.duration, time);
}, [
  { time: "0:0", note: "C4", duration: "8n" },
  { time: "0:1", note: "D4", duration: "8n" },
  { time: "0:2", note: "E4", duration: "8n" },
  { time: "0:3", note: "G4", duration: "4n" }
]).start(0);

Tone.getTransport().start();
📤 Submit via ConnectYour Track 05 structure plan (a screenshot or written outline of your intro/build/drop/outro) plus your in-progress file
// LEVEL UPTurn the intro into a build. Add four more events to the Part at times "1:0" to "1:3" using the same notes one octave higher (C5, D5, E5, G5) so it climbs before the drop.
06
🎛️ Effects & The Mix
▾
// TRACK OBJECTIVEAt least one effect applied to at least one instrument, with balanced levels across the whole track.
  • Learn what an effect actually does: it takes a raw sound and reshapes it before it reaches the speakers
  • Try Tone.Reverb - makes a sound feel like it's in a room, hall or cave, depending on the decay setting
  • Try Tone.Filter - cuts or boosts certain frequencies; a "lowpass" filter muffles the high end, useful for the build-up in Track 05
  • Connect your instruments through effects using .connect() instead of .toDestination() directly
  • Balance your levels - kick, chords and melody should all be audible, nothing should drown out anything else
  • Save a "mixed" version of your track with at least one effect on at least one instrument
💡 HintMore effects is not automatically better. One well-chosen reverb on your melody can sound huge - three effects stacked on everything usually just sounds muddy. Add one, listen, decide if it's actually improving anything.
// ASK AI"How do I connect a Tone.js synth through a Tone.Filter and then a Tone.Reverb before it reaches the speakers, using .connect()?"
// Route a synth through a filter, then reverb, before the speakers
const reverb = new Tone.Reverb({ decay: 3, wet: 0.4 }).toDestination();
const filter = new Tone.Filter(800, "lowpass").connect(reverb);
const synth = new Tone.Synth().connect(filter);

synth.triggerAttackRelease("E4", "4n");
// LEVEL UPSwap the reverb for new Tone.FeedbackDelay("8n", 0.4).toDestination(), then change the filter from 800 to 300 and to 3000. Describe how each change alters the sound.
Week 4
07
🧠 AI Composition
▾
// TRACK OBJECTIVEOne AI-suggested idea (chord, melody shape or title) tested, adapted, and either kept or deliberately rejected with a reason why.
  • Use Copilot to generate raw ideas: chord progressions, melody shapes, or a short set of lyrics for your track's theme
  • Take whatever AI gives you and translate it into real Tone.js code yourself - AI can suggest note names, it can't write your Tone.js structure for you
  • Test the AI's suggestion against your scale from Track 04 - if it suggests notes outside your key, decide whether to fix it or let it be a deliberate clash
  • Ask AI for a track title and a one-line "artist statement" idea, then write your own version in your own words
  • Compare your AI-assisted version against your original Track 04/05 draft - which is actually better, and why?
  • Document one thing AI got right and one thing it got wrong or you had to fix
💡 HintTreat AI like a bandmate throwing out ideas, not a producer finishing your track for you. The best results come from taking one small idea from AI and building on it yourself, not copying a whole progression wholesale.
// ASK AI"Suggest a 4-chord progression in the key of C major that sounds emotional or uplifting, and suggest one short lyric line or track title to match the mood"
08
🎧 Full Track Build
▾
// TRACK OBJECTIVEA complete track with drums, chords, melody, structure and at least one effect all playing together in time.
  • Bring every piece together on one shared Transport clock: drums (Track 03), chords and melody (Track 04), structure (Track 05), effects (Track 06)
  • Make sure every layer starts at the correct time relative to your planned structure, not all at once
  • Run your full track start to finish without stopping it to fix something - note every glitch as you go
  • Fix timing issues first, sound issues second - a track that's in time but slightly rough beats a track that's polished but falls apart rhythmically
  • Name your track and save a version you're happy to call "finished" for now - you'll get one more pass at it in Track 09
  • Get a check-in from your teacher or a nearby producer before moving on
💡 HintIf two layers sound out of sync, check they're both actually attached to the same Tone.getTransport() clock and using bar:beat notation (like "0:2") rather than raw seconds - mixing timing systems is the most common cause of drift.
// ASK AI"My Tone.js layers sound slightly out of sync with each other even though they're all started at the same time - what are the most common causes of that?"
// A complete layered track - swap in your own parts
Tone.getTransport().bpm.value = 100;

// Drums (Track 03)
const kick = new Tone.MembraneSynth({ volume: -4 }).toDestination();
const hihat = new Tone.NoiseSynth({ volume: -12 }).toDestination();
const drums = new Tone.Sequence((time, step) => {
  if (step === "kick") kick.triggerAttackRelease("C1", "8n", time);
  if (step === "hat")  hihat.triggerAttackRelease("16n", time);
}, ["kick", "hat", "hat", "hat"], "4n");

// Chords and melody (Track 04)
const chords = new Tone.PolySynth(Tone.Synth, { volume: -12 }).toDestination();
const progression = new Tone.Sequence((time, chord) => {
  chords.triggerAttackRelease(chord, "2n", time);
}, [["C4", "E4", "G4"], ["A3", "C4", "E4"], ["F3", "A3", "C4"], ["G3", "B3", "D4"]], "1n");

const lead = new Tone.Synth({ oscillator: { type: "triangle" }, volume: -10 }).toDestination();
const melody = new Tone.Sequence((time, note) => {
  if (note) lead.triggerAttackRelease(note, "8n", time);
}, ["E4", "G4", "A4", "G4", "E4", null, "D4", "C4"], "8n");

// Intro (Track 05)
const introSynth = new Tone.Synth({ volume: -6 }).toDestination();
const intro = new Tone.Part((time, value) => {
  introSynth.triggerAttackRelease(value.note, value.duration, time);
}, [
  { time: "0:0", note: "C4", duration: "8n" },
  { time: "0:1", note: "D4", duration: "8n" },
  { time: "0:2", note: "E4", duration: "8n" },
  { time: "0:3", note: "G4", duration: "4n" }
]);

// Layer it all on one clock (bars:beats)
intro.start(0);              // bar 1: intro on its own
drums.start("1:0");          // bar 2: drums and chords come in
progression.start("1:0");
melody.start("3:0");         // bar 4: melody joins once the beat is established

Tone.getTransport().start();
📤 Submit via ConnectYour Track 08 full working file, plus a short note on what you fixed to get everything in time
Week 5
09
🎨 Cover Art & Remix
▾
// TRACK OBJECTIVEFinished cover art exported from Canva. At least one piece of peer feedback acted on in the final track.
  • Open Canva and design cover art for your track - think about how the mood of your music matches the colours and imagery you choose
  • Keep your track title and "artist name" (your producer alias) clearly visible on the cover
  • Swap your in-progress track with a partner - each of you listens to the other's track fresh, without knowing what they were going for
  • Give real feedback: one thing that works, one thing you'd change, using the rubric categories as your guide
  • Take at least one piece of feedback and make one genuine change to your track before Release Day
  • Export your Canva cover art as an image file, ready to display at your performance
💡 HintWhen giving feedback, be specific. "It's good" and "I don't like it" both help nobody - "the drop feels like it comes in too early" or "I couldn't really hear the melody under the drums" actually gives someone something to work with.
🔍 Google Image Search"album cover art design ideas music"
// ASK AI"I'm designing an album cover for a track I made. Based on the mood of my track, what colours, imagery or style would suit it?"
10
🎤 Release Day
▾
// TRACK OBJECTIVEPerformed your finished track live on Release Day. Final reflection and cover art submitted.
  • Arrive with your final track saved and ready to Open in the studio, plus your cover art ready to display
  • Safety/format briefing: each producer gets one uninterrupted play-through on the studio speakers, no talking over someone else's track
  • Perform your track live to the class in the running order set by your teacher
  • The class votes across categories: Best Beat, Best Melody, Best Mix and People's Choice
  • Complete your final reflection: what you're proud of, what you'd change with more time, and one thing you learned about coding sound
  • Submit your final track file, cover art and reflection through Connect
💡 HintNerves are normal. If your track glitches live, let it play through rather than stopping and restarting - a small glitch in a full performance almost always lands better than a track that gets cut off and restarted twice.
// ASK AI"Help me write a short reflection paragraph about what I learned making an original track by coding sound with Tone.js"
📤 Submit via ConnectFinal track file, cover art, and your final reflection
🎤

Release Day Awaits

After 10 tracks of coding raw sound into a finished song, your track hits the studio speakers for real, live, in front of the whole class. Every producer performs, every producer gets feedback, and the class crowns the best beats.

🎧 Live, no do-overs
🗳️ Class-voted awards
🏆 Four titles to win

Press Run in Beat Lab Studio and begin // Track 01

SYSTEM ONLINE // YEAR 9-10 DIGITAL TECHNOLOGY BEAT LAB // 10 TRACKS