- Learnt27 min · cues, sections and stopping the old loop
- Basic25 min · give your video a verse and a chorus
- Challenge 1–327 min · two sections, four, and an ending
- Extrabonus · the breakdown
Review — where we got to 5 min
Last lesson the stage filled up. It all moved on the beat.
next costumewith the beat’s wait is a dance.- A pulse grows and shrinks back in one beat.
- Whatever a loop changes, the blocks above it put back.
Quick-fire
In the Extra, every sprite counted its own eight beats to find the drop. What goes wrong after five minutes?
Reveal the answer
They slip apart. A wait is never exactly half a second. So three sprites that count on their own slowly stop matching. Today one sprite counts. The others do what it says.
Today’s Topic 3 min
- Sections: a verse and a chorus are two different ways to move
broadcast [verse v]andwhen I receive [verse v]as cuesstop [other scripts in sprite v], and why a new section needs itswitch backdrop to [Spotlight v]for each section
Learning outcome
By the end of this lesson you will be able to:
- Write one script that holds the running order. It calls each section.
- Give a sprite two ways to move. Switch between them cleanly.
- Change the whole look of the stage on a cue.
Learnt — cues and sections 27 min
Why one sprite has to be in charge
Three sprites that count on their own are like three clocks. They match at the start. By the end they do not. Changing the numbers does not fix it.
The fix is not better counting. The fix is one counter. One sprite holds the running order and calls it out. The rest wait to be told.
The director
The director is the sprite in charge. Add the Microphone sprite. It never dances. Its only job is the running order.
when flag clicked
broadcast [verse v]
wait (8) seconds
broadcast [chorus v]
wait (8) seconds
broadcast [verse v]
wait (8) seconds
broadcast [chorus v]
The dancers listen
Every dancer swaps its when flag clicked for two when I receive [verse v] hats. There is one hat for each section. Each one has its own loop.
when I receive [verse v]
stop [other scripts in sprite v]
set size to (90) %
forever
next costume
wait (0.5) seconds
end
when I receive [chorus v]
stop [other scripts in sprite v]
set size to (120) %
forever
next costume
change [color v] effect by (25)
wait (0.25) seconds
end
The block that makes it work
stop [other scripts in sprite v] is the key block. What if it is not there? Then chorus starts a second forever loop. The verse loop is still going. So the sprite changes costume twice as fast.
It is easy to spot. The dancer shakes much too fast.
How to use this: Click the green flag to start it. Nothing else to press — watch it through, then use ↺ Reset to run it again.
The Stage listens too
A new backdrop shows the viewer that the song has moved on. It is the fastest way. The Stage gets the same cues.
when I receive [verse v]
switch backdrop to [Concert v]
when I receive [chorus v]
switch backdrop to [Spotlight v]
How to use this: Click the green flag to start it. Nothing else to press — watch it through, then use ↺ Reset to run it again.
Basic — give the song a shape 25 min
Open your video from last lesson. This changes how it starts. Test after each step.
How to use this: Click the green flag to start it. Nothing else to press — watch it through, then use ↺ Reset to run it again.
Step 1 — the director
- Add the Microphone sprite. Put it in the centre of the stage.
- Give it the running-order stack: broadcast, wait, broadcast, wait.
- Make the two messages
verseandchorusas you go. - Press the flag. Nothing happens yet. Nobody is listening.
Step 2 — one dancer listens
- On your first dancer, change its flag hat to
when I receive [verse v]. - Put
stop [other scripts in sprite v]right under the hat. - Play. The dancer should start when the director calls the verse.
Step 3 — the chorus behaviour
- Right-click the hat and choose Duplicate. Change the new hat to
when I receive [chorus v]. - Make the chorus stack bigger, faster, or lit up.
- Play. Watch the switch happen at eight seconds.
Step 4 — everybody else
- Do the same on your second dancer and on the drum kit.
- Each one gets two stacks and two stops.
- Play. The whole stage should change at the same time.
Step 5 — the Stage
- Add the Spotlight backdrop to your project.
- Give the Stage the two receive-and-switch stacks.
- Play. The room should change with the song.
Step 6 — watch the whole thing
- Go full screen. Watch all four sections. Do not touch anything.
- Does something keep going from the section before? A stop is missing.
My dancer flickers madly after the first chorus.
Two loops are running on it at once. The stop [other scripts in sprite v] is missing from the chorus stack. Or it is below the loop, not above it.
Nothing happens when I press the flag.
Every sprite is waiting for a message. Nobody is sending one. The director needs its when flag clicked.
The music stopped.
Your backing track was on a when flag clicked. You changed it to a receive. Give the track its own flag hat. It plays through every section.
Two sections, told apart
Make a verse and a chorus. A stranger can tell them apart with the sound off.
- At least two things are different: size, speed, colour, or who is dancing.
- The change happens on a cue, not on a timer inside each sprite.
- Nothing from the verse keeps going in the chorus.
The whole running order
Write the song out: verse, chorus, verse, chorus. Put it in one script that reads like a plan.
- Four sections, called by one sprite.
- Each section lasts as long as you chose.
- The backdrop changes with the section.
Teacher note — the script that is a document
The director’s stack is worth dwelling on. It is the first script in Level 1 that is not doing a job so much as describing a plan, and a pupil can hand it to somebody else and be understood. That is a real idea, and it is worth naming.
An ending, not a stop
After the last chorus the video should finish. Add a last sound and a pose. The stage stays still.
- One more message, sent after the last section.
- Everyone stops their loop and holds one costume.
- The music ends. It is not cut off in the middle of a loop.
- Nothing keeps moving in the corner.
How to use this: Click the green flag to start it. Nothing else to press — watch it through, then use ↺ Reset to run it again.
Teacher reveal — the ending cue
when I receive [end v]
stop [other scripts in sprite v]
switch costume to [anina stance v]
set size to (100) %
clear graphic effects
On every dancer. The stop kills the section loop, and the three blocks under it put the sprite into a pose you chose rather than whatever costume it happened to be on.
The director ends with wait (8) seconds then broadcast [end v]. Note it does not need stop [all v] at all — when every loop has stopped, the project is finished on its own.
The breakdown
Add a third section. In it, the music gets quieter. The other dancers fade. One dancer is left in the light.
How to use this: Click the green flag to start it. Nothing else to press — watch it through, then use ↺ Reset to run it again.
- A third message, with its own place in the running order.
- The other dancers fade with the ghost effect. They do not vanish.
- At least one layer of the music stops. It comes back after.
- The next section puts everyone back just as they were.
Teacher notes — fading, and putting it back
when I receive [breakdown v]
stop [other scripts in sprite v]
set [ghost v] effect to (60)
when I receive [chorus v]
stop [other scripts in sprite v]
set [ghost v] effect to (0)
set size to (120) %
forever
next costume
wait (0.25) seconds
end
The important half is the second stack. Every section has to set the things the other sections change, or a sprite that faded in the breakdown is still faint in the chorus. That is the same “put it back” rule as last lesson, one level up.
Going further: the drum dropping out is stop [this script v] in the breakdown and a fresh receive to start it again. There is a neater way to say “play only during these sections”, and it needs a variable holding the name of the current section — which is a Level 2 idea.
Summary 4 min
A song is made of sections. Sections need someone in charge.
- One sprite holds the running order. It sends
broadcast [verse v]at the right times. - All the others have a
when I receive [verse v]stack for each section. - Each of those starts with
stop [other scripts in sprite v]. If not, the old section keeps running under the new one. - The Stage listens too. The backdrop shows the viewer where they are.
- Cue
- A message that tells everyone a section has started.
- Director
- The one sprite that holds the running order. It does nothing else.
- stop other scripts in sprite
- Ends this sprite’s other stacks. A section change needs it.
- Section
- One way of moving, with its own look and its own speed.
Next lesson: the finale. The audience gets the keyboard. You share the video.