copy/paste ignores respelling of accidentals

• Apr 23, 2015 - 18:09

I have a score that's in F major, but there's a section that's in G major and uses A# as a chromatic lower neighbor to B-natural. This note can be created by entering a Bb and then using Ctrl+j to choose an alternative spelling. However, when I copy and paste a block of music containing this note, it gets pasted back as a Bb, ignoring the respelling. Is there a way to get copy/paste to honor the actual spelling of the notes that have been copied?

This may or may not be related to the problem described in the topic "Spelling of accidentals will not stay put", but it seems sufficiently different I thought it would be best to open a new topic for it.


To get the A# to 'stay put' when copy/pasting. Do this:

1. Enter the A.
2. Click on the sharp sign (#) in the Note Entry Toolbar to turn the A into an A#. Copy/pasting this note should work.


In reply to by Jm6stringer

That probably works (I'm not able to check it right at the moment) but it strikes me as suboptimal. I do as much of my note entry as I can using the keyboard. It slows me down quite a bit to have to mouse up to the toolbar to change accidentals, so I'd like to avoid it if I can.

If you are seeing this with the release 2.0, then it is indeed the same issue, fixed a while back. If you are seeing this in a nightly build, it's a new issue - so please poist the specific score you are having problems with and precise steps to reproduce the problem. Note that simply taking an already-corrupt score (eg, one you created in 2.0 using Ctrl+J on a concert pitch instrument while not in concert pitch mode) and loading it into a nightly won't in itself fix the corruption - you'll have to re-fix the spelling.

In reply to by Marc Sabatella

Can you clarify this for me? I'm not familiar with concert pitch mode. Is it likely that I would be in the situation you describe (i.e., entering notes on a concert pitch instrument while not in concert pitch mode) by default, or is there some action I would need to have taken to get into this state?

I am running the 2.0 release, but I can try this on a nightly later today.

In reply to by ghicks

Concert pitch *off* is the default, so unless you turned it on. As for whether you are working with concert pirch instruments or not, I can't say, as I haven't seen your score. Generally, most wind instruments transpose, most others do not, so if you aren't specifically writing for winds, you are writing for concert pitch instruments. If you weren't familair with the "J" command, seems unlikely you'd have used it accidentally, but again, I don't really know. And again, using the arrow keys does work correctly in 2.0 regardless of mode. So if you have a specific score and a specific score that reproduces a problem, it would really help if you could post. We are getting ready to release 2.0.1 very soon, and if there is a bug here, we want to know so we can fix it!

In reply to by Marc Sabatella

I should have mentioned: the score is a piece for piano 4-hands, so it's most certainly a concert pitch instrument. If by the "J" command you mean just typing the j key, I wouldn't have done that on purpose, but I'm using Ctrl-j a lot to respell notes, so it's conceivable I might have done it by accident. I spend the majority of my time using the keyboard anyway, and typos happen.

The arrow keys are useless for me in this circumstance. If I'm trying to achieve an A# in a piece with that has Bb in the key signature, I don't seem to be able to get there using just the arrow keys. Up-arrow from A gives me Bb every time. The only way I've been able to find to get an A# using the keyboard is to enter a Bb and then respell it with Ctrl-j.

I'm not in a position to attach the score at the moment, but I'll do it as soon as I have a chance if you think it would be useful. I'll also download a nightly build and see if the same problem occurs there.

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