Skip to content

Guitar Pro round trips discard per-note velocity metadata #3021

Closed as not planned

Description

@sgabenov

Note

AI-authored disclosure (alphatab-ai-authored-v1)

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

  1. Start with a Guitar Pro file containing different per-note velocity values, for example a score prepared from MIDI notes played with different strengths.
  2. Import the file into alphaTab and export it again as a Guitar Pro file.
  3. 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.

Is there an existing issue for this?

  • I have searched existing issues for Guitar Pro velocity reports; I did not find an obvious duplicate.

I have read the contribution rules

  • I have read CONTRIBUTING.md and AGENTS.md.

AI authorship

AI-assisted (disclosure block included above).

Link to jsFiddle, CodePen, Project

No public minimal example is available in this report.

Anything else?

The scope and current limitations of the draft PR are described in Further details above.

Activity

  1. github-actions commented on Nov 16, 2026

    @github-actions

    Closing automatically — the description wasn't updated within the 7-day grace period, so state-rules-not-followed is applied and this issue is closed.

    The earlier bot comment lists what needs fixing. Reopen any time by updating the description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    Priority

    None yet

    Area

    None yet

    Platform

    None yet

    Work State

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions