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
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.
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.
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.
Link to jsFiddle, CodePen, Project
No public minimal example is available in this report.
Version and Environment
alphaTab 1.10.0 develop, commit ec751a23f2e1f9601abb3ce2022300001c096565; Node.js 24.22.1 on Windows.
Activity