musescore / musescore/MuseScore

Imported harmonics from Guitar Pro are overlapping with vibrato

Open
#34,683 1 comment 0 reactions 2 assignees View on GitHub

@miiizen is already working on this.

Since Aug 25, 2026.

engraving guitar P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Import/export issue

Description with steps to reproduce

Reproduced with .gp file where feedback type of harmonics was added to multiple notes, for example: Fdbck with vibratio.gp.zip
This element is added only for imported .gp files to cover the harmonics from the Guitar Pro.

Steps to reproduce:

  1. Open the attached file in the MSS v4.7.4
  2. Note the lines' overlap in the 15th measure and further
  3. Go to the 10th measure
  4. Add a section break

Actual result:

  • "Fdbck" line collides with vibrato line in the 15-17th measures
  • "Fdbck" line also collides with vibrato line in the (yet there is a problem with measure numbering in case of this imported file, so i'm not sure that section break is the cause of this overlap, attached screencast)

Expected result:
No collisions

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/34522d7f-82fd-4519-b61e-8c600cc854c3

In which versions of MuseScore Studio is this issue present?

4.7.4

Regression

No.

Operating system

macOS Tahoe 26.5

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.