Convert well-known melodies, themes, and scores into chiptune arrangements using chiptune-studio. Takes a song reference (title, artist, or melody description), researches key/tempo/notes, makes creative arrangement decisions per scene or section, and outputs a composed WAV via chiptune-studio synthesis. Use when: user asks to "make a chiptune version of [song]", "cover [track] in 8-bit", "arrange [theme] for chiptune", "do a chiptune [song name]", or references any well-known melody that should be rendered through the chiptune-studio toolkit. Also triggers on: "soundtrack this with [song]", "score this video with a chiptune [reference]".
Arrange well-known melodies as chiptune compositions via chiptune-studio.
Prerequisite skill: chiptune-studio (synthesis toolkit). This skill handles the
creative arrangement process. Chiptune-bricks handles the sound.
Gather these facts about the source material:
E E D C Bb B)Research sources (try in order):
Output: A docstring at the top of the composition script documenting what you found.
Don't transcribe literally. Translate idiomatically.
Translation principles:
| Source sound | Chiptune equivalent |
|---|---|
| Guitar riff | arp() with sawtooth/square, crush=3-4 |
| Bass line | arp() octave down, square, note_frac=0.5, lowpass(800) |
| Drum kick | noise(0.06) + lowpass(150) + tight env(a=0.002, d=0.03, s=0.1, r=0.02) |
| Drum hat | noise(0.04) + highpass(2000) + tight env |
| Orchestral pad | drone() or pad() with triangle, heavy lowpass |
| Choir/vocal | Detuned pad() pairs with tremolo, slow env attack |
| Solo melody | sawtooth/triangle arp with reverb/delay |
| Power chord | Stack root + fifth as simultaneous arps |
| Sustain/held note | resolve() with reverb |
| Distortion | bitcrush depth 2-4 |
What to preserve vs reinvent:
| Preserve | Reinvent |
|---|---|
| Core melody (the recognisable notes) | Instrumentation (chiptune voices) |
| Key and mode | Arrangement density (usually sparser) |
| Rhythmic feel | Production effects (bitcrush replaces distortion) |
| Signature intervals (what makes it that song) | Dynamics (env/vol curves) |
| Tempo (unless scene-matching) | Layering (2-4 voices max) |
When scoring a video with defined scenes:
resolve(), ghost of melody fadingUse this template structure:
# /// script
# requires-python = ">=3.10"
# dependencies = ["numpy", "scipy", "pydub", "audioop-lts"]
# ///
"""
[Title] — [Source Song] as chiptune [style].
[Key]. [BPM]. [Arrangement approach].
Core: [melody as note names]
Original: [composer]. Chiptune-covering with love.
"""
import sys
import numpy as np
sys.path.insert(0, "~/Repos/symbient-skills/skills/chiptune-studio/scripts")
from bricks import *
from bricks.osc import sine, square, sawtooth, triangle, noise, silence, pad
SR = 22050
DUR = [total_duration]
BPM = [tempo]
c = canvas.make(DUR)
# [Define riff/melody note arrays]
RIFF = ["E3", "E3", "D3", "C3", "Bb2", "B2"]
# ============================================================
# SECTION [N]: [NAME] ([start]-[end]s) — [description]
# ============================================================
# [Place layers with canvas.place()]
# ============================================================
# MASTER
# ============================================================
c = canvas.normalize(c)
c = fade_in(c, 1.5)
c = fade_out(c, 3.5)
canvas.save_wav(c, "[output_path]")
Composition heuristics:
lowpass everything that isn't the lead melodysub_rumble() under intense sections for physical weighttriangle, vol=0.03-0.05) add depth without mudsparkle() cascades for transitions or "something appearing"resolve() at the root noteuv run [score_script.py]
Mix levels when combining with voiceover:
See references/doom-e1m1-example.md for a complete annotated walkthrough of
converting Doom E1M1 "At Doom's Gate" into a scene-matched chiptune score.