Skip to main content

composer-nb

A small language for chords and drums, played right inside Jupyter notebooks.

%%music
// what happens now: crash once, the groove repeating under it
time 7 over 8

pattern groove = 3 bars {
  kick: x--x---
  snare: ----x--
  ride.bell: x--
}

play 6 bars {
  crash: 1
  groove
}

Each play renders to audio in the notebook, with a play button, a waveform, a drum grid, the chords it heard and any mistakes it found.

Install

pip install composer-nb

Then, in a notebook:

%load_ext composer_nb

It works in JupyterLab, Jupyter Notebook 7, VS Code and Google Colab. Sounds are rendered in your browser, and the piano, guitar and drum samples load from the web, so you need an internet connection. Press Tab inside a %%music cell for completions.

Cells that continue from each other

Give a cell a name, and later cells can start from the settings and names it ended with:

%%music intro
tempo 75
capo 2
sound guitar
chords riff = Am E7|G D
play chords: riff
%%music verse after intro
play chords: F C|Dm E7 riff

verse plays on guitar with a capo at fret 2, at 75 bpm, and can use riff, wherever it sits in the notebook and whenever you run it. If intro hasn't been run yet, you get an error saying so. A cell can still change anything it inherits: tempo 90 in verse speeds up just verse.

A cell with no name plays on its own and isn't saved.

From Python

%%music is a shortcut for Song, which you can use directly:

from composer_nb import Song

intro = Song("tempo 75\nsound guitar\nplay chords: Am E7|G D", name="intro")
verse = Song("play chords: F C|Dm E7", after=intro, name="verse")
verse  # shows the player

Songs are ordinary Python values, so you can generate them with loops and functions:

blues = "|".join(["A7", "D7", "A7", "A7", "D7", "D7", "A7", "A7", "E7", "D7", "A7", "E7"])
Song("tempo 120\nsound epiano\nplay chords: " + blues)

The language

Every line starts by saying what it is:

Line What it is
tempo 90 A setting: a reserved word and its value
steps pair = X-x- A name, with its type in front: steps, chords or pattern
kick: x--x--- Inside braces, an instrument and what it plays
play { ... } Plays what's after it, a pattern or one line. Nothing else makes sound

// starts a comment. Blank lines and indentation mean nothing. Settings and names carry on into the cells below.

Types

A name's type goes in front of it, and = gives it its value:

Type What it holds Where it goes
steps A drum's hits: steps pair = X-x- On a drum's line: hat: pair pair
chords Bars of chords: chords verse = Am F|C G On the chords line: chords: verse
pattern Lines in braces that play together, over and over: pattern groove = { ... } On a line of its own, or after play

A name only holds its type, and only goes where that type goes. Chords on a drum's line, or steps where a pattern belongs, is an error that names both types. A name without a type is an error too, and the message shows the line to write.

Settings

Setting Default Meaning
time 4 over 4 Notes in a bar, over which note: 7 over 8, or felt in groups: 3+4 over 4
tempo 120 Quarter notes per minute
step 1/16 How long one drum step lasts: 1/8, or 1/12 for triplets
sound piano What chords play on: piano, epiano, organ, pad, bass, guitar
key C Key for Roman numeral chords: C, Am, Bb, F#m
capo 0 Capo fret, 0 to 12. Only with sound guitar
octave 3 Octave chords are voiced in, 1 to 6
kit rock Drum sound: rock or synth

Every number is arithmetic (tempo 60*2, (1+2) bars groove), so * and / only ever multiply and divide. That's why a time is 7 over 8 rather than 7/8.

Chords

Chords go on a chords: line and play on the sound setting:

sound guitar
play chords: C - - G|Am - F G|%|F - _ -

