When voice is overfilled with rests how can I easily remove them?
I regularly encounter measures where one voice has somehow become overfilled. And I've never discerned the ideal and quickest way to fix such measures. I can usually fix them with a bunch of fussy guesswork but this one stumped me so I thought it might make a good example.
In the attached score there Voice one is overfilled with rests.
MuseScore - Bar Voice 1 overfilled.mscz
(For the record, the provenance of this measure was from a MusicXML import, but regardless I think MuseScore might offer, or should offer, a simple remedy.
Any ideas or recommendations?
I would be really great if—in an overfilled voice—MuseScore would simply allow us to delete rests.
scorster
Comments
That score is corrupt. See How to fix a score that contains corruptions
If this is the result of a MusicXML import, that should get investigated, and the MusicXML file is needed
In reply to That score is corrupt by Jojo-Schmitz
Yes. Thanks Jojo.. I failed mention that I got a "corrupted" message after saving and reopening.
MuseScore let's me "Ignore" and continue. And as your reference indicates, once I've fixed or deleted the cited measure(s) MuseScore opens the score without reporting corruption.
This has happened after importing scores from Overture. When I encounter or can create a succinct example I'll submit the MusicXML and the corrupted MuseScore file.
scorster
In reply to Yes. Thanks Jojo.. I failed… by scorster
Question then is whether Overture's MusicXML export is broken, or MuseScore's MucXML import ;-)
Can't you import Overture directly?
In reply to Question then is whether… by Jojo-Schmitz
This phenomenon often occurs when the imported MusicXML score has values of duration that do not match the durations implied by the values of type for the individual notes. Such MusicXML files often come from programs that take the view that duration is intended to indicate the play duration of the note, not its musical duration. (Overture is an current example.)
While that is a very useful form of the protocol, I have concluded that it is not the best interpretation of the intent of the MusicXML specification and documentation.. In fact, after agonizing over all the contradictory complications in this area, I conclude that the best behavior when decoding a received MusicXML file is, if a note carries both the duration element (mandatory) and the type element (optional), to ignore the element.
As a counterpart to this, I will probably recommend to the developer of Overture that its behavior in this regard be changed. I do not expect that this recommendation will be well-received.
I am completing an extensive technical report on this issue, and will make it available here as soon as it is ready.
Best regards,
Doug
In reply to This phenomenon often occurs… by Doug Kerr
The attached technical report discusses (at length) the matter that I discuss in the note above.
Best regards,
Doug
For the reocrd, you can delete rests or notes, Ctrl+Delete removes any selected beats entirely.