play transposition
Hi Mark,
Sorry, I should have attched the file the first time. I was changing the bass clarinet part. (up/down play transposition)
GIT commit: 3c7a69d
Attachment | Size |
---|---|
Ave_Verum_Corpus.mscz | 51.9 KB |
Hi Mark,
Sorry, I should have attched the file the first time. I was changing the bass clarinet part. (up/down play transposition)
GIT commit: 3c7a69d
Attachment | Size |
---|---|
Ave_Verum_Corpus.mscz | 51.9 KB |
Comments
Can you please describe the actual problem - give precise steps to reproduce whatever you think is a bug. Right now, looking at the score, it looks just fine. What do I need to do in order to see a problem? You previously mentioned something about changing instrument - a perfectly valid thing to do - but also mentioned something about messing with play transposition, which is *not* something you should ordinaril do. So please explain what you are actually trying to accomplish with the steps you list.
Please post additional information here rather than opening a new bug report. I'm closing the other one so the discussion can stay here.
Hi Marc, I was taking music from the web (Musescore sheet music) and taking the third part (perhaps saxophone) and changing instrument to Bass Clarinet. This puts the notes well above the staff. If I change "play transposition" by octave the notes on the staff move an octave and are written in a range for bass clarinet. However if I select "up" an octave, it assigns a new key signature - which seems strange.
I could simply change instrument to Bass clarinet, then select all notes (which is a bit awkward as there are multiple pages), then use Cntl + down arrow which results in moving the notes into the correct range. Ah, I just realized that the "major second" may be a factor. However -
To duplicate this, open the file I sent, select the first bar of bass clarinet, then change the play transposition to "up", rather than down, if you click "apply" the notes on the staff move down 2 octaves rather than up one. (this is with play transposition set to to "perfect unison"). Strange.
I hope this is useful!
The third part is currently Bb Cornet. If I change it to bass clarinet, then of course the notes go up an octave from where they are now - that is the correct transposition, because bass clarinet sounds an octave lower than cornet. A bass clarinet would have to play those pitches in order to yield the same sound. If you want the bass clarinet to play lwoer notes, don't lie to MuseScore about the correct transposition for the instrument - simply transpose the part down an octave (by selecting the contents of the staff - click first measure, press Shift+Ctrl+End to select to the end or scroll to the end then shift+click the last measure, then press Ctrl+down). It will be more playable, but will of course sound an octave lower than it currently does, because again, that's just how a bass clarinet is - it really *does* sound an octave lower than a cornet.
The reason the key changes when you tery messing with the play transposition is that the part is currently transposed correctly: an octave *plus* a major second. You are changing the transposition to an *incorrect* value - only an octave. This changes the key from G (correct) to F (incorrect). The piece is actually in F (as you can see if you turn on "Concert Pitch"), and for any Bb instrument like bass clarinet, that translated to the key of G. When you lied to MuseScore about the transposition - telling it the transposition was an octave rather than a major second plus an octave - it changed the key to match. Again, this is completely correct: *if* bass clarinet transposed by only an octave instead of an octave plus a major second, then F *would* be the right key.
The reason the notes go up when you specify down as the play transposition and vice versa is that this field does what it says: it specifies the transposition to be applied *on playback*. When you tell MsueScore an instrument has a play transposition of an octave up, you are telling it that it sounds an octave higher than wirtten (which is not true, but it is what you are saying) so MuseScore dutifully transposes the written music down an octave so that on playback it will sound correct.
So everything you are describing is correct behavior.
If you have further questions on how MuseScore works, or how transposing instruments work in general, please use the support forum. You might start, however, by doing some research on transposing instruments.
Thanks Marc, I am familiar with what transposing instruments are, my error was assuming that changing the instrument would create a part playable by the new instrument chosen rather then moving the notes on the staff that would produce the same pitch with the new instrument. Logic says however, that is should not do that!
I changed the play transposition from major second only to eliminate it possibly affecting the octave shift, that is when I found it would jump 2 octaves when I selected up rather than down. I still don't understand why that is so, but it matters not. I'll do it the "normal" way from now on.
Thanks again and sorry to waste you time.
Best regards.