Deleting first couple of (empty) bars, it also delete Tempo and Clefs
If I delete those empty bars showed on the pic, the flats disappears and both staves goes to Violin clef
| Attachment | Size |
|---|---|
| Screen Shot 2019-01-09 at 16.57.47.png | 17.82 KB |
Do you still have an unanswered question? Please log in first to post your question.
Comments
Feel free to add this into the issue tracker
In reply to Feel free to add this into… by Jojo-Schmitz
I can't reproduce this with an existing score in the stable release or starting from scratch using OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.1.4922, revision: 598057d (which is about 36 hours old).
In reply to I can't reproduce this with… by mike320
Me neither... so we need a score that shows that behavoir
In reply to Me neither... so we need a… by Jojo-Schmitz
There you go:
1- select both empty bars both staves
2- contextual menu --> Delete Selected Measures
In reply to There you go: 1- select… by danworks
Only thing I can confirm with that score is that the bottom staff changes to treble clef, key sig (the flats) stay put (but adjust to the clef of course). But that does happen with 3.0 and the latest development builds, so back to my initial reply: please enter this into the issue tracker
That score had been last saved with 96c1f7b, which is the RC, not the final release, did you upgrade to that?
In reply to Only thing I can confirm… by Jojo-Schmitz
The score was imported and the instrument in musicxml defined the staves as both being treble clef. When you delete the first measure that contains a clef change, the clef is deleted with it.
The tempo is text attached to the first note/rest of the score and is deleted with the measures also. This is something that might need to be reconsidered when deleting the first measure of a score.
In reply to The score was imported and… by mike320
Strange to learn that the xml carries treble clef also on left hand considering that the imported xml was playing correctly the piano sound.
In reply to Strange to learn that the… by danworks
The problem is most likely with the export from the other program. If you attach the xml, a programmer can look to make sure the problem isn't on the MuseScore end.
In reply to Strange to learn that the… by danworks
Please attach the xml to #281488: Deleting first couple of (empty) bars, it delete Tempo and Bass Clefs
In reply to Only thing I can confirm… by Jojo-Schmitz
Sorry, my mistake … not key signature but tempo disappear.
The MS version I'm using is the one I've just downloaded after MS warning message of a new version.
In reply to Sorry, my mistake … not key… by danworks
The final release didn't do that, just from beta to beta to RC, so you need to install the final version yourself and better do it now, else it would not notify you of 3.0.1 which is due shortly.
The tempo disappears by design, although we might be able to special case tempo on 1st measure.
In reply to The final release didn't do… by Jojo-Schmitz
I've just downloaded the new version directly from the website (v. 3.0.0.20137) and it's newer compared to the one (v. 3.0.0.20100) MS asked me to download few hours ago when I've launched it.
Strange isn't it?
In reply to I've just downloaded the new… by danworks
The beta or rc versions only prompt you to update to a newer beta or rc, not to the released version.
Personnaly I find that a pretty bad decision, but so is it.
In reply to I've just downloaded the new… by danworks
Not as strange as it may sound at first, the betas and RC were for testing, so only upgraded from one to the other, the release version is on a different stream, so not part of that beta update schema.
But yes, it caught me be surprise too...
In reply to Not as strange as is may… by Jojo-Schmitz
MuseScore encourages users to download and try the beta, with an update experience.
The fact these users are prompted to get a new version of the beta everytime there is one, but that after that when it is released the function"check update" says no update available while there is clearly one (the release) can only be "strange".
In reply to MuseScore encourages users… by frfancha
Well, it is bizarre from the user point of view cos if don't see "BETA" on the splashscreen, I think I'm running a release, therefore when I get a message about a new release I think it's a new … "release".
Not a big deal though :-)