strange transposed score
I have a score in c-flat-major that I want to transpose to b-major. I.e., the tones don't change but all the notes change from the c-flat representation to the b representation.
Could someone tell me whether these results are as expected, or if this is a bug in which case I can file a bug report.
What I expect is that there are no # signs in the score. All of the notes are implicitly flat in the C-flat score (as c-flat has 7 flats), and 5 of the notes are sharp in the B score. But these should be implicit by the key signature. I don't want redundant shapes in the score after transposition.
I'm attaching screen shots of what I see before (c-flat-major) and after (b-major), as well as the values in the transpose form which I chose.
I"ll also attach the scores before and after.
I'm using a pretty recent nightly build, but not todays. I"m happy to try it in the latest if someone thinks this is something which has been fixed.
Attachment | Size |
---|---|
screen-shot-c-flat-major.png | 341.99 KB |
screen-shot-B-major.png | 369.81 KB |
screen-shot-tanspose-B.png | 151.91 KB |
ascending_3rds-c-flat.mscz | 2.34 KB |
ascending_3rds-b.mscz | 2.45 KB |
Comments
using to-day nightly 957d375 under Linux Mint your ascending_3rds-c-flat.mscz 2.34 Ko shows nice. see attached
In reply to using to-day nightly 957d375 by robert leleu
That is interesting, when I close the score in B (with all the redundant # signs) and simply reopen it, it displays correctly. Robert, what happens when you transpose the C-flat version to B with the options I've shown in the form? Does it show the ugly version?
In reply to That is interesting, when I by jim.newton.562
yes, it does.
so it's a minor bug that you have to report
In reply to yes, it does. so it's a minor by robert leleu
I filed it as a bug. http://musescore.org/en/node/25904