Custom palette

• Sep 21, 2023 - 16:33

Musescore 4 does not save own palettes. Yes, I know it has already been discussed, but the problem is still unsolved. And it's not a minor issue - it really slows down work and is very frustrating.

Only one file opened, one window.
Windows 11

Attachment Size
3 (reopened).png 131.68 KB
1 (open any file).png 129.82 KB
2 (customized then saved).png 150.48 KB

Comments

This really impairs the workflow compared with MuseScore 3 which works quite well in this respect.
To list the crucial items IMO:
Properties for palette items not accessible when items are the result of a palette search
https://github.com/musescore/MuseScore/issues/18632

Palette search can't find custom palette - https://github.com/musescore/MuseScore/issues/18640

Palette Cell attributes' changes do not persist across launches.
https://github.com/musescore/MuseScore/issues/12002
Notice that properties (including name) do not update until another element is added to the custom palette
But a search via Ctrl + F9 will not find the new name.

Positive news: Apply current palette element command not implemented
https://github.com/musescore/MuseScore/issues/13281 Fortunately there is a fix.

Paltte news for Windows: see https://musescore.org/en/node/342791

Do you still have an unanswered question? Please log in first to post your question.