Measures are hidden in parts although not empty
Reported version
3.0
Type
Graphical (UI)
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
Ich habe eine Projekt aus Musescore 2 importiert und habe nun das Problem, dass in den Auszügen an manchen Stellen die Zeilen ausgeblendet werden, obwohl es sich nicht um Leertakte handelt. Dafür habe ich keine Erklärung. In der alten Version werden die Auszüge korrekt angezeigt.
Die Funktion "gewählten Takt löschen" ist nicht mehr zu finden.
Vielen Dank für eine Rückmeldung
Comments
Translation (DeepL): "I imported a project from Musescore 2 and now have the problem that the lines in the parts are hidden in some places, although they are not empty bars. I have no explanation for this. In the old version the extracts are displayed correctly.
The function "delete selected bar" is no longer available.
Thank you very much for your feedback."
Please attache the score to reproduce it.
Concerning "delete selected bar" I suppose you're talking about about the context menu as reported here: #114366: Add "Delete Selected Measures" command to context menu
Kutrowatz Concerto for 2 Pianos 1. Satz Musescore 3.mscz
Thank you for your reply. I have to get ready this sheet Music as soon as possible and want to use Muscore 3.
is this #278057: "Hide empty staves" hides non-empty staves when first measure is empty?
Looks like the only part with this is issue is Klavierauszug, around reheasal mark A. Hidden staves are enabled, Klavier 1 plays on the second measure and not the first, and so does not show up. Good news, looks like it's been fixed - next beta version or nightly should work.
To get a faster overview: Could you give some examples, where it happens?
For example in Part “Partitur” from Bar 79 Cadenza Piano 2 ist missing from bar 79 to 88 an then piano 1 is missing from 89 to 74, the n Piano two from 85 to 119, and the Piano 1 from 120 to 124.
The same bars are missing in Part “Klaviere”
I didn’t check the whole score if there are any other bars missing.
Thank you
It's definitely #278057: "Hide empty staves" hides non-empty staves when first measure is empty. The next Beta update should have the fix, or the nightlies. Meanwhile, you can go to Style and uncheck the 'hide empty staves within systems' option.
Yep, seems so. It doesn't happen with the last nightly (3e4ea9b), where this issue is fixed. So you could also download the actual nightly build.
Thank you, but can you explain, how I can find the nightly bulid?
see: https://musescore.org/de/download#Entwicklerversionen
Thank you, i have installed the nightly build. The missing Bars arr correct now. But Percussion 2 ist written on the same place as piano 1 in Bar 95 and bar 131.
I don't get it. In the sore? In some of the parts? Maybe attache a screenshot.
(By the way, I notice inside the parts dialogue for some parts ("Percussion", "Partitur") the instruments don't appear in "instruments in part". Not sure, if it's another issue).
as you can see in the screenshot. This is how i get my Part "Partitur" on some places.
the other piont with showing the instruments - I dont know i made the parts in MuseScore 2 there the Instruments are properly shown.
Not for me (OS: Opensuse, 3e4ea9b). Maybe open a new issue entry for further investigation.
strange waht means (OS: Opensuse, 3e4ea9b). Do have to change something in the document?
No, I didn't change anything. I just opened your score with my operating system (=OS) OpenSuse Linux and with the mentioned revision of the development version (you'll find it inside the menu help->about...). And there I don't see this behavior. Or it could, I'm missing something myself and someone other is able to reproduce it.
It's right, that's this issue entry (your initial question) is marked as "duplicate". But this has the consequence, that this issue isn't shown as open issue.
So again, it would be useful to start a new entry inside the issue tracker for this latter request, so that's visible for other too. Describe it and attache your screenshot again. And don't forget to mention your Operating system (Windows in your case) and the revision of the development version (see above (it could be, that's a bug in your nightly/development version, but already fixed in another)).
And attache the score again in this issue entry.