Hello to you all dear forum.
In this picture - bar# 214, I am introducing “staff below” on the next system (
#215 and on - to bring in dynamic changes) but I’m getting this preliminary staff in
#214 and I’d have liked to remove it
( because it’s just taking up space here ).
I have tried “manual staff visibility” as well as (in engrave mode) “reset layout” - “move to next system” - but I am still getting this preliminary staff in the bar before. So what I want is not just to hide the preliminary but to remove it completely without removing the staff below in the next system.
Thanking you in advance for your guidance - cheers - Rami.
I have just tested this out on a new piano project as well as one with just a single vocalist and I don’t have this problem.
You could try adding the extra staff at the beginning of the piece and hide it up until the start of the relevant system. I know you mentioned you have tried Manual Staff Visibility but did you mean this?
Could you attach your project?
If you enable View Signposts, specifically Staff Count Changes, you should see a purple signpost above where this extra staff fragment begins. Select the signpost and press Alt + Right Arrow. The signpost and the start of the extra staff should move to the right. Fiddle with that until you are happy.
2 Likes
Thanks very much dear Daniel for your reply .
Perhaps the issue here is a bit different then adding a vocalist (which is like a new instrument) - because this is a grand staff. Sometimes a need arise to add an extra stave for the “classic” grand staff. I have checked my project and have found that there are many system breaks that I hide ( so I didn’t see them prior to this writing ) maybe this was the reason but I am not sure but when I tried to remove them chaos occurred .
As for uploading my project - I am using Dorico V now, I tried to use the “silence” template but this doesn’t reduce the file size. Is there any other way?
Thanks again - Rami.
Super amazing - many thanks 
The grand staff should have no difference - I tested it too.
It seems like your problem is solved with the instructions @StevenJones01 provided?
