Playback: short notes cut off long ones in same staff

• Mar 27, 2015 - 00:51

I don't know if this has been reported already; feel free to delete if it has.

When a staff bears multiple voices: if one voice has a long note, and another at any time hits a short note on the same pitch as the sounding long note, the long note is truncated when the short note ends. Example if needed.

This makes it almost impossible to enter, say, organ music (continuous notes, staff polyphony), or hymn-disposition choral music, without the need to silence notes with the Inspector. This cannot be right.


In reply to by schepers

Yes, exactly. Having read that, I can believe there are issues with polyphonic violin music etc., but with any keyboard instrument, there are no issues at all, and the current behavior is the worst choice, and a nuisance to catch and fix manually.

Actually, the interaction of multiple voices on a staff and the use of a single midi channel exactly models polyphonic (single-) keyboard music, which in turn provides a model for how it ought behave.

Another way of looking at this is that the short note now "kills" the long note: the long note should "kill" the short note.

Can I add my, erm, voice, to the crowd to fix this one please? The behaviour as it is is bizarre not only for keyboards but for singing voices too. The trivial example attached is taken from a piece I cannot create practice files from because it simply doesn't work.

Attachment Size
Musescore_Voices_Bug.mscz 2.25 KB

In reply to by Jojo-Schmitz

Thanks, but that won't work for me because I've written a program to take the MIDI output and create multiple MP3s from it, one for each voice, by changing the volumes and pans to emphasise each voice respectively. It detects two notes sounding at once in one MIDI channel and splits the channel into two, assigning them to one or the other. Stopping a note sounding would mean that it wouldn't appear in the separated voices. (I understand I'm hacking here but it's come as a great disappointment after developing this that it doesn't work for certain pieces.)

In reply to by Jojo-Schmitz

I'll raise it in the issue mentioned. I would guess that as this is a change to the algorithms at the heart of MuseScore that it would both take me an awful long time to work out how to make a fix and the chances that I'd break something else in the process would be extremely high.

In reply to by cadiz1

Yes, progress indeed.
Turning off play in the Inspector for those problematic 2 voice enharmonic notes is a decent workaround, considering the alternative in the following Example 1 below:


Example 1 plays correctly in MuseScore (.mscz file also attached) without any workaround. Also, it is a true representation of the notes actually executed on the guitar.

Example 2 is intuitively easier to sight read - with 2 groups of sixteenth notes per 2/4 measure, and is the way guitar music (especially classical) is usually notated, even though the guitarist would not actually span six frets to play those enharmonic bass notes (i.e. what the linked TAB would display). Yikes! :-o

Setting the play property of one of the notes to off is definitely the way to have good playback and good notation.

Attachment Size
Example.png 36.73 KB
Example.mscz 9.25 KB

If you read my original report of the issue, I said without the need to silence notes with the inspector to get it to play properly. I should not have to tell the music-playing program how to play music. It kills the wrong note; that's all there is to it.

In reply to by [DELETED] 1831606

Of course, I read your original report (this is an issue for me too, and I had testified with a file on the Issue Tracker there is three weeks)
I'm just saying that I did not understand, in this instant, the workaround (which is a workaround, it's true)
But listening to this file:
- Milonga without workaround.mscz
and by comparing with the same (with the workaround):
- Milonga Buscaglia workaround.mscz
you'll agree, I suppose, that there is at least a progress :)

In reply to by [DELETED] 1831606

I have scores of 75 measures and more ... And not everyone, far from it, has the systematic and repetitive nature of this file.

Let's say it's a matter of priority. My priority is being able to edit and print a score that I can play on my instrument. It might surprise you, but the Playback is entirely secondary to me.

It's more enjoyable, more comfortable, of course.

But if you had followed the "history" of the development of MuseScore since a year (for example!), you would be absolutely amazed, stunned, by the considerable work done to stabilize the 2.0 and improved it by various features.

I understand your point of view and query (and I share it), but let's say I know better now put the issues in perspective.

N.B. Furthermore, notice that after selecting the relevant notes, this can be done by unchecking "Play" one time.
It's exactly the same thing when you want to change the Head type of the notes when there is unisons. I would even say that you can do two things at once in several situations.

In reply to by cadiz1

Every note in your lower part is a dotted eighth aggrieved by a sixteenth; "select all notes in voice" would work fine if it was them you wanted to silence, but it's not; it's the sixteenths that strike them, and it's not so easy to select those many-at-once without some minor slip losing the selection. Your posted "example 1" is probably a better answer.

In reply to by [DELETED] 1831606

Not agree.
By default, you receive that after entering bass and voice1
No risk to loose the selection. If you make a mistake, you do not have to start all over again (as some of us have known there is some months yet before a magical fix!)
So, back to our example: select the involved notes (16th voice1) , and in the Inspector, untick "Play" + change the Note head, and you have the result like in the previous attached file.
Just a little less easy for the other bass (no dotted), because you must separate the notes in unison before to untick "Play" for the good one.

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