Skip to content
Guitar Prometheus

Getting Started

Getting Started

This guide walks through your first export end-to-end: from opening a MusicXML file to dropping the resulting MIDI on top of a VST in your DAW.

Prerequisites

  • A Guitar Pro score in one of three formats:

    • .musicxml / .xml — exported from Guitar Pro 8 via File -> Export -> MusicXML.
    • .gp — native Guitar Pro 7 / 8 file. No export step needed.
    • .gpx — native Guitar Pro 6 file. No export step needed.

    See Native Import for which techniques each format preserves.

  • A DAW with at least one guitar / bass VST that supports keyswitches — Shreddage 3, Ample, Spitfire, Odin III all work.

Open a Project

  1. Launch Guitar Prometheus.
  2. File -> New Project… and pick your score file. The dispatcher picks the right importer based on the file extension.

The track list appears with one row per score part. Each row shows the part name, the GM patch byte (or “Drum Kit” for percussion parts), and an empty Profile column.

You can also drag a score file onto the window — the New Project flow runs automatically.

Bind a Profile

A profile is the contract between a part and your VST: which keyswitch notes trigger which techniques, what velocity to fire them at, what note-name maps to each drum piece. Out of the box, the profile list is empty.

  1. File -> New Profile… mints an “Untitled Profile”. The editor opens with it pre-selected.
  2. Walk the tabs (Techniques, KS Velocity, Articulations, Articulation Mods, Articulation KS Velocity, Velocities, Drum Map) and fill in the keyswitch notes your VST expects.
  3. Save to write the profile to disk.
  4. Close the editor. In the track list, click the part’s Profile column and pick the new profile from the dropdown.

For a step-by-step on what each tab does, see Profile Binding.

Adjust Tempo (Optional)

File -> Edit Tempo Map… opens the tempo editor. Each measure has a Beat picker (1.0 … N.875 in 32nd-note steps) and a BPM field. Setting a BPM at any sub-beat position adds an override that fires at that absolute MIDI tick on export. Reset clears the override and falls back to the score’s parsed tempo.

Export

File -> Export… opens the export dialog. Pick:

  • Output mode: per-track (one MIDI file per part) or merged (one Format 1 file containing every part on its own track).
  • Output path: where to drop the file(s).
  • Per-part octave offsets and humanizer settings (velocity sigma + timing jitter) if you want them.

Hit Export. The export log shows any parser warnings + any tracks that hit “no profile bound” (those export raw — no keyswitches injected).

Drop the resulting .mid onto the corresponding VST track in your DAW. The keyswitches drive the technique articulations — palm mutes thunk, let-rings sustain, hammer-ons and slides resolve as legato.

Save the Project

File -> Save Project As… writes a .gpproj containing the embedded source payload (in its original format — MusicXML, .gp, or .gpx), your track bindings, tempo overrides, and export settings. Open it later via File -> Open Project… or the Open Recent submenu — every format round-trips through the project file.