Skip to main content

groovebin

A drum groove programmed for one kit plays the wrong sounds on another, a folder of thousands of patterns can only be browsed by file name, and a bassline has to be written against the drums by hand. groovebin does these jobs on the MIDI files themselves, in Python, with no DAW or plug-in installed or running.

It reads and writes Standard MIDI Files and keeps every event in them. It translates notes between instrument maps, so a groove made for one kit plays on another: General MIDI drums, Addictive Drums 2, Logic's Drum Kit Designer and its brush kits, and EZbass's keyswitches. It transforms notes by selection (velocity curves, humanize, swing, note lengths) and lays one part's feel on another. It indexes a folder of patterns so they can be searched by section, meter, tempo and feel, or ranked by how close their rhythm is to a groove you give it, and it strings real bars together into new phrases.

For bass, it reads the chords a bassline implies, reports how a line sits with the kick and with the chords, and writes a new line over a drum part, by rules or by picking real bars from a bass library and moving them onto your chords. On the 1,256 grooves EZbass installs, the root it reads from each bassline matches the bass note of EZbass's own chord labels on 89.7% of beats; that is one vendor's library, and other styles may read differently. It calls a chord major or minor only where the bass plays the third.

Status: alpha. Commands, the library API and the index format may change before 1.0.

Install

pip install groovebin
groovebin --version

Needs Python 3.12 or newer.

Commands

groovebin remap IN.mid --from drum-kit-designer --to addictive-drums-2 -o OUT.mid
groovebin notes IN.mid --map gm
groovebin transform IN.mid -o OUT.mid --preset humanize --seed 7
groovebin index ~/Grooves --map addictive-drums-2
groovebin search --role verse --meter 4/4 --tempo 90-110
groovebin generate --meter 4/4 --bars 16 --fills --role verse -o verse.mid
groovebin search --like 3f2a9c --beat
groovebin feel programmed.mid --from played.mid --map gm -o felt.mid
groovebin bass --drums verse.mid --drum-map gm --chords "| Am | F G |" -o bass.mid

Usage: docs/usage.md. Python API: docs/api.md. Changes: CHANGELOG.md.

Develop

From a checkout:

bin/run setup
bin/run pytest
bin/run lint        # ruff + the pf-core structural gate (300 soft / 500 hard lines)

See CONTRIBUTING.md.

groovebin ships note-number tables only: no sounds, patterns or MIDI content from any vendor.

Metadata

Release files for groovebin 0.4.1

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

Source distribution (sdist)

Source distribution for groovebin 0.4.1
File Size Uploaded
groovebin-0.4.1.tar.gz 89.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for groovebin 0.4.1
File Interpreter ABI Platform
groovebin-0.4.1-py3-none-any.whl Python 3 none any Details

Total release size: 193.3 kB

Release files / groovebin-0.4.1.tar.gz

Download URL groovebin-0.4.1.tar.gz
Size 89.4 kB
Tags Source
SHA-256 checksum
How to use checksums
da956813fe8e0acf712ee0027417a045192b0758a41f0412a1312e4049e0a78e
BLAKE2b-256 checksum
How to use checksums
c1a613f84d10931bfec242f7f6da25b59a60e765377534cfed7f96209da1d584
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 1, 2026.

Transparency log

Release files / groovebin-0.4.1-py3-none-any.whl

Download URL groovebin-0.4.1-py3-none-any.whl
Size 103.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
df8846b71982708222c808b813b450ce1e3179ce43eb2c4c8643a9fbf82198bd
BLAKE2b-256 checksum
How to use checksums
aaf2dfdcb3d988d1f6da685586efcc9a44ba1f42b246e6596fc963ea250ddea4
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 1, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.0

2 release files

This release

0.4.1 This release

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

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