Switching "Concert Pitch" is incorrect

• Apr 27, 2019 - 06:43
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project

1.) Download attached .mscz file
2.) toggle "Concert Pitch" off then turn it back on.

Concert Pitch does not retain the original "6 Sharps" and changes to various enharmonics in flats.

This file was generated as a "Part" from an overall score. The whole score and arrangement was written in the key of E Major (4 Sharps) with the "Concert Pitch" toggle on. Upon finishing the arrangement and attempting to export parts, the "Concert Pitch" toggle remained on in each part. In the file provided, It's in Concert F# Major (6 Sharps) when it should be Concert E Major (4 Sharps). The key of F# would technically be the correct transposition from C to a Bb instrument, but it did not correctly move the notes.

This bug could not be reproduced trying to make a brand new score and exporting parts.
If further examples and documentation is needed of this issue, I can do my best to provide with the arrangement and score I am currently working on.

Thank you

Attachment Size
Terminal Terminal (Clarinet Part).mscz 31.12 KB

Comments

Status active needs info

I believe you are seeing the result of a known bug, already fixed in 3.1 beta, where if you save a score with concert pitch on, that setting gets forced onto the parts as well, but in a way that actually messes up the transpositions, because the wrong pitches were saved.

Would you agree this sounds like what happened? If so, we can close this. Otherwise, we would need more information on what actually did happen.

Either way, it should work to delete the parts and regenerated them - and then be careful note to save the score with concert pitch on, until you update to 3.1.

Status needs info duplicate

If you haven't done so already, you could at least try things like re-adding the key signature, or using Tools / Transpose, to see if you can kick things back into shape. Also consider installing the 3.1 beta, which won't repair the existing file, but will keep the problem from happening again.