Notes do'nt give sound

• Jan 3, 2016 - 22:31

In a piece of music when i playback this music some notes do'nt give sound.
What can be the problem. In this case it's about high D and high E.


Comments

In reply to by Jojo-Schmitz

The notes which don't play are just simply too high for an Alto Sax to physically play, even with the extension I added to the soundfont instrument to take it up to Eb6.

Normally it is not expected to write parts as high as this for saxes - the top octave of the range is extremely difficult to produce consistently, and is avoided by all composers and arrangers who know what they are doing.

Obviously whoever wrote this did not!

In reply to by ChurchOrganist

If I make a new melody with this same high notes and the same instrument this notes give sound and they give for the high E note the value Pitch:E5.
In the sheet I posted for this same note the program gives the value Pitch:E6
Maybe there is something wrong with the notation or there is a bug in the software.

In reply to by dirkdesart

The reason it works with a score created from scratch is that you are entering the *written* pitch, and that E is within the *written* range for alto saxophone. But alto saxophones are transposing instruments, and it appears the transposition information for this score is messed up. If you view it in Staff Properties, you will see it is set to no transposition, but when you hit the concert pitch button, you'll see bad things hapen. Probably the MusicXML it was imported from was not created correctly and that is why the transposition information is messed up, but we'd need to see the original MusicXML file to know for sure.

The reason the notes are not marked as out of range is that someone modified the range in Staff Properties to tell MuseScore an alto saxophone can play all the way to G9 :-)

In reply to by dirkdesart

Well, again, it seems the error is in the MusicXML file you imported this from. It would be very helpful if you could post that. That is, we are guessing that there is a bug in the program that produced that MusicXML file, and that is why you are having to do illogical things now to work around that bug in that other program.

At least, we seem to be assuming you started by importing a MusicXML file from another program. I'm not sure you ever said you did. If you did start by importing a MusicXML file from another program, again, we would like to see that file. But if you created this score from scratch from within MuseScore, we would also like to know more about how you did that, since this score has some things going on with the transposition that just should not ever happen, so we want to know how it got this way.

In reply to by Isaac Weiss

Eureka, I found the cause of this problem. First my melody was written in the program "Encore5".
The notes where configured 1 octave to high but I never noticed that and Encore5 had no problem playing this notes. I converted the file via xml to Musescore. For Musescore this notes where to high for the sax. So the cause of the problem is clear.
It is still strange for me that Musescore don't indicate that the notes are 1 octave higher.

In reply to by dirkdesart

I'm not a MusicXML expert, but I think Encore has exported this file incorrectly. It includes incorrect / insufficient informatyion about the transposition. There should be two transposition tags: one for "diatonic" set to -5, and one for "chromatic" set to -9. Instead, there is only the "chromatic", and it is set to 3. I'm pretty sure that's just wrong, and that this is the cause of the octave error.

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