Nightly possible problem with key signature?

• Nov 4, 2014 - 11:24

Hi
I downloaded a Nightly at the weekend to start another arrangement.

1efc609

As I am not clever enough to write at written pitches, I always write 'at concert'. Having just started the arrangement I thought I'd better check that all was well "so far" and clicked to go to "written pitch".

Alto 1 transposed perfectly but Alto 2, Baritone and Trumpets did not (as far as the written score is concerned). They 'play' perfectly.

I am including screen shots and the score so far just in case its something I've done -which I don't think I have as I started it the way I always did with MS 1.3. If it turns out that I haven't done anything silly, then it'll need reporting to the bug controllers.


Comments

I think what you donwloaded is not a Nightly build but the Beta build, which is rather older. And what you are seeing is very possibly a bug that was fixed since the Beta. Probably this one:

#31571: Adding transposing instrument to a score in C yields no key signature

I'm curious, did you start this from the Jazz Big Band template? If so I'm somewhat surprised this happened even with the Beta. But if you started from scratch or from some other other template started adding instruments later, that would explain it. As far as I know, that bug affected only instruments added after initial score creation, and only scores in "C".

In reply to by Marc Sabatella

Thanks Marc
as far as I was aware I went to the Nightly section. I really don't want to believe I downloaded the wrong one after psyching myself up to a nightly!
Anyways, whatever I've done, yes I started from the Big Band template.
Is the attached bitmap the latest version. And if it is and once I've got it going, will I be able to copy my arrangement "across" to it or will I drag the bug as well?

Thanks for your continues patience marc

In reply to by onscuba

It looks like you *installed* the nightly, but you might still have the Beta on your system as well, and perhaps you accidentally ran that instead.

Even though the bug I mentioned only affects instruments created after initial score creation, I wouldn't be surprised if templates weren't "special" somehow (different from creating scores from scratch) and that the same bug might affect scores in "C" created from template. In any event, I can't reproduce in a Nightly build.

The bug itself is pretty harmless - the only thing that went wrong is that the key signature was not crerated. So create it manually. Should be fine.

In reply to by Marc Sabatella

It won't allow me to add the correct key sig. at the start of the score. EG Tpts should be 2 #'s. So when I add 2 #s to the tpt staff it suddenly shows 4 !! (so it knows there should be 2 and then presumably adds the new ones that I just entered.
I do indeed have the MS beta on my system but in a separate folder so I can't get them mixed up.

agghhhh, The last screen shot was from my search just now. So my question really should have read something like...

"Is this the latest nightly version, and if so, I WILL download that one to make sure I'm on the latest version"

In reply to by onscuba

When you drag a key signature to your score in 2.0 builds, it affects *all* staves, not just the one you are dragging to. Normally, of course, that's exactly what you want. But since it affects all staves, it currently expects you to use the concert key. So drag C major to any staff, and all staves will be updated with the correct transposed key.

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