Chords can no longer be entered on beats without a note in v.3.5

• Jul 30, 2020 - 09:59

Previously chords could be entered on every beat in a measure. In 3.5 this is no longer possible - I assume because of the changes re. playback of chords?.


For the record, there have been no changes here. Space or semicolon continue to stop on every beat, Ctrl+number stops at the corresponding duration. If you have a score where this seems not to be the case, please attach it so we can investigate.

In reply to by Marc Sabatella

I studied the case a little closer, and here it is:
It was a score imported from an xml file, in which there were apparently issues (but not related to rhythm). If I continue editing it before having saved it as a musescore file, space will not move to the next beat on longer notes, only to the next note.
If I save the file as mscz and then reopen it, it behaves as expected, but I have to close and reopen it again.
Here's my system: OS: Arch Linux, Arch.: x86_64, MuseScore version (64-bit): 3.5.0, revision: fb3c202
I attach the file.

Attachment Size 32.3 KB

In reply to by eyolf

The problem seems to be with the time signature. I'm not enough of a MusicXML export to say why this is happening, but notice no time signature appears in the score. The file itself appears to declare it as 2/2, but MuseScore seems to be interpreting it as 1/1. You can see this by looking at the status bar while you select various notes. You'll see it doesn't report four beats per measure, it reports just one. A measure with four quarter notes reports as being beats 1, 1.25, 1.5, and 1.75.

So, Space when entering chord symbols is doing what it supposed to do - skipping to the next beat. It's just that there is only one beat per measure, so that ends up going to the next measure.

If I delete the symbol="common" from the file, it works. Somehow that seems incompatible with a time signature of 2/2 as far as MuseScore is concerned.

Fix is to change the time signature to cut time. Or 4/4, but you'll need to change it to cut time (or something else) first, because changing it to 4/4 won't actually cause MuseScore to recognize the change and update the beats.

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