maps. season 2.

I’ll get it up soon. Been deep in a creative project.

re: licensing, you can just use anything from the streams as you please. The streams are CC licensed, and i just assume people will rip any chunk of code they find useful. You can attribute me if you like, but I’m not precious about these relatively informal stream documents. Just happy they’re proving useful!


@Galapagoose, patron saint of gifted code, and maps. :cowboy_hat_face:


:blush: :partying_face:

i’m so ready for this


The final episode is postponed until 9/2, as I couldnt get it recorded before this tiny vacation in the northeast.

All prior VODs are up & linked in the top post!


Have fun on vacay! I hope it’s a good time.

@dan_derks First, I want to say how thankful I am that you’ve gone through and timestamped these episodes and laid out all the info so well. Without this outline It would’ve taken me so much longer to grasp the concepts. I’ve been digging into Crow a lot lately and there’s only so far that the scripting reference can take me. So your outlines of these Maps episodes have been a real boon for my learning.

I just wanted to note that I believe I may have found a small typo in the Zippers code. I saw that you link to the Github in your post for making notes and addressing typos but I’m not too Github savvy so I thought I’d post it here.

For Zippers this code seems to be missing a parenthesis. I’ve added it below and bolded it (or I suppose asterisked it **). There should be a parenthesis on the second to last end at the bottom to close the

This typo also exists for the shorter code example you added just above this longer code that I’ve pasted below.

Thanks again for all the work laying out this info!!

function big_melody2()
    while true do
      local stage = stages() -- pass the currently-indexed table to 'stage'
      output[1].slew = stage[2]/2 -- the second entry describes time
      output[1].volts = stage[1] -- the first entry describes voltage
      if stage[3] then -- if there's a third entry, for shape...
        output[1].shape = stage[3] -- change the output shape!
      else -- otherwise...
        output[1].shape = 'linear' -- keep it linear
      clock.sleep(stage[2]) -- the second entry describes time

rad, thank you for the keen eye! appreciate the review + kind words!!

let’s get you going with it! small changes like this are approachable using GitHub’s Desktop interface :slight_smile:

  1. if you haven’t already, create a GitHub account
  2. after verifying, download GitHub Desktop
  3. once installed, either:
    a. navigate to GitHub - monome/docs:, click the green Code button and select ‘Open with GitHub Desktop’
    b. in the Desktop application, navigate to File > Clone Repository > URL, enter for the Repository URL, select a meaningful local path for yourself, and hit ‘Clone’

(if you’ve already done steps 1-3 before, make sure to hit the ’ :recycle: Fetch origin’ button in the top-middle of the Desktop app’s interface to grab the most recent version of the repository)

  1. once the repository is cloned to your computer, you can either open the individual files from your file browser or open the entire repo from the GitHub app – either way, we’re looking to edit docs/crow/maps/ (if you need a Markdown editor, I like MarkText)
  2. make your changes to the file, save, and navigate back to the GitHub Desktop application – you’ll see your file changes as well as a warning message which lets you know that you can’t write to the repository directly:

    click ‘create a fork’ in the bottom left, then ‘Fork This Repository’ > ‘To contribute to the parent project’ to bundle up your contributions :slight_smile:
  3. now, you can add a little bit of detail describing the change you made in the bottom left – press ‘Commit to gh-pages
  4. press ‘Push origin’ in the main area of GitHub Desktop to send the commit to your fork:
  5. in the GitHub Desktop application navigate to Branch > Create Pull Request (or press CMD-R) to propose your changes to the main codebase. this’ll open your browser to review the changes:

    if it all looks good, hit the green ‘Create pull request’ button and you’ll see the descriptive text you entered:

    hit ‘Create pull request’ again and it’ll be submitted for review!

it might seem like a buncha steps, but it blows by once you do it for the first time – i’d love for you to submit the change, so please let me know if you run into any trouble!


This is a really nice little Github guide. I might be linking to this from elsewhere on the internet…


Thanks so much for the Github guide! I suppose I have no excuse now not to jump in. Will do today!


fnl() is great, especially with the increase in iic devices. Is that something you think will be folded into the standard library?

Also: thanks for this! Very helpful and interesting to see crow explored in this format. Clicked in a way reading the docs hadn’t.

1 Like