| is a bar line, and the chords in a bar split it evenly. - holds the chord before for another slot, _ is silence and % repeats the bar before. Chords can be names (Cmaj7, F#m, Bb7, C/E) or Roman numerals that follow key (I vi IV V7).

Drums

kick, snare, hat, ride, crash, tom and floor are the drums, one to a line. Some have other sounds with lines of their own: ride.bell, hat.open, hat.pedal, snare.rim (a rimshot) and snare.ghost (the snare's ghost notes, so they can sit under its main line). A drum plays either steps or beats:

pattern beat = {
  kick: x---x---x-x-----
  snare: ----X-------X---
  snare.ghost: --------------x-
  hat: x-
}

play 2 bars {
  crash: 1
  beat
}

Each drum has one line in a block. To layer it, its line takes a block of steps, one layer a line. The layers repeat until they line up again, and where two hit the same step, the lower line wins. A rest never wins, so a layer only changes the steps it hits:

pattern ghosts = {
  snare.ghost: {
    --x-
    ------------ddd-
  }
}

A block of steps is steps, so it can be named too: steps ghosts = { ... }. Where patterns played together hit the same drum at once, the lower line wins too.

An open hi-hat rings until the next hi-hat hit closes it (a stick on hat, or the foot on hat.pedal), and replaces a closed hit at the same moment, so hat: X-x- can keep going under hat.open: ------X-.

Steps are one character each, a 16th note unless step says otherwise: x hit, X accent, g ghost (on the snare, use snare.ghost), d double, - nothing. Beats are counted 1 e & a 2 e & a, and - between bar lines is an empty bar. Steps after a beat say how it's hit, and carry on from there: 2 X is an accent on 2, and 3 dd a burst of doubles from 3. So a line that's mostly rests is written by where it hits: snare.ghost: -|3 dd instead of snare.ghost: ----------------------dd----.

Patterns and play

A pattern is lines in braces that play together, over and over: everything in it repeats until the pattern ends. Give it a name, and play it by name. Names in a row play one after another:

pattern hit = { crash: 1 }
pattern groove = {
  kick: x---x---
  snare: ----x---
}
play hit groove groove hit

Inside braces, a pattern's name on a line of its own plays next to the lines beside it. A pattern without a name plays wherever a name could: play hit { snare: xxxx } hit.

Repeating and lengths

Putting something in a pattern is the one way to repeat it, and a length is the one way to say how long.

You write Meaning
pattern beat = { hat: x- } Everything in a pattern repeats until the pattern ends
play { crash: 1 ... } A play is a timeline, and its own lines play once
groove, on a line of its own In a play, the pattern repeats until the play ends
3 bars { ... } A length, always in front of what it measures
6 bars groove groove repeats for 6 bars
8 bars (a b) Brackets group: a then b, repeated for 8 bars

Without a length, a pattern lasts until its lines line up again, and a play lasts as long as the longest thing in it. A play can be longer than its lines, and the rest is silent: play 4 bars { crash: 1 }.

Whatever repeats has to fit what it's in a whole number of times. Lines of different lengths drift against each other, which is how you write a polyrhythm, and the pattern's length has to be one where they line up:

pattern poly = 15 bars {
  kick: x---
  floor: x--
  snare: x----
}

With 4 bars that's an error, and it says the lines line up every 15 bars. What's set or named inside braces stays inside them.

Playground

The same language runs in the composer-nb playground, a notebook-style web app you can use in the browser with nothing to install. Its source is in the playground/ folder of the repository.

Developing

This package lives in the dsl/ folder of the repository. The parser and audio engine are JavaScript (dsl/js/), and the Python side (dsl/python/composer_nb/) passes cell sources to them through an anywidget. Build the widget before installing:

npm install
npm run build -w dsl
pip install -e "dsl[test]"
pytest dsl/tests/python

Metadata

Release files for composer-nb 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for composer-nb 0.2.0
File Size Uploaded Provenance Actions
composer_nb-0.2.0.tar.gz 167.0 kB With provenance Details for composer_nb-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for composer-nb 0.2.0
File Interpreter ABI Platform Actions
composer_nb-0.2.0-py3-none-any.whl Python 3 none any Details for composer_nb-0.2.0-py3-none-any.whl

Total release size: 335.0 kB

Release files / composer_nb-0.2.0.tar.gz

Download URL composer_nb-0.2.0.tar.gz
Size 167.0 kB
Tags Source
SHA-256 checksum
How to use checksums
22315d2676bab33184c8bb7ecb3292c97abaa648f12a8f4a223bd79a48cf5205
BLAKE2b-256 checksum
How to use checksums
19fe2b7a5774a7b8c974be0dbfc59bd4b69d1652c1b0ad1f593670929e79a2c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.

Transparency log

Release files / composer_nb-0.2.0-py3-none-any.whl

Download URL composer_nb-0.2.0-py3-none-any.whl
Size 167.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4fb5ac966ed7db4c3a31d2f99b78ff6e2e39bbb2e8529106fed5b50bca22b657
BLAKE2b-256 checksum
How to use checksums
87c36ee71bd65fcfec7f0dc9ec28f8eed6cbb7dfef3d914180d9cec65775f2fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.

Transparency log

Security for composer-nb 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for composer_nb-0.2.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page