Skip to content

Vibrai v1.6.3

Latest
Latest

Choose a tag to compare

View all tags
@gitizenme gitizenme released this 19 Aug 15:36
· 2 commits to main since this release
v1.6.3
141b932
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A fix release, and the fixes are audible. Five drum part types have been quietly generating the same rhythm as each other since they shipped; break and fill placement has been counting in 4/4 on sets that aren't. Both are corrected here — which means some presets now generate different notes than they did in 1.6.2.

Your crash, fill and percussion stop copying the kick

HiHatPlus, Percussion, Crash, Fill and Roll had no Euclidean cell of their own, so all five fell back to the same generic 4-pulse pattern. A crash hit, a drum fill and a shaker part produced the literal identical rhythm, differing only by seed and pad.

Each now has its own cell, authored per part and checked by ear: sparse loud accents for Crash, dense pre-transition activity for Fill, off-grid movement for Percussion.

This changes generated output. Any preset using those five part types will produce different notes than it did in 1.6.2. Every other part type is untouched.

Bars that land where your meter says

BreakOverlay computed step offsets from a hardcoded 4/4 sixteenth, even though it already carried the real meter and derived bar boundaries from it. At any non-4/4 meter, step N landed on the wrong beat. Break and fill steps now use the same grid the rest of generation does — which also realigns them with the shadow kick grid they are supposed to lock to.

The installer stops refusing while Live is open

It used to exit with an error if Ableton was running, which is a support ticket for something you can solve yourself. Now it warns, proceeds, and tells you to restart Live.

That matters because Live reads the Vibrai device and the remote script at startup. Install over an open Live and the new files sit on disk unused. The installer can't tell you that — nothing inside a macOS package reaches your terminal — so vibrai version does:

vibrai version

It now names any bridge serving a different build than the CLI and tells you to restart Live. Believe it over the installer's "successful".

Three JSON fields that were reporting the wrong number

If you script against Vibrai's --json output, read these — each is a breaking change to a value you may have compensated for:

  • scene_index was reported raw and 0-based by notes set / notes add and their MCP siblings, while track_id beside it was already converted to the 1-based wire format. The write itself was always correct; only the reported number was off by one. If you were subtracting 1, stop.
  • automation render emitted a raw Live track id, a convention belonging to the older automation apply. It now matches render_automation, which never had the ambiguity.
  • generate returned warnings: null when there was nothing to report, while plan returned [] for the same key. It is always an array now. Code branching on warnings === null will take the other branch.

Also in this release

  • 12 shipped genre files carried automation: blocks that pointed at nothing and were silently skipped every render. Removed.
  • vibrai update can no longer leave you with new CLI binaries and an untouched Ableton device — the Ableton-side reinstall now runs before the binary swap, not after.
  • The MCP user guide documents the eight generate-time style knobs (swing, humanize, ornament_density, dropout, gate, native_randomization, bass_motion, kick_relation). They were only in the older combined guide before.
Full list of merged pull requests

What's Changed

Full Changelog: cssllcio/Vibrai@v1.6.2...v1.6.3

Contributors

gitizenme
Assets 11
Loading