Continuous view issue
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
I wrote a simple melody score starting from the template MS blank page, and then added chords symbol. I've realised that MS automatically added system breaks which is good. Then I've switched to "Continuous view" and the score was all 'compressed', notes too close to each other and not enough space for the chords, it looked quite bad. Am I doing something wrong?
best
Comments
Continuous view does not use the auto avoidance algorithm so it's not uncommon in this view to have some rather ugly crashes that you don't see in page view. From what I've seen, this is the only issue with continuous view so the measures widen enough to make room for notes. I don't use chords so I don't know if room is made for them or not. I'm guessing, like with lyrics, the chords shouldn't overlap. Perhaps you can attach a score and explain what's wrong with it.
I have the same issue. If there is a chord or more than 1 lyrics line it is easily overlapping with other content.
Do you know if there is a way to manually fix this somehow?
Thank you.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.4.5763, revision: cda4080
Checked with nightly as well. No difference.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.5909, revision: 0fac294
In reply to I have the same issue. If… by Ferenc Farkas
The fix for this is to use a spacer from the Breaks and Spacers palette to make more room between staves. You can remove them when your are ready to make final adjustments to your score in page view, for sharing online or printing. If this doesn't help, then you need to use page view to enter the score.
As I stated earlier, there is little auto avoidance happening in continuous view. You either live with the crashes in that view, or enter the score in page view.
In version 2 I always used continuous view to avoid wild jumps of my display that happen in page view. In version 3 I adjust the Scaling in Formating->Page settings... so the number of measures I want on a page usually show up on the page. I mostly enter music a page at a time, and then press "Enter" to force a page break for the next page. In version 2 , I would adjust the scaling after the entire song was entered.
I find this works well for me.
Thanks Mike! The spacers helped me to fix it.
I would be willing to bet the original report was about 2.3.2 not 3.0, and it's mostly talking about horizontal spacing, not vertical. And if I understand correclty, what is being described is perfectly normal - measure widths in continuous view are different from measure widths in page view, because they aren't being artificially stretch to fit the page width. That's a good thing, otherwise you wouldn't be able to see as much of your score at once. There should be no actual collisions, though - just tighter spacing - true in both 2.3.2 and 3.0. If the OP wants to attach a score that illustrates some sort of actual problem with this, we can investigate, but as it is, I am pretty sure it's all
by design".
What we now are talking about here is vertical spacing, which indeed works differently in continuous view. For the record, autoplace still does "most" of what it would in page view, but the main thing it does not do is add space between the staves. this was a deliberate decision but it's a legitimate question as to whether it should be revisisted. See #282579: Continuous view needs space for lyrics