playback fix

• Jul 31, 2015 - 03:06

When you add a sharp to a "G", then put another "G" in the same measure, both "G"s should be sharped. In the playback, only one is. :(


Comments

Can you post an example of a score like that and detail precisely what you're doing that's not working? I can tell you that normally, "When you add a sharp to a "G", then put another "G" in the same measure, both "G"s are sharped in the playback. :-)"

In reply to by Blue Bear

To post a score here, click the "File attachments" link right below where you type.

In this case, instead of seeing the score, it would be better if you posted the precise step by step instructions to reproduce whatever problem you are seeing. You might want to read the Handbook section on note input first, and/or watch the tutorial videos, to make you aren't simply doing something incorrectly.

I can *guess* that maybe you are first entering both G's, *then* changing one to G# and expecting the other to change as well. It doesn't work that way. MuseScore doesn't changes note that you don't tell it to change. Changing ond fe G to G# doesn't change others, any more than changing one quarter note to an eighth note changes others. That's why it adds a natural sign - to make sure the note doesn't change. If you want to change multiple notes, simply select multiple notes

If on the other hand you enter the accidentals s you go - enter the first G, sharp it, then enter another G - MuseScore does rememebr the sharp and automatically applies it to the next, meaning it appears with no natural and plays as G#.

Having looked at your score it is clear that you don't know that notes in different octaves will require an accidental even if they are in the same bar.

So if you make G on the 2nd line in treble clef natural in a piece with G# in the key signature, if you then enter the G an octave higher ie in the space above the stave then it will still require a natural sign to prevent it being played sharp.

http://www.dolmetsch.com/musictheory9.htm

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