Adjusting notes to Chord symbols

• Jan 26, 2016 - 11:14

Hi

I am new in Musescore.
On my first two scores I added Chord Symbols to the notes, and whenever a Chord symbol was long (eg. C#7+5), the program would adjust the notespacing accordingly, without me having to do anything.
Now I suddenly find it doesn't, meaning that there is not enough space to put in the chord symbols, if they are long.
Anyone got an idea of how to solve this?

Jens


Comments

Can you share the score that is showing this?
Which Version of MuseScore, what OS?
Are you sure you really entered them a chord symbols, via Ctrl+K, not as staff text, via Ctrt+T

In reply to by jensaxel

Hi Jens,
I downloaded your score and placed a line break at bar 5. You had 13 bars on the first line. I added some nonsense notes and chords to bar 1, and it expanded enough for someone to read and play. Again, what I added is garbage. I just wanted to see if it worked. The program seems to be working fine.

Perhaps someone else can comment.

- Lee

Attachment Size
The_message LEE.mscz 9.61 KB

In reply to by jensaxel

I don't see a Problem with that score, the chord symbols render quite nicely.
Are you talking about that 1st chord symbols, that seems to span several notes?
That is not a problem at all, as there is no other chord symbols nearby needing space, and if you'd add one, the space would get created automagically

In reply to by Lee Batchelor

My problem was, that I needed another chord in the second bar. It didn't expand automatically.
However, I went in an expanded the first bar manually. It's just that before (and I think that should be the way) - this manual adjustment shouldn't be necessary..

Thanks anyway

By the way, the bars and note spaces stretch fine when, I add lyrics

In reply to by Jojo-Schmitz

Yes, that would be a nice new feature, but it's not a bug. As I explaiedn, the current algorithm is only csapable of working *within* a measure, and there are technical reasons why it is currently difficult (next to impossible) to work across measures. By "currently" I mean, until the layout algorithm is redesigned to make it feasible for the layout of one measure to depend on the layout of other measures. For all I know Werner's current work might enable this, but right now, there just isn't really a way to do.

So we have a choice: either always pad out a measure for a chord symbol that would extend over the barline, or never do. The compromise we currently have in place is to add a certain amount of padding before the barline, and we have a parameter I mentioned in my previous response to control how much. So you can set it very low and get the chord to always spill, or set it very high and get it to never spill, or compromise and set it somewhere between and hope for the best as we did with the default.

Meaning, again, the algorithm is doing exactly what it is designed to do; there is no bug. However, as a new feature to implemented some day in the future if/when it becomes more feasible, sure, collision avoidance that works across measures would be nice.

See #25278: Chord symbols won't overlap barline for more information on this.

By default, the automatic spacing only works within a single measure. A chord symbol so long that it spills into the next measure won't affect the spacing. So if you have only a single chord symbol per measure and your measures are unusually narrow as is the case here, then indeed long chord symbols won't add space.

If you don't wish to add line breaks (which would make your measures wider since there are fewer per line), you can still force MuseScore to add space by increasing the "Maximum barline distance" parameter in Style / General / Chord Symbols. This controls how much MuseScore extra space MuseScore will allocate *within* a measure to accomodate a long chord symbol. The bigger this parameter, the more space MuseScore will allow. We don't make it very big by default because if there is no chord symbol in the next measure there would be no need to add space, and the situation where there is a chord symbol at the end of one bar *instead* of at the beginning of the next comes out looking very bad in that case.

Do you still have an unanswered question? Please log in first to post your question.