Stems and Flags visibility always synced between score and parts

• Sep 15, 2024 - 11:24

Hello all, this thing pushed me to write my first forum post. I hope I'm on the right place, I think it's a bug... I tried to reproduce the problem and simplify it. The problem is killing me...

My situation:
I have a score and 4 parts. I want to write cue notes in one of the instruments (so the player knows what another instrument is currently playing). I want the cue notes to be INVISIBLE in the score (where it is useless, because the score contains all the instruments below it) and VISIBLE in the part. I write the cue notes in voice 2 so that the rests (or notes) that are the true part of the current part are visible at the same time.

My procedure in MuseScore:
In the SCORE, I write the rests into voice 1 (because the player isn't playing anything at the moment). Into voice 2, I write the cue notes (copy from a different part). I set everything in voice 2 as invisible (and also as Cue size and grey color).
I go from the score to the PART and select everything in voice 2. I uncheck "Synchronize mith main score: Style/appearance and Position (because I also want to change the stems direction so the cue notes are not overlapping the regular notes)" and set everything as visible. When I go back to the score, the lines and flags are back-synced to the score.

So it is not possible to have different visibility in score and part for stems and flags.

The file is brand new (no conversion), OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: 0b3dd00

Am I doing something wrong? Is this a bug? I attach the image of my score and the part.

Thanks a lot for the answer!

Attachment Size
Clipboard01.png 94.58 KB
Clipboard02.png 62.13 KB

Comments

• Feb 7, 2025 - 18:40

Hey, was this issue ever solved? I have been having the same exact issue. I have been looking all over for just a streamlined answer on adding cues and not having these issues and haven't found one. This seems like a really important thing!

Reply

• Feb 27, 2025 - 01:44

I find that clicking on the "visible" box in the properties tab to check or uncheck it often does unexpected things which pressing v on the keyboard does not, even though pressing v causes the "visible" box to check or uncheck.
So if clicking on the "visible" box doesn't do what you want, or does do what you don't want, try pressing v instead.
I would have expected clicking on the "visible" box and pressing v to have exactly the same effect but I have discovered that they do not. Perhaps the MuseScore people have made it different on purpose, which could be why hovering over the "visible" box doesn't open a little window with further explanation and the keyboard shortcut in the same way that, for example, hovering over the tenuto button opens a little window saying "Tenuto (Shift+N)"

Reply

• Apr 12, 2025 - 01:40

I have just repeated what you did in your video but with only one difference. Where you clicked on the "visible" tick box in the properties tab I pressed v on my keyboard instead. It worked perfectly. Then I noticed that I had missed out making the notes heads small so I went back using ctrl z and re-did it. This time I got the same result as your video.
I closed that file without saving and started all over again. Now I get the same result as your video.
I closed and restarted MuseScore and started again again. Same result as your video.
I am writing this to let Jojo-Schmitz know I can reproduce it since they couldn't. I hope it helps a bit.
My first attempt (the one that worked) was my first use of MuseScore since upgrading to 4.5.1.250800846
Selecting just the beams in the score and pressing v put it right, but I agree it shouldn't be necessary.

Reply

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