AU + VST3 plug-in · macOS & Windows
MidiVerse indexes your entire MIDI and sample library once — then sorts it, classifies it, and lets you search, preview, edit and generate inside your DAW, without ever leaving the session.
LOGIC PRO · CUBASE · ANY AU / VST3 HOST
The Library
MidiVerse analyses every MIDI and audio file in your folders a single time and keeps the index in one central store. After that, searching tens of thousands of files is instant — and up to four source folders are searched as a single library, with files staying exactly where they live.
Results are organised the way songs are built — Intro, Verse, Pre-Chorus, Chorus, Hook, Bridge, Breakdown, Build, Drop, Fills, Outro — detected from file and folder names, with a part filter and jump-to-section when you need one piece fast.
Tick any combination of genres in the sidebar and the list narrows live. Key, tempo, length and family filters sit alongside, and merged results show which source folder each file came from.
Preview in place, load into the built-in editor, or drag a file out onto a track. Dragging hides the editor window for the duration, so the drop target is never covered.
The library reopens with your last results already in place instead of rebuilding from scratch, and a refresh that would shrink the index suspiciously is held back — Reindex is the deliberate, full rebuild.
A small sample catalogue showing how search, type, genre and part filters combine. The real plug-in does this across your whole indexed library.
Sorting & organising
Point MidiVerse at a folder and it sorts thousands of files in parallel — from the index when it's fresh, without reopening every file. Sorted copies land in one central output store, organised and named; your originals are never moved or deleted, and every job can be undone.
Files are classified and filed into genre folders — by rules, by your tags, by what the plug-in has learned from your corrections, or by the trained AI model.
MIDI is read for the drum classes it actually contains and filed by combination — kicks, hats, snares and full kits land in folders named for what's inside.
Near-identical loops and variations are grouped together, so the twelve versions of the same idea sit in one folder instead of twelve different ones.
Exact and near duplicates are pulled into their own review folder, so you decide what to keep with everything in one place.
Audio sorts by duration and family, with rename, trim, split, reverse, fade and convert tools alongside — plus a starter pack builder that round-robins genres into a ready-to-use collection.
Every sort and transform is snapshotted first. Changed your mind? One Undo restores the store to how it was — the source folder is never touched.
The Editor
Load any file from the library into the built-in editor — MIDI on the grid, audio on the waveform — and shape it without exporting, converting or switching apps.
Drag a rubber-band selection and every note it touches lights up live. The highlighted section loops automatically — and both the selection's and the loop's edges can be dragged to extend or shorten the span, right in the grid.
The view pages itself to keep the playhead visible, and the on-screen keyboard — which opens centred on middle C — jumps to follow any note played, from the grid or your controller.
Grid edits carry a 40-step undo/redo stack; whole jobs like sorts are undone from the store snapshot. Nothing is one-way.
Eleven actions — Play, Stop, Record, Sort, Reindex, Library, MIDI Out and more — on a fixed map with MIDI Learn and presets for popular controllers. Continuous controls like preview volume and tempo follow live.
Transport audition locks to the host: the render is rotated to the DAW's current phase and looped, and when the DAW stops, the editor parks its playhead exactly where the host stopped.
Capture ideas as Takes straight from the plug-in, or send playback out over MIDI — to a hardware port, a virtual port like loopMIDI, or (in the MIDI variant) directly to the track it's inserted on.
If the host goes down mid-job, an interrupted index resumes on next launch instead of starting over — other jobs are reported, never silently restarted.
The sound you pick for library previews is the sound the editor plays with. No more auditioning with one instrument and editing with another.
Local AI · No cloud
MidiVerse trains a small neural network — 70 musical features, one hidden layer — on the folder you point it at. It only overrules the built-in rules when a file is untagged and the model is at least 60% confident, and training and inference happen entirely on your machine. Your library never leaves your computer.
32 GENRES, INCLUDING
The same classifier covers audio: train it on your sample folders and it files one-shots and loops by genre too.
Pattern generator
Pick a style, key, scale, length and tempo, and MidiVerse writes a complete pattern — drums, bass, chords and a synth part — straight into your chosen folder and loads it into the editor. Split it into separate files and they still share one seed, so the parts line up perfectly.
MidiVerse scans your AU and VST3 instruments and lists them in one Sound picker — sforzando and your SFZ libraries included. Pick once; library previews and editor playback both use it.
LUFS normalise, time-stretch to tempo, write tags, trim, split, reverse, fade and convert — production housekeeping done in bulk, in place, with undo behind it.
The Catalog view unions your stores — home, OneDrive, up to three extra roots — into one list. Play or drag a file and it's pulled down and cached automatically; push a folder once with “To cloud” and it's there on the next machine.
Two variants
MidiVerse ships as two plug-ins that can sit in the same session: the full audio version for browsing, previewing and editing, and a pure-MIDI variant built for Logic's MIDI FX slot and track playback.
Audio effect · AU + VST3
MIDI effect · AU + VST3
Questions
No. Sorted, grouped and transformed copies are written to one central MidiVerse output store — on your home folder, OneDrive, or a custom folder you choose. Source folders are only ever read, and every job keeps a snapshot so it can be undone.
No. The genre model is a small neural network that trains and runs locally on your machine, on the folders you choose. There is no cloud AI in MidiVerse. The optional Catalog feature only copies files between store folders you configure yourself.
MidiVerse ships as AU and VST3 for macOS and Windows. It is in daily use in Logic Pro — including the MIDI FX slot — and works in Cubase, where the reliable route for MIDI-out playback is a virtual port such as loopMIDI on an instrument track.
It was built against a real working library of more than 51,000 audio files plus tens of thousands of MIDI files. Indexing is incremental — a refresh only analyses what's new or changed — and files that turn out to be undecodable are remembered, so they aren't retried on every pass.
Any of yours. MidiVerse scans the AU and VST3 instruments already on your system and lists them in a single Sound picker, alongside sforzando for SFZ libraries. One pick covers library previews and editor playback alike.
Yes — that's what the Catalog is for. Point the stores at a shared folder such as OneDrive, push files with “To cloud”, and the second machine sees the union of every store, pulling and caching files as you play or drag them.
MidiVerse
MidiVerse is in active development for macOS and Windows, tested daily in real Logic Pro and Cubase sessions against a working library of more than fifty thousand files.