You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Guitar Pro round trips discard per-note velocity metadata #3021
Portions of this content were authored by an AI agent. The agent has read AGENTS.md and the human submitter accepts responsibility for
compliance with the rules in that document.
Current Behavior
In our MIDI-to-Guitar Pro workflow, notes can have different MIDI velocity values, representing how softly or strongly they were played. We want to keep these differences when working with the resulting score.
We found that when a Guitar Pro file already contains per-note velocity values, alphaTab drops those values when the file is imported and exported again.
Expected Behavior
Per-note velocity information in a Guitar Pro file should be preserved during an alphaTab import/export round trip, so it remains available to applications that use the exported file.
Steps To Reproduce
Start with a Guitar Pro file containing different per-note velocity values, for example a score prepared from MIDI notes played with different strengths.
Import the file into alphaTab and export it again as a Guitar Pro file.
Compare the per-note velocity values in the original and exported files: the exported file no longer contains those values.
Version and Environment
alphaTab 1.10.0 develop, commit ec751a23f2e1f9601abb3ce2022300001c096565; Node.js 24.22.1 on Windows.
Platform
Node.js
Further details
Draft PR #3022 proposes preserving the Guitar Pro velocity fields. It does not currently change MIDI import, how velocity is displayed, or alphaTab playback; those parts of the workflow need separate verification.
Thanks for opening this. Before we dig in, a couple of things need addressing in the description:
Complete the 🕷️ Bug Report template. The description is missing sections of the 🕷️ Bug Report template: Is there an existing issue for this?, I have read the contribution rules, AI authorship, Link to jsFiddle, CodePen, Project, Anything else?. Please include them — even a short answer keeps the report actionable.
If the description isn't updated within 7 days, this issue will be closed automatically and labeled state-rules-not-followed. Reopen any time — an edit to the description is all it takes.
If an AI helped draft this, AGENTS.md covers the same expectations from the AI side.
Activity
github-actions commentedon Nov 8, 2026
Thanks for opening this. Before we dig in, a couple of things need addressing in the description:
Is there an existing issue for this?,I have read the contribution rules,AI authorship,Link to jsFiddle, CodePen, Project,Anything else?. Please include them — even a short answer keeps the report actionable.If the description isn't updated within 7 days, this issue will be closed automatically and labeled
state-rules-not-followed. Reopen any time — an edit to the description is all it takes.If an AI helped draft this,
AGENTS.mdcovers the same expectations from the AI side.