vinsynlib

The shared base of a family of terminal instrument browsers.

Nine sibling programs browse nine instruments over MIDI from a terminal: emorphed (E-mu Morpheus), ensqsqed (Ensoniq SQ-R Plus), eosed (E-mu E4XT), kwsed (Korg Wavestation SR), nanosyned (Alesis NanoSynth), p2ked (E-mu Proteus 2000), rxved (Roland XV-2020), s3ked (Akai S1000/S3000) and x5ded (Korg X5D/X5DR).

They grew separately, which is the right way to learn what an instrument does and the wrong way to arrive at nine copies of the same code. This library is where the parts that are not the manufacturer's live, so that a change to one of them happens once instead of nine times.

Support this project

is free software and always will be. Nothing is behind a paywall, no feature is withheld, and none of what follows changes that.

But if it has been useful — if it saved you an evening of mapping zones by hand, or got a library onto a machine that had no way of reading it, or best of all, if it has your vintage instrument switched on and in use more often than it was, and you are having more fun with it — then please consider supporting the work.

Because here is what it has actually cost:

• Real machines on a real bench. Much of what these tools know about these formats was measured on hardware rather than read anywhere, because for most of it there is nowhere to read it. That needs the machines — the instruments themselves — and it puts hours of wear on hardware that has been locked up and recovered more than once in the course of it. Some of these instruments were bought specifically to add and verify a format; the others were already here, because the person doing this is a vintage instrument enthusiast first and the projects exist because the instruments were in the room.
• Dozens — realistically hundreds — of hours of human time. Format reverse-engineering is slow: measure, be wrong, measure again. A single parameter law in this README can represent an evening at the bench.
• AI assistance, which is a paid service, used heavily throughout and not cheap at this volume.

This is support, not a donation — and the distinction is a legal one, not a turn of phrase. The maintainer is based in Germany, where payments like these are not Spenden in the tax sense: they count as taxable income for the recipient and are not tax-deductible for the giver. So this section is titled Support, deliberately, and no receipt for tax purposes can be issued. (That is a statement of how it is handled here, not tax advice.)

If the project saved you the work, you can support it through GitHub Sponsors — the Sponsor button at the top of the repository. Payment is handled entirely by GitHub and Stripe, so bank and tax details are never handed to the person paying.

Support is not expected, and it is not the only currency.

• Bug reports — ideally with the bank, preset or disk image that produced them. A tool's failures are usually specific to one file rather than general, and without that file they are very hard to reproduce.
• Confirmations from hardware that is not on this bench, which matters more here than for a single-machine tool. These tools write for whole families of instruments, and the bench holds only a subset. Whether a variant accepts what we write is genuinely unknown, and several notes say "on this unit" for that reason. A "loads fine here too", or a "no, mine refuses it", is worth a great deal.
• Corrections to the reverse-engineering notes. The wrong turns are recorded next to the findings in docs/RESOLUTION_NOTES.md — retractions included, because a finding that was withdrawn is as useful as one that stood. If any of it is wrong in a way that is still costing someone time, saying so improves the record.

AI assistance & human authorship

was built by its human author together with AI assistance. The ideas, the project vision, and every feature came from the human author; AI assisted with writing the code and analyzing the binary formats. Crucially, the reverse engineering rests on hands-on human work — all testing and verification on real hardware, creating the reference images/banks on those instruments (disk saves, SysEx probes), and aural A/B comparison of presets — which is what makes the results correct. Full account in DISCLAIMER.md.

⚠️ Use at your own risk — back up first

is provided as is, with absolutely no warranty and no liability for data loss or hardware damage. You assume all risk. Full terms: DISCLAIMER.md.

Before you use this software, make good, current backups of all your files — and of any existing banks on your instrument and storage media. These tools can write to hardware and storage media; a mistake, a bug, or untested output could overwrite or corrupt data, or be rejected by hardware. Always test on a spare unit or emulator before connecting irreplaceable equipment.

What is in here, and what is not

In here: how a preference is remembered, where a favourite lives, what an error says, which key means what, how a port list is printed, how a legend wraps.

In each project: the wire format, the bank table, the meaning of a byte, the LCD glyphs.

The line is ours versus the manufacturer's. A MIDI port name is whatever ALSA reports, so the port listing is shared; which SysEx byte selects which bank is that instrument's business and stays put.

