Green lines are not visible.

[tmvkrpxl0]

According to screenshots on website, there are 5 green lines on the piano sheet:

But they do not appear on my pc:

Could you tell me how to make them appear?
Environment info:
OS: Linux
DE: Plasma
Distro: KDE Neon 5.27

[Martchus]

The environment info lacks one crucial detail: Are you using by any chance Wayland? And which version of PianoBooster are you using exactly?

Note that Wayland is not supported by PianoBooster. When porting to Qt 6 the it has gotten better but there are still graphical glitches, at least using KWin. As a workaround you can enforce using XWayland which is supposedly also not supported but at least worked in my tests. To use it, add e.g. -platform xcb to the invocation arguments.

[tmvkrpxl0]

@Martchus Version is 1.0.0 and I don't use Wayland

[Martchus]

Then I don't know. It actually also misses the notes. What happens if you try to play? Maybe the MIDI file cannot be parsed correctly?

[tmvkrpxl0]

Then I don't know. It actually also misses the notes. What happens if you try to play? Maybe the MIDI file cannot be parsed correctly?

Ah, sorry for confusion. The notes indeed appear correctly. It's just 5 green horizontal lines that are not visible

[tmvkrpxl0]

(ignore the error on above, piano wasn't connected)

[tmvkrpxl0]

@Martchus I haven't heard from you for 2 days. Sorry for the ping, but I feel my message wasn't notified to you.

[Martchus]

I'm simply out of guesses. Well, you could try the latest version from Git (compiling it yourself). You could even test the version from my custom branch (https://github.com/Martchus/PianoBooster). You could also try compiling it against Qt 6. Not sure whether that will fix your issue, though.

If you have multiple GPUs on that system you could try the other one. If you have multiple OSs you could also try the other one. I don't know your GPU but maybe you can try another driver for it. Maybe just try a whole different machine. This problem is definitely nothing I've seen so far and I suppose anybody will be able to fix it without reproducing it.

By the way, even if I would be able to come up with a fix: This project is no longer regularly maintained. So when my fixes would land here is unclear anyways. (Hence I'm piling commits on the previously mentioned custom branch.)