1 of 25

1

MAKE BEATS. LEARN CODE. PROMOTE EQUITY.

v3.1

2 of 25

Complete coding a song by remixing stems from songs from our featured Indigenous artists that use their “voice” and include a message.

AGENDA

  • Understanding Reconciliation
  • Preparing the Final Song
  • Adding Voice to Your Code
  • Debugging Your Song
  • Check Your Song's Characteristics

2

MODULE 8 - CODE YOUR VOICE

OBJECTIVE

v3.1

3 of 25

3

GROUP DISCUSSION

1. What have you learned about the Inequalities and injustices that Indigenous people have faced and continue to face in Canada? 

2. How are these injustices similar and different to the injustices faced by African American people in the United States?

3. What are some examples of initiatives aimed at promoting equality in Canada? (Example: Orange Shirt Day)

4. What does Reconciliation mean to you?

v3.1

4 of 25

4

2. ADDING POWER TO VOICE

v3.1

5 of 25

5

Reflect on the final song you want to create, will you:

  1. Revise and finalize your existing song

OR

  • Create a new song

v3.1

6 of 25

6

Top-down approach

Bottom-Up Approach

Mixed Approach

Sketch Out the Song Structure First

You might start by defining your song structure and sketching out the parts you want.

  • Intro
  • Verse 1
  • Chorus
  • Transition
  • Verse 2
  • Chorus
  • Transition
  • Bridge
  • Verse 3
  • Outro

Build the Parts First

You might want to build parts first—like the chorus or intro—and then assemble them into a song afterwards!

A Mix of Both

A combination of top-down and bottom-up!

v3.1

7 of 25

7

In your Student Coding Workbook, reflect on the final song you want to create, will you:

  1. Use Hard-Coded Functions? def intro():

OR

  • Functions with Variables? def chorus(start, end):

OR

  • A mix of both?

v3.1

8 of 25

8

In your Student Coding Workbook, reflect on the final song you want to create, will you:

  • Add more tracks?
  • Change the tempo?
  • Add any additional comments?

v3.1

9 of 25

9

MAKE IT A VIRAL HIT

  • Choose a form and structure for your song (for example: ABAB)
  • Be personal. Write from the heart. Tell a story.
  • Create repetition - Include an earworm or hook. Make your melody memorable.
  • Build variation in your song. Include contrast and change between minor and major chords.
  • Match beats between verses. Keep your verses to the same number or a multiple of a number of beats.
  • Maybe try some of the other 'effects' from Extension B in Module 4!

v3.1

10 of 25

10

Add comments to highlight sections that show the 4 R’s: respect, relevance, reciprocity, and responsibility

# This lyric is an example of

# Institutional Racism, prison Pipeline �fitmedia(ENTREP_VOX_BK_LETOUT,18,6,14)

Add comments to express your voice (through comments or selected lyrics) or the voice of your community.

# I Chose this lyric because…# This drum beat makes me think of…

ADD VOICE TO YOUR CODE

v3.1

11 of 25

11

Include a comment to let us know your target audience and the theme of your song.

# author: <Student Name>

# Audience: Family and Friends

# My song is to explain that there is

# ongoing racial inequity in our community

You can use the print function to print the purpose of your song in the console.

print("My song is to explain that there is ongoing racial inequity in our community")

Include a comment to tell us if you are speaking as an ally, an activist, or as yourself?

# author: <Student Name>

# writing as an ally/activist/self

v3.1

ADD VOICE TO YOUR CODE

12 of 25

12

Include comments to give credit to the artists of the sound clips used in your song.

# Audio clips used for remix from:

# Jayli's song “Child of the Government”

# Dakota Bear “Freedom”

v3.1

v3.1

ADD VOICE TO YOUR CODE

13 of 25

DEBUG Your Code

13

FINAL COUNTDOWN

v3.1

14 of 25

  1. Run your code.
  2. Check the console - are there any errors?
    1. If there are no errors, move on to Part 2 (Check Your Song's Characteristics) in the song submission process.
    2. If you have an error in your code, continue to step 3 in the debugging process.
  3. Read the console for clues (such as line number or type of error).
  4. Locate the error in your code: If the console provided a line number, take a look at that line and the previous line in your code. Check any arguments carefully. You can also comment out the lines of code one at a time to identify where a possible error could be.
  5. Print debugging can also be used to locate an error. Insert print statements throughout your code to obtain the value of variables and check your logic.
  6. Squash the bug: Check for syntax errors, like unclosed parentheses, quotations, or brackets. Edit the code, and run it to verify its correctness.
  7. Ask for help: If you find you have spent too much time on a bug, then ask someone for help!
  8. A fresh pair of eyes can do wonders for spotting mistakes.

14

DEBUGGING YOUR CODE

v3.1

15 of 25

15

3. CONSOLIDATION / REFLECTION

v3.1

16 of 25

16

Go through the checklists in your Student Coding Workbook to ensure your song is ready to submit to the competition.

v3.1

17 of 25

17

  • Is your song a minimum of 30 seconds (16 measures) and a maximum of 3 minutes?
  • Does your song use at least 5 unique music tracks?
  • Does your song include at least one sound clip (stem) from an Indigenous artist featured in the program (Aysanabee, Dakota Bear, Dr. Duke Redbird, Jayli Wolf, Samian)?
  • Play your song — Does the song sound like a remix of one of the artists? Have you changed the style, tempo, order of beats? Have you mixed other sounds with their stems?
  • Do you have any sounds that are not from the EarSketch library or that were recorded by you? If so, did you attribute the source in the comments? Any copyrighted sound clips that you do not have rights to must be removed from your song. Information on copyright can be found here.

v3.1

18 of 25

18

  • Does your song include the EarSketch API function fitMedia to insert sound clips?
  • Does your song use variables?
  • Does your song use comments to describe the code and document your message in the song?

TIP: Share your code with a peer (if possible). Do they understand the flow of the code? Are there places where additional comments would help them understand your code?

v3.1

19 of 25

19

To be eligible for the Grand Prize, you must also meet the following requirements:

  • Does your song include custom/user-defined functions?
  • Your song must score 60 points with the code indicator, you can score 60 points by having two user-defined functions

v3.1

20 of 25

20

  • Does your song include a message or call to action that promotes equity?
  • Does your song demonstrate student awareness or analysis of racial injustice?
  • Have you prepared a short reflection about your song to include with the submission form?

v3.1

21 of 25

21

Copyright protects the creator of a piece of original work to have the exclusive right to reproduce and use that work.

Have you used sounds outside the Earsketch music library (for example, uploading stems from your computer)?

  • NO - All music samples in the sound library are licensed, so you can use them as you wish in your music. No action required
  • YES
    • Did you upload your own sounds and vocals? No action required.
    • Did you upload sounds from other songs and websites? Check the copyright and ensure they fall under a Creative Commons license (such as sound clips on Freesound) or a free culture license. You cannot use samples or covers you do not have the rights to. Click here for more info on Copyright.

v3.1

22 of 25

22

NOW, GO FINISH CODING

YOUR SONG!

v3.1

23 of 25

23

When you are ready to submit, get the song link!

v3.1

24 of 25

24

SUBMIT YOUR SONG

bit.ly/yvipsubmit23

Deadline: June 30, 2026.

Sign up here to be notified of all Competition announcements and never forget that…

Now, give yourself a round of applause!

TIME TO SUBMIT!

v3.1

25 of 25

25

THANK YOU!

v3.1