The half sound is not correct

• Apr 14, 2020 - 16:08
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

1, load the attached musescore file: nelkuled.mscz
2, The score seemed to be in A minor, but there is a lot of b's (modifier sign) on B and E note. I thought it is better to put them and the whole music will be in G minor.
3. I did it, but the b is not disappeared in from of E notes in the score.
4. neither when I regenerated the modifiers.
5. and there are a lot of Fb notes, what is equal to E, so in the example should be a an E with the almost hash sign (I don't know its name in English.(resolver?))

Attachment Size
Nelkuled.mscz 30.53 KB

Comments

• Apr 14, 2020 - 16:32

That score stems from MuseScore 2.1.0, an antediluvian version meanwhile. Update to 2.3.2 and 3.4.2
The # sign is called sharp, the b sign flat, both are accidentals
Not sure what the issue with the score is though.

Reply

• Apr 14, 2020 - 16:43
Frequency Many ⇒ Once
Severity S5 - Suggestion ⇒ S4 - Minor
Status active ⇒ needs info
Type Development ⇒ Functional

So where is that score from? And what do you think to be bogus about it?
The half sound is not correct doesn't make sense to me, neither does what you wrote in your initial post.
Well possible that the piece might be better writte in another key signature, so what keeps you from doing it?

Reply

• Apr 14, 2020 - 18:53

I wrote, this score is written in A minor. There is No sharps or flats in the begining of the score. But there are two flats in it before the notes itself. That means the score is in G minor. (And the song ends with G note also) this suggest me, the song is in G minor. So I can put two flats in the first 5 lines, after a key. That means, the whole song is in G minor. I put 2 flats, as I thought. The app should recognize it, and should modify the score, and remove all “local” flats before each B and E note in the whole score. And it doesn’t work like this. There are unnecessary flats in the whole score. I tried also recreating flats, and sharps. It doesn’t works. What it is, if not a bug?

Reply

• Apr 14, 2020 - 19:41

As I look at the piece I see "e"s which are not altered and I see sharps. it seems to me that the piece has been deliberately written with no key sig,. which, at least among jazz players is a style.

It looks to be written in G minor.

No matter which key sig. you use there will be other accidentals. If you must have a key sig., I would do it in Gm and accept the "odd" accidentals.

Reply

• Apr 15, 2020 - 00:21

The piece is in G minor - two flats.
At some point, accidentals have been added manuallly, possibly because the Time Signature was not set.
Fundamentally - it is not an “Issue“ in that it has nothing to do with the programming.

Reply

• Apr 15, 2020 - 06:27

Hello, good morning,

Yes, you are right. Almost...
There are two sides of the thinking. The first is to see the issue(?) with musician eyes. With this view, there isn’t an issue. There are unnecessary flats in the note. Yes, no problem. I know it. The melody will not change if I remove the unnecessary flats. And the programmers doesn’t have to do anything. But I am a software engineer too. This is my job. And to see the notation with a sw engineer’s eyes. There IS an issue. There is a feature For example, in the tools menu (I don’t know exactly which menu, I use the application in hungarian language) that function is “Regenerate modification signs” or something like that, which should delete the unnecessary modification signs. Am I right?
And there appears “Fb” notes, which are Equal to “E” notes. (The same situation would be with “Cb” notes) so I think, if they aren’t bugs, it should be an improvement suggestions. And, if you think, there is nothing to do as a programmer, it should be marked somehow, maybe with another color, to see, that there are unnecessary modification signs.

Reply

• Apr 15, 2020 - 06:36

"Respell Pitches", But this is for a different purpose. To get rid of those courtesy accidentals (explicitly added to some notes, without a real need), transpose the score up/down by the same amount

Reply

• Apr 15, 2020 - 07:16

I have read the full thread and you haven't answered to the fundamental question : how did you add the two flats at the beginning of the score?
If properly by adding a key signature from the palette, then MuseScore will remove the flats in the score. If you tried any other trick that's not a proper key signature, then it doesn't work.
That's all there is to say really.

Reply

• Apr 15, 2020 - 07:53

I see (now) there's indeed something fishy going on, the accidentals later in the measures for notes of the same pitch just stay put without any need to.
They are not needed though (by standard musical convention an accidental is valid to the end of the measure for all notes on the same space or line), so are seen as courtesy accidentals. And as such they do stay put and that is by design I guess.

Reply

• Apr 15, 2020 - 08:25

@jojo-schmitz: if you write with @ sign like me now, I will see to whom you answered. Anyway, I don't know what courtesy accidentals. I looked it in google translate, and it says, that is a polite accidentals. It is un-understandable. Do you mean: careless?

Anyway, if I do diatonic transpose without "Keep degree alterations", then a get another tune/melody. Not the right solution.

Reply

• Apr 15, 2020 - 14:51

Courtesy accidentals are accidentals with are often used in the bar after an accidentaled note was altered.

For example, if the key signature contains a Bb and later in the piece the B note is to be a B natural, it is marked as such.

Then if a Bb is in the next bad, often an engraver will add a courtesy accidental to that note to show that it is reverted to a flat. Usually those note are surrounded by brackets B(b) to show that it is just a reminder.

I hope that is clear :)

Reply