Basic Usage

Basic Usage

The normal workflow

1. Choose one local audio file.
2. Select CPU or GPU mode.
3. Review the output-related settings if needed.
4. Start the conversion.
5. Open the generated MIDI file and review it in a MIDI-capable application.

A2M processes one selected file at a time. Choosing a file does not immediately decode or transcribe it; decoding begins when conversion starts.

Controls that affect the result

Control	What it changes
Pedal events	Includes or excludes model-produced sustain and soft-pedal controller events from the exported MIDI.
Expressive dynamics	Uses the velocity selected by the transcription model for each note.
Uniform dynamics	Replaces every exported note velocity with the chosen value from 1 to 127.
Output location	Selects the folder in which completed MIDI files are reserved and written.

CPU usage and GPU memory controls affect resource use and batching, not the musical interpretation requested from the model. GPU mode also uses the same model and decoding path as CPU mode.

During conversion

The status area reports the active engine, runtime, resource settings, pedal choice, dynamics choice, progress, and an estimated time remaining when enough progress information is available.

You can request that conversion stop. Cancellation is cooperative: A2M checks for it between decoding, feature-processing, inference, and output steps, so it may take a moment to finish the current operation. A canceled or failed conversion does not intentionally leave a partial MIDI file at its reserved output name.

Output behavior

A2M derives the MIDI name from the source filename and removes characters that Windows cannot safely use in a filename. It never intentionally overwrites an existing result. Name candidates are tried in this order:

recording.mid
recording_2.mid
recording_3.mid
...

The MIDI contains one Acoustic Grand Piano instrument track. Notes use MIDI pitches and velocities; supported pedal predictions are written as MIDI controller events.

A practical review checklist

After importing a result into a DAW or notation program, check:

• missed or extra notes;
• repeated notes of the same pitch;
• note endings and legato passages;
• very quiet notes;
• chords with closely spaced attacks;
• sustain and soft-pedal changes;
• dynamics that need musical rather than literal adjustment.

See Accuracy, Limitations and Best Results for why these areas can be difficult.