display problems converting between concert pitch and conventional pitch

• Oct 31, 2014 - 19:19
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

I've attached a score which demonstrates the problem.
When you view it with Concert Pitch enabled, the notes of the English Horn display properly.
And play correctly.
But when I turn off concert pitch the notes are wrong.
For example notice in the 3rd measure the D and the C do not change position, but the other notes do.
In either case when I play the score it sounds correct (to my ear).

Attachment Size
rondo-oboe-english-horn-6.mscz 15.44 KB

Comments

• Oct 31, 2014 - 19:38

Something is weird with the English Horn because it's supposed to transpose by a fifth, but it's doing some weird octave jumping.

Reply

• Oct 31, 2014 - 19:46

Is it possible the score was created with an older build - something pre-Beta? If so, that would be the source of the problem right there.

If you created this from scratch in the build from an hour before your post - first, congrats on such fast note entry :-) - but second, it would be good know *how* you entered the notes that are the problem. Eg, clicking on staff, typing, MIDI keybaord, copy/paste, etc.

Reply

• Oct 31, 2014 - 20:25

Yes I created this in an older version indeed. I don't know which version anymore as I had not updated in a while. When I noticed the problem, I upgraded to the newest to see if the problem is fixed. But I saw that the problem remains.

When I created it, I created by entering the notes one by one manually. I usually do this from the keyboard by typing abcdefg 3456 and cmd-up and cmd-down etc.

Reply

• Oct 31, 2014 - 20:48
Status (old) needs info ⇒ closed

If it was created in an older build, then that explains it. The problem is caused by incompatibility between builds - anything saved before, oh, maybe around March won't work when opened in current builds. It's not a bug in the older version or a bug in the current version - it's just what happens when two incompatible versions try to read each others' files.

Best workaround I know to solve this particular incompatibility would be to select all, then press up arrow followed by down arrow, which will recomputer all the pitches (and re-spell accidentals, so be prepared to do some fixup). Chances are, though, other things will still be wrong because of incompatibility. Realistically, you just cannot expect files saved in much older builds to still work. Much has changed. Files created starting with the Beta or more recent builds should, so far, be fine.

Reply

• Oct 31, 2014 - 21:19

Thanks for the information about the workaround. But alas it does not work. pressing up then down or down then up return me to the same as before. :-(
Is there another possibility, such as xml-out/xml-in ?

Reply

• Oct 31, 2014 - 21:27

It seems a workaround is to create a new instrument, (say a flute), select and copy the english or staff to the flute. Delete all the notes in the english horn staff, then copy the flute back to english horn.

Reply

• Oct 31, 2014 - 22:22

Be sure to be in conert pitch mode when you do the up/down. Works for me. When I then turn concert pitch off, thens are as they should be.

BTW, selecting a range in MuseScore is much like most other programs: click beginning, shift+click end. Or click beginning, then press shift+ctrl+end.

Reply

• Nov 1, 2014 - 16:15

The other way is as I said: click the beginning of the selection, shift+click the end. For keybaord use, you could click the first measure, then Sift+Right and hold it is down until you reach the end. Practical for short scores, maybe not for ones that are hundreds of measures long. Some keyboards with no End key have a shortcut that provides that function. On my Chromebook, for example, it's Search+Right. You might check to see if any documentation came with the computer/keyboard. That's a Mac, right? Somewhere or other there must be published lists of keybaord shortcuts for stuff like that, the fact that you need Fn+Delete to do a true "Delete", etc.

Reply