Not able to enter dual notes
When trying to enter dual notes in a score, sometimes the notes will delete the previous note. e.g., if placing a G above a D, or vice -versa, the first note will vanish!
Do you still have an unanswered question? Please log in first to post your question.
Comments
Pay attention to the option selected in the drop-down list below N
In reply to Pay attention to the option… by Shoichi
Thanks for your reply but I may have misled you. I intended to say notes as a chord. I looked at the drop down, but don't understand the meanings in respect to my question.
In reply to Thanks for your reply but I… by George Drew
If you were in "repitch" mode, then this would be normal - I think that was the point.
Anyhow, without knowing exactly how you tried entering the chord - by clicking multiple times, using keyboard shortcuts Shift+letter, using a MIDI keyboard, etc - it's hard to say what might have happened. Also be aware tablature and percussion staves work differently from standard.
In reply to If you were in "repitch"… by Marc Sabatella
"if placing a G above a D, or vice -versa, the first note will vanish!"
This is what happens if you enter e.g. a quarter note for the D, and then change the value, say a half note for the G.
Is it that's what you do and want to achieve?
If so, you have to enter the notes in two different voices: https://musescore.org/en/handbook/voices
In reply to "if placing a G above a D,… by cadiz1
Thank you for your helpful responses - I am a new music software user, so am still getting used to the nuances.
I am not using voices or changing values. I have attached a file of a small example - this one is Musescore 2 as I have temporarily reverted. If you take the G as being the first note of the chord, if I then enter a B above it, the G vanishes. A workaround that sometimes
suceeds is if I go back out of note insert, click on the stave section and then re-enter. But messy. Sometimes in 3.0 (current version) I cannot click on (select) the measure without difficulty - not sure what is going on here, but no problems in 2.0. Anyway, not unduly stressed as v2.0 is working OK and sounds good.
Cheers.
In reply to Thank you for your helpful… by George Drew
N 6 . G Shift+B
In reply to N 6 . G Shift+B by Jojo-Schmitz
You say nothing about this: which device do you use for entering the notes?
See: https://musescore.org/en/handbook/note-input#input-devices
In reply to N 6 . G Shift+B by Jojo-Schmitz
Hi Georges,
When your cursor is on an existing note (let's say G) and you need to add a B, just enter the B by shift+b.
Typing the letter B only will replace the G by B, using shift+b will add the B note to the G note.
By the way, the added B will be above the G note, if you wanted the B below the G, just use ctrl-downarrow immediately after entering the B, the B will be set one octave lower.
Fred
In reply to Thank you for your helpful… by George Drew
My guess is that you simply clicked the wrong spot accidentally, or inadvertently pressed Shift while clicking, or as mentioned changed the duration meanwhie. Because absolutely nothing has changed in this respect between MuseScore 2 & 3 - if you click to enter a G, then click above that to enter a B without changing duration, you get a B added to the chord, exactly the same as in Musescore 2 (or 1, for that matter).
In reply to Thank you for your helpful… by George Drew
Clicking is different in version 3 than in version 2 and just takes a little getting used to. It's difficult to to describe how it's different, but some things just don't seem to work the same. I miss my target still more than I did in version 2 and I've been using it since last September.
In reply to Clicking is different in… by mike320
While I think I understand what you are saying when it comes to selection and drag & drag and the exact point at which you need to position your mouse, my point is that nothing about the process of building a chord in note input has changed. It's still the case that if you click to enter one note, then click to enter another note at the same location and with the same duration, you get a chord. My guess is that the OP was entering a note of a different duration - perhaps because he was adding to the chord after having already entered other notes and forgot to change the duration back.
In reply to While I think I understand… by Marc Sabatella
It has to do with when I click and don't always get the results I would get in version 2. It's like the pointer points at a different spot. It's most noticeable when I try to select a measure. In version 2 I almost never had to resort to click the first note then shift + click the last note now I have to do it a lot. I do notice other clicks don't work the same as they did in version 2. It's hard to describe the difference, it just is. I thought it might be the "Proximity for selecting elements" setting in preferences, but they're the same for me.
In reply to While I think I understand… by Marc Sabatella
Thanks Marc, I appreciate your assistance, and everyone else's, however as my desktop PC (WIN10) has now crashed, I am beginning to suspect an operating system problem as I am seeing numerous complaints re WIN10 on the net. I am replying to this on my laptop. I will keep you informed when I get back to normal?
Regards, George
In reply to Thanks Marc, I appreciate… by George Drew
Hi all, I was right about the WIN10 issue. Following a recent update, my SSD had become corrupted. Now, two weeks later with a re-built PC and new clean version of WIN10 v19.3, Musescore 3 is working fine. I just finished an intermezzo (50+ bars long, and it sounds great). Thanks to everyone, and for those who are experiencing problems with Musescore, don't rule out your OS system, or hardware. I now have a very quick 3.8Ghz AMD processor on a Gigabyte MB (GA-A320M-H) 16Gb of RAM, and a 500Gb SSD hard drive. Great sound from the on-board Realtek Audio thru' my Senheiser headphones. Regards to the great team that put this program together - it has saved me heaps of time (and money), although I had to fix my PC anyway. Cheers.
In reply to Thanks Marc, I appreciate… by George Drew
Hi all, I was right about the WIN10 issue. Following a recent update, my SSD had become corrupted. Now, two weeks later with a re-built PC and new clean version of WIN10 v19.3, Musescore 3 is working fine. I just finished an intermezzo (50+ bars long, and it sounds great). Thanks to everyone, and for those who are experiencing problems with Musescore, don't rule out your OS system, or hardware. I now have a very quick 3.8Ghz AMD processor on a Gigabyte MB (GA-A320M-H) 16Gb of RAM, and a 500Gb SSD hard drive. Great sound from the on-board Realtek Audio thru' my Senheiser headphones. Regards to the great team that put this program together - it has saved me heaps of time (and money), although I had to fix my PC anyway. Cheers.