vinsynlib/
  config.py        the settings cache: port, channel, device ID
  favorites.py     the favourites database: SQLite, slots, ratings, tags
  keys.py          the keymap and the legend
  cli.py           the command line every tool builds the same way
  spec.py          that command line, as data: flags, commands, exit codes
  terms.py         the vocabulary: our words, and each tool's two
  midi.py          port listing, the shared error taxonomy, clean exit
  conformance.py   the checks a project runs against itself
  devchecks.py     checks that catch cross-project mistakes
  ui/hints.py      the legend widget

Installing it, and who depends on it

This is a library, not a program, and it is not on PyPI yet. The ten tools in the family depend on it, so it has to be a sibling checkout of whichever one you are building:

git-repos/
  vinsynlib/     <- this one
  x5ded/         <- and the ten tools beside it
  emorphed/  ensqsqed/  eosed/  kwsed/  ...

cd ../x5ded                     # or any sibling
git clone https://github.com/lentferj/vinsynlib.git ../vinsynlib
python3 -m venv .venv
.venv/bin/pip install --no-deps -e ../vinsynlib   # --no-deps: its deps are theirs
.venv/bin/pip install -e .

Each of the ten writes those steps out in its own README, because a reader starts from the tool and rarely from here. For projects that configure [tool.uv.sources] pointing to this library, uv sync takes the path from there, so the checkout only has to exist and neither pip line is needed. For projects that work from an index (like the published tools), the explicit pip install -e ../vinsynlib line remains necessary until the library is published.

Publishing this to PyPI would replace all of it with an ordinary dependency line. Until then, the sibling checkout is the install.

Why it exists

Nine projects each grew a config.py (about 190 lines, 90-97% identical), a favorites.py (about 620 lines, 85-100% identical), a KeyHints widget and a wrap_blocks helper. Measured across the family: 8,101 lines of cloned code, roughly 6,300 of them duplicates that need not exist.

Three of those copies had already drifted into bugs worth naming:

• emorphed's LICENSE file opened with the words "nanosyned — Terminal browser for the Alesis NanoSynth".
• emorphed's mypy and deptry configuration still named the nano module, and one function imported nano.config -- nanosyned's package, which is not installed beside it. That function worked in the project it was copied from and raised ImportError the moment --config was used.
• eosed wrote port names into config.toml without escaping them, so a port name containing a quote produced a file that is not TOML -- and its settings writer refuses to overwrite a file it cannot parse, so the cache never healed until somebody deleted it by hand.

None of these were visible in review. They were visible the moment there was a second copy to compare against, which is what this library is.

Using it

from vinsynlib.config import Settings

settings = Settings("x5ded")
channel = settings.load_channel()  # 0-15, or None; a TOML bool is None
settings.save_port("Midi Out: X5D")

from vinsynlib.favorites import Favorites

with Favorites(app_name="x5ded") as favourites:
    favourites.add("A", 7, name="Warm Pad", rating=4, tags="pad")
    favourites.toggle("A", 7)  # clears the flag, keeps the rating

from vinsynlib import cli

parser = cli.make_parser("x5cli", "Browse a Korg X5D's sounds.")
cli.add_common_arguments(parser, port=True, scan=True, channel=True)

Development

$ uv venv && uv pip install -e ".[ui,midi]" && uv pip install \
      pytest pytest-cov mypy ruff vulture deptry detect-secrets pip-audit
$ make check

make check runs the whole gate in order and stops at the first failure: ruff, mypy in strict mode, the test suite with coverage, then vulture, deptry and pip-audit.

Legal: DISCLAIMER.md · LICENSE

Where the rules are written down

docs/UX-SPEC.md is the contract: terminology, the command line, the keys, the paths, the exit codes, and the reasoning behind the parts that are not obvious. It is the document to read before changing anything here, and the document to argue with.

Three things in it are worth repeating, because they are the parts a new contributor is most likely to get backwards:

The instrument's word is the instrument's. Each tool declares the word for a stored sound and for the area it lives in, once, and uses it consistently within itself. A Yamaha says PATCH; an E-mu says PRESET. The unit's word wins, because a tool that renames it has to translate, and a mistranslation is the difference between finding a sound and not.

Our words are the same everywhere. favourite, search, scan, dump, port: no tool invents a synonym for a concept the family owns.

config.toml is disposable; favorites.db is the user's own work. The first lives in the working directory and is safe to delete. The second lives in the platform data directory, is keyed on the slot rather than the name, and is the one file here worth backing up.