Master effects interface disappears (when no plugins loaded) - Windows

• Aug 2, 2014 - 13:21
Type
Functional
Severity
S4 - Minor
Status
closed
Project

See Technology Preview thread http://musescore.org/en/node/28711 for details.

On Windows machines there is no master effects interface present.

Behaviour appears to vary according to the version of Windows installed.

On a WIndows 8 machine the interface reappears if you load any plugin ie the problem o0nly appears whne no plugins are loaded

On at least one Windows 7 machine the interface remains blank even if plugins are loaded.

This could be related to #22465: Blank artifacts when using qml objects

I have filed a separate issue, though, as the circumstances are slightly different.

Windows 8.1 Pro
MuseScore 2 commit 4e426c4808


Comments

I wonder if we plan on having any plugins load by default, in which case, it would be very unlikely nyone would run into this? Not that it shouldn't be fixed anyhow of course. Just curious.

loading a plugin by default (my vote would be notenames and/or colornotes, being the ones that do useful work) might be a good workaround for the nightlies and possible the next beta (provided the real issue hasn't been fixed by then).

The simple fix for this is to load a plugin by default until we can find out why the blank interface is there.

It certainly ought to be implemented before beta 2 comes out, as there are people complaining about not being able to control the amount of reverb in beta 1.

Fwiw, on Linux, I often see weird artifiacts - not exactly blank, but distorted like a scrambled cable TV channel. It fixes itself when I resize the window. Related?

I have just tried with a clean build of 43b80ad3e5 on Windows 8.1 and Qt5.4

I had to install a plugin to get the Mater effects interface to show.

So presumably there is more work to do??

Not sure why it works on Lasconic's system and not mine!

I found the cause of the problem!
The problem lies in the path to the "qml" folder containing the qml dlls.
By default, the qml engine searches for these dlls in the folder from which the executable is launched (in our case MuseScore/bin) or in a "qml" subfolder (in our case MuseScore/bin/qml). Therefore, it misses the correct folder which is actually MuseScore/qml.
On the other hand, when a plugin is loaded, the correct path is added to the searching list for the qml engine here:
https://github.com/musescore/MuseScore/blob/master/libmscore/mscore.cpp…
and that's why loading a plugin solves the bug.
Indeed, if the "qml" folder is copied inside the "bin" folder, this bug disappears.

Status (old) active fixed

Thanks a lot Werner, this will solve also the Windows problem some users were experiencing (and that I was able to reproduce somehow by running MuseScore under Application Verifier).

This bug can therefore be considered fixed.