[Guitar Pro] Regression: GP 5/4/3 files Plays Piano Only

• Mar 13, 2019 - 20:30
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project

If I open a GP file (gp3, gp4 or gp5) all of the instruments use the piano sound. I can save as an .mscz and that file does play correctly when I open it.

I uninstalled 3.04 completely and did a fresh install of 3 different versions with default settings.

MuseScore-3.0.1 - All GP files play correctly with fresh install
MuseScore-3.0.3 - Piano for all instruments
MuseScore-3.0.4 - Piano for all instruments
MuseScore-3.0.5 - Piano for all instruments

Oddly enough in 3.05. If I save the GP file as an .mscz and open the .mscz, the file's instruments play correctly, then if I go back and open the GP file , the GP file's instruments play correctly too. If I close MS and open the GP file without first opening the .mscz file the instruments are again all piano.

This happens on both Mac and Win versions 3.05, 3.04 & 3.03...and as mentioned the GP files open and play correctly in 3.01

Here is a video of the issue
https://streamable.com/h6a4r


Comments

Title Mac & Win version 3.04 & 3.05 Plays Piano Only in GP files [Guitar Pro] Regression: GP 5/4/3 files Plays Piano Only
Frequency Once Few

3.0.5 version: OS: Windows 7 SP 1 (6.1), Arch.: x86_64, MuseScore version (64-bit): 3.0.5.5992, revision: 58dd23d

Other test files:

-Gpx (=GP6) file: works: fireflight_the_hunger.gpx
But same file in Gp5 format fails (all tracks play piano): fireflight_the_hunger.gp5

A last one (comparison)
- Alessia Cara - Here (guitar pro).gpx works vs. Alessia Cara - Here (guitar pro).gp5 fails

Status active fixed
Type Performance Functional
Priority P0 - Critical

Oh, that is bad, it looks like my fix for this problem didn't solve it for Guitar Pro import.
Still all works correctly in current master. Knowing what was the cause of the issue, I suspect this should have happened with merging of this pull request: https://github.com/musescore/MuseScore/pull/4541
Anyway, if I am correct, any future versions should not have this problem anymore. Feel free to reopen this issue if it is not so.

Fix version
3.1.0