MIDI.audio

BEFORE YOU RENDER

Your music.
Your data.

MIDI.audio renders on a hosted service. Here is what is submitted, how it can be used and how to remove a submission. The full rendering and training terms are also shown in the installer.

Uploads begin when you press Render.

The service receives the MIDI file you choose, including every track in an imported file, your selected instrument, render settings and any optional reference audio. Opening the plugin, choosing a file or reading a DAW track does not upload it. Unrelated projects and files are not uploaded.

Submitted music may be used to improve the models.

Submitted MIDI, selected instrument and reference audio are retained and may be used to train, evaluate and improve MIDI.audio’s audio models. Only submit MIDI and recordings you own or have permission to provide for both rendering and model training.

Temporary rendering jobs expire after 24 hours. Training contributions remain until deletion is requested. Local downloaded audio and cached MIDI stay on your Mac. Earlier submissions remain governed by the terms that applied at that time.

You can request removal of stored inputs.

The metadata JSON next to a downloaded take contains its job ID. The installer includes a removal helper and instructions in the DAW handoff guide. Run this on the Mac used for the render, replacing JOB_ID with that ID:

zsh "/Library/Application Support/midi.audio/remove_submission.sh" JOB_ID

The helper asks for confirmation and authenticates with the local installation. Removing stored inputs does not reverse model training already completed. Keep private render metadata out of public issue reports.

Commercial use of rendered music is allowed.

The current terms allow you to use rendered music commercially. This does not grant rights to third-party material in your inputs or permission to resell or redistribute the app or model.

Website measurement.

The landing page does not ask for an account, email address or payment details. The selected audio example loads from this site. Cloudflare hosts the website and processes request information to deliver and protect it.

Cloudflare Web Analytics measures page visits and loading performance. It does not use analytics cookies or track people across websites. Learn about Cloudflare Web Analytics.

We also count page views, download clicks, demo interactions and installation-command copies using a first-party endpoint on this site. We store daily totals by page, button, demo instrument and broad entry-source group for up to 180 days. These counts use no cookies or visitor IDs and store no IP addresses, full referrer URLs, query strings, MIDI, audio, email addresses or render metadata. Cloudflare still processes network information to deliver requests. Browser Do Not Track and Global Privacy Control signals disable these interaction counts. A download click does not tell us whether you installed the app or rendered music.