Plugin — Mivia Sign

HOW IT WORKS

Forget it's there.

Drop Mivia Sign on the master bus. Bounce a draft, a stem, a final, an alt — every one gets fingerprinted and lands in your library, with everyone you signed with credited automatically.

0 Bytes
modified in your audio: 0 Latency
added to bounces or playback: 0 Changes
to your audio

FINGERPRINT

It reads. It doesn't write.

The plugin computes an acoustic fingerprint from your bounce and stores it in your library. Your audio file is never modified, never re-encoded, not even stored by us. We only keep the fingerprint itself to read in /scan.

Want the inaudible watermark embedded into the audio? That's /sign.

COLLABORATORS

Credit, on the spot.

Anyone in the room can sign on. No emails. No apps. No wait.

Open the plugin's QR pane. They scan with their phone. They sign in to Mivia. They're on the next bounce.

That's it. The track ends up in everyone's library. Every contributor, automatically credited.

LIBRARY

Already saved.

Every bounce ends up in your library. Yours under Mine; your collaborators' under Collaborations. Each one gets a public verify link you can drop in liner notes, send to a label, or use to settle a credit dispute years later.

INSTALL

Pick your platform.

Two installers. Both ship every plugin format and the Mivia helper binary. Both finish in under a minute.

FormatsAU · VST3 · CLAP

DAWsLogic · Ableton · Cubase · Pro Tools · Reaper · Bitwig

MinimummacOS 11 Big Sur

Archarm64 (Apple Silicon)

Ships as a .pkg. Double-click to install; use the Customise panel to untick plugin formats you don't need. The Mivia helper installs by default and handles bounce-filename capture via Accessibility permissions — if you skip it, bounces still sign, they just appear as "Untitled bounce" in your library. v1 is unsigned — Gatekeeper will warn "unknown developer"; right-click the .pkg and choose Open to approve (one-time prompt).

FAQ

Before you insert it.

The things a producer asks before trusting any plugin with their master bus.

Does it add any latency?

No. setLatencySamples(0) is hard-coded and the audio path is a true passthrough. Fingerprinting runs on a side chain, never in the mix signal. Your offline bounces are bit-identical to bounces without the plugin.

Does it alter my audio in any way?

No. The plugin is fingerprint-only — it uploads your bounce so the server can compute a Chromaprint acoustic fingerprint, then stores that fingerprint plus your session metadata against your account. No watermark is embedded, no file is written back to disk, your original bounce stays bit-identical to one made without the plugin. The watermark-embedding path is the web signer.

What happens if my internet drops mid-bounce?

The bounce completes, audio passes through unsigned, you see an error chip on the plugin. Nothing is queued for later upload. Your next bounce tries again from scratch.

What data is uploaded, and where does it go?

The rendered audio is posted to our signer endpoint for the duration of signing, plus the metadata listed in "What's captured". The audio is not persisted server-side after the signed WAV streams back. Nothing else leaves your session.

Can I run it on more than one machine?

Yes. Each install gets its own PKCE token tied to a device name you pick. You can revoke a single install from /account without affecting the others.

Does it work with offline bounce in Logic / Ableton / FL?

Yes, and those four DAWs plus Reaper are covered by our automated render harness — meaning every plugin build is bounce-tested in the real host before shipping. Cubase, Bitwig, and Pro Tools are supported but covered by manual testing.

What's the difference between this and the web uploader?

The plugin signs every bounce inside your DAW, automatically, with metadata the web flow can't see (host, BPM, render mode). The web uploader is a drag-and-drop for files you already have — use it for one-offs, files from other producers, and per-recipient share lists the plugin doesn't cover.