MusEDLab / Learning through making

Vibe
Coding

Make an idea playable.
Learn by changing it.

Describe a musical idea to an AI coding tool. Try what it builds, listen closely and keep revising. The experiment is a way to ask what music—and learning—could become.

01 / Start with a question

What else could
this become?

Vibe coding brings conversation with AI into the process of making software. For us, the interesting question is what we can learn by making, playing and revising a musical tool.

A working result is a beginning. Look inside the code, ask how it works, test your assumptions and change one thing at a time. A tool may run and still make unexpected musical choices or leave someone out.

Listen

Make a possibility

What happens if a rhythm has another layer, a different cycle or a new sound?

Learn

Open another way in

Could a new interaction help someone explore, teach or participate?

Reflect

Explain the making

What did you change, how did you test it, and what surprised you?

Start from MusEDLab’s tools or a musical question of your own. Check the original code and asset licenses before reusing them, and credit your sources.

02 / Our Scratch roots

Look inside.
Make it your own.

Learning by remixing has a history here.

MusEDLab’s Scratch projects let learners play with musical ideas, inspect the blocks and reshape how a tool behaves. These earlier projects used block-based programming. Today’s AI-assisted experiments offer another route into the same cycle of making, listening and revising.

William Payne and S. Alex Ruthmann examined the possibilities and limitations of music making in Scratch in Music Making in Scratch: High Floors, Low Ceilings, and Narrow Walls? (May 16, 2019).

Lab originals in Scratch

Rhythm

Groove Pizza ↗

By alexruthmann
Shared January 2, 2019

Open the project and use Scratch’s “See inside” to explore the blocks.

Pitch & play

aQWERTYon ↗

By alexruthmann
Shared January 2, 2019

Explore another route from a musical interface to editable code.

Community remixes in Scratch

Follow a Groove Pizza remix chain: alexruthmann’s original → remix by Degazio → remix by kylewu0715.

These are independently shared community projects, credited by their public Scratch handles. Project links and public metadata were verified; playback has not been tested.

03 / Listen to the possibilities

One family.
Different questions.

Compare what each design makes easier to hear, see or do.

Independent AI-assisted experiment / Ethan Hein

Drum Pizza

Ethan Hein’s Drum Pizza showing four drum layers, a circular rhythm pattern, step grid and sound-loading controls.
Drum Pizza interface by Ethan Hein. Actual screenshot with the Rock preset, captured October 22, 2026.

Ethan Hein’s independent, vibe-coded Drum Pizza explores four drum layers, triplets and custom WAV or MP3 sounds. Its playful character recalls the early Groove Pizza prototypes before the formal 2016 Herbie Hancock Math Science Music launch.

Try a question: How does changing a subdivision or adding your own sound change the groove?

Try Ethan Hein’s Drum Pizza ↗

An independent prototype maintained by its creator. This feature shares existing work as inspiration; it does not announce a submission or participation in this initiative.

Accessible Groove Pizza and Groove Pizzeria are earlier research projects shown as design precedents; they are not presented as AI-generated tools. See the Groove Pizza family for the established instrument and more history.

Read the design histories

Bisson, Tyler J. (2018). Groove Pizzeria: Designing a Circular Step Sequencer for Polyrhythm and Polymeter. Master of Music in Music Technology thesis, NYU Steinhardt, November 26, 2018. Advisor: Dr. Alex Ruthmann. Original, unchanged PDF; 89 pages.

Hein, Ethan (2013). Designing the Drum Loop: A constructivist iOS rhythm tutorial system for beginners. Thesis presentation, December 17, 2013; 18 slides on SlideShare.

04 / Community Remixes

Bring the demo.
Tell the story.

Submissions are not open yet

A showcase is taking shape.

We are preparing an on-site submission form. It is not accepting entries yet. In the meantime, build an experiment and document what you discover.

We welcome musical and teaching questions from educators, musicians, students and creative coders. A future submission should include:

  1. A working demo link. Give visitors something they can try, with any useful instructions.
  2. An image for display. Show the interface or musical idea and include a clear image credit.
  3. Your process and tools. Explain what you started from, how you built or remixed it, which tools—including any AI tools—you used, and what you tested.
  4. The teaching and musical possibilities. Describe what the design lets someone explore, make, hear or learn, and what still needs work.
  5. A title and creator credit. Include source acknowledgments and how you want the work credited.

Only share material you have permission to display. Leave out private recordings, student names and other personal data.

This initiative also supports MusEDLab’s developing NOHME chapter on vibe coding. Any future research participation or use of quotations would require a separate invitation and consent; display in a showcase does not provide research consent.