AIVA MIDI Import: Arrange Your Melody or Use It as an Influence

You have a melody in a MIDI file and want a fuller arrangement. Before using AIVA, decide whether the exact notes must survive. Importing your notes for editing and uploading music as an influence are different jobs. Choosing the wrong one can produce an attractive composition that no longer contains the melody you meant to arrange.

Download the melody and arrangement map · Explore an arrangement in Music Lab

Feature information checked September 17, 2026. The downloadable melody is an original practice file created for this guide; its structure was checked locally, but it was not imported into AIVA during this research. The hero is an AI-generated editorial illustration.

Choose between importing notes and influencing a composition

AIVA’s general user manual distinguishes MIDI import from Upload Influence. The editor provides note and instrument controls, while an influence is used to create a new composition. Treat the latter as inspiration, not a promise to preserve the original notes exactly.

A MIDI file describes musical events; it does not contain the sound of the instrument that originally played them. Even perfectly preserved notes can sound very different when rendered through another instrument. Compare the note data and the listening result as two separate checks.

Start with an eight-bar melody you can inspect

Download the original eight-bar practice MIDI. It contains one monophonic melody track at 96 BPM in 4/4, with no pickup. Eight bars take twenty seconds at that tempo. The file is deliberately sparse so you can hear what an accompaniment adds or obscures.

The table uses scientific pitch notation, with middle C written as C4. Some editors label octaves differently; MIDI note numbers are the reliable reference. The starting note is MIDI 60. Quarter and half refer to note lengths, not seconds.

You can use your own eight-bar idea instead. Keep its reference score or a simple piano render so you have an independent way to check the import. If the MIDI came from audio transcription, clean obvious errors before treating it as an exact musical source.

Prepare the file according to the route you chose

For direct editing, name tracks by role and inspect overlapping notes, accidental extra notes, and unexplained tempo changes. A file that plays correctly in one application may rely on instrument or controller settings another application interprets differently.

AIVA’s Upload Influence guidelines recommend at least eight bars, separate parts on separate tracks, quantized notation, and channel 10 for percussion in that influence workflow. These are influence-preparation guidelines, not a claim that every direct MIDI import has the same requirements. Confirm the route before applying them.

Quantization means aligning events to a rhythmic grid. Do not erase an intentional performance feel simply because a guide mentions a grid. For this practice file, the notes are already aligned and the timing is straightforward. For expressive playing, keep the original file before preparing a simplified influence version.

Inspect the imported melody before adding anything

Open the imported material in AIVA’s editor using the available project controls. The current manual describes opening compositions in the editor and working with pitched or percussion layers, notes, and instruments. Interface labels can change, so use the route that opens the actual imported note material rather than launching a new influence generation.

1. Confirm the tempo and the start of the first bar.
2. Check the opening note and the upward gesture in bar one.
3. Inspect the rest in bar four and the longer final note in bar eight.
4. Play the melody alone with a simple instrument.
5. Save an untouched reference version before arranging.

Those checks are deliberately spread across the file. A correct first bar does not establish that the entire import is correct. Also inspect whether note lengths overlap in a way that creates unintended sustained harmony.

Add one accompaniment role at a time

Begin with a quiet sustained harmony layer. Its job is to support the melody without occupying every rhythmic gap. Keep the melodic range clear, especially around the upward gestures. If the accompaniment makes the tune harder to follow, simplify its register, rhythm, or level before adding another instrument.

Next, consider a bass part with a limited role: establish the harmonic foundation and support phrase changes. It does not need to mirror every melody note. A bass line that follows all the upper movement can make the arrangement feel busy without providing a stable foundation.

Add percussion only if the intended use needs it. The practice melody already has a readable pulse. For a quiet gallery cue or reflective montage, an extra drum layer may add little. A fuller arrangement is not automatically a better arrangement.

Where AIVA offers generation or inpainting for layers, inspect the target layer and region before applying it. Keep the original melody reference visible. Do not assume that adding accompaniment means no other note data can change in your workflow.

Compare note preservation and musical balance separately

First, compare the melody’s pitches, onsets, and durations against the original. Then listen to the complete arrangement. An unchanged melody can be masked by a bright instrument or a dense accompaniment, so data preservation alone is not enough.

Use a simple listening test: play the arrangement once, then try to hum the opening gesture. If you remember only the accompaniment, reduce competing movement or change register. This is a practical editorial check, not a formal measure of composition quality.

Review the ending with its final rest intact. Accompaniment that rushes into a new phrase can undermine the melody’s closure. Let the last note decay and make an intentional decision about how the exported cue ends.

Export the material your next tool actually needs

If you plan to continue arranging, check whether your current AIVA plan and workflow provide the MIDI export you need. If you need a finished cue, inspect the rendered audio format and applicable usage terms. Availability and permissions can change, so avoid planning a commercial delivery around an assumed free-plan entitlement.

Reopen the exported file and check duration, start time, and the final tail. Keep imported source, arrangement project, and rendered audio distinct. They represent different stages and make later corrections easier.

Use QuestStudio Music Lab to explore a separate arrangement’s mood or instrumentation. The exact MIDI import and note-editing steps in this article take place in AIVA; they are not claimed Music Lab features. For MIDI extracted from generated audio, the MIDI cleanup guide helps prepare the source before arranging.

Frequently asked questions