Front half of measure is uneditable
I have a measure in my attached file where the front half is totally blank. No matter how many notes you add to the measure, it keeps that much blank space. Deleting the notes also maintains the spacing. I don't believe this is an issue of breaks, spacers, or stretches. Any help is appreciated!
| Attachment | Size |
|---|---|
| Bon_Bon_Bug_8_22_22.mscz | 285.46 KB |
| wideMeasure.JPG | 37.76 KB |
Comments
Select the 1st not in the top staff, the B4, then in Inspector reset Segment > Leading space (to 0)
Unrelated: Why are you using staff text for chord symbols rather than... chord symbols?
In reply to Select the 1st not in the… by Jojo-Schmitz
That solved it, thanks!
The chords were for quick notation for myself while I am transcribing this piece from a recording.
Most likely that extra space got there from trying to drag a note. Generally speaking, don't do that, unless you are going for highly unusual special effects.
In reply to Most likely that extra space… by Marc Sabatella
Yes I agree that's probably how it happened. Selecting and dragging the 1st note allows me to replicate the issue and fix it quicker than through inspector>offset.
In reply to Yes I agree that's probably… by Bon_Bon_
Well, I wouldn't try to fix it that way - almost no chance you'll actually get it exactly back to 0. Way way way faster to just click the reset button next to the leading space field than to try to carefully eyeball the exact distance.
What I'm saying is, don't drag notes. Ever. Not for any reason at all. Anything you think you might want to accomplish through dragging a note is far better accomplished a different way.
If the drag happened accidentally through attempting to drag the canvas, then my next advice would be, don't do that, either :-). The much better way to scroll your score is using your normal scroll wheel / touchpad scroll gestures (eg, two-finger swipe).
Dragging is a recipe for trouble and should be avoided for almost anything in MuseScore.
In reply to Well, I wouldn't try to fix… by Marc Sabatella
Dragging is a recipe for trouble and should be avoided for almost anything in MuseScore. ... so ... why is there, then? But as a question: If I open a score which is higher than workpane screen (> about 13 staves, e.g. a wind band score) in continuous view, PgDn/Up scrolls left/right - but how, other than with dragging, can I see lower staves of the score?
H.M.
In reply to Dragging is a recipe for… by hmmueller
Good questions!
First, why is dragging there? It's there because it's easily discoverable, and some people don't mind living dangerously. msueScore 4 is disabling some of the worst of the side effects that can happen from dragging, but even so, it's never going to be as precise or efficient as other methods.
Second, how to scroll - as I said, with the standard scroll wheel on your mouse, or equivalent touchpad gesture (eg, two-finger swipe - with or without Shift to toggle between horizontal/vertical on devices that don't support free swipe).
In reply to Good questions! First, why… by Marc Sabatella
What the ... I never knew about "two-finger swipe" up to now! ... "easily discoverable" dragging vs. ... well ... unfathomed new horizons. Well. Thanks. Works.