sharp sign in chord (keyboard issue?)
I use an azerty-keyboard (Belgium) and can't get the sharp sign to work with mscore.
G739 or G7"9 is what I get instead of G7sharp9.
Unstable prerelease for version 0.9.5_revision 1898
Ubuntu 9.04
Do you still have an unanswered question? Please log in first to post your question.
Comments
I can't reproduce the problem with a QWERTY (USA) keyboard. Have you encountered this problem before using earlier releases?
Does the number sign (#) work anywhere in MuseScore (such as the page title?)
In reply to I can't reproduce the problem by David Bolton
It doesn't work in the title region either, which made me realize it is actually a keyboard issue, not mscore.
It doesn't even work in an OpenOffice document, so I put the issue in the wrong forum (blush)
(Unless any other belgian azerty users here have a solution??)
I'm having a similar problem. I'm using a British keyboard, where the sharp sign is usually ALT+3. This works in all other applications, but pressing it has no effect anywhere in MuseScore. Even worse, if I copy a # onto the clipboard, I can't even paste it into a chord name.
In fact if I try to enter a # into a text field in the MuseScore Preferences dialog, I get a message "No note selected. Please select a single note and retry operation". However, COMMAND+V to paste it in does work here.
Help!
In reply to I'm having a similar problem. by Ian Goldby
I am able to copy text from another application and paste it into the chord name text field. I'm not sure why it doesn't work for you.
As a workaround go to Edit > Preferences > Shortcuts and look for "enter third below". Change the shortcut to something other than Alt+3.
Note to developers, Mac OS uses the Alt key to add special characters. Windows and Linux do not behave this way so the problem is limited to the Mac version of MuseScore.
In reply to I am able to copy text from by David Bolton
Still not working.
I have discovered that copy/paste just doesn't work at all in score elements. I can't copy in or out of MuseScore.
Reassigning the Alt-key shortcuts in Preferences means I can now type # characters in the text boxes in the Preferences dialog, but I still can't type # (or any other alt-combination characters) in score elements. The keystroke is just seemingly ignored.
The only slight oddity is that if I type alt-e followed by e then I get an e-acute (é) character, as is normal with OS X. So it is not as if MuseScore is ignoring the alt key completely, or ignoring all non-ASCII characters. Very puzzling.
In reply to Still not working. I have by Ian Goldby
I can work around this problem for now by switching to the US keyboard layout. Obviously this is not ideal because now the keycaps don't match the glyphs. But at least I can complete the score I am working on.
In reply to I can work around this by Ian Goldby
As it says, this is still an issue in 0.9.6 r2811.
Also I find I cannot enter minor chords because 'm' is recognised as the shortcut for opening the mixer. I have to go to keyboard shortcut preferences and change the mixer shortcut to something else. This is also a problem when entering lyrics.
Surely the keyboard shortcuts should be ignored when editing chord names, etc?
I also notice that although I can change the shortcut preferences and it works for the current session, the changes are not remembered. They have to be re-entered each time.
This is on a Mac, OS X 10.6.3.
--
colin
In reply to Still an issue in 0.9.6 r 2811 by cwhysall
For the "m" shortcut problem see: http://musescore.org/en/node/4817
For the shortcut preferences saving for the next session see: http://musescore.org/en/node/2590
Both of these problems are fixed in the latest nightly builds . The next prerelease (Release Candidate 1) is expected sometime next week.
In reply to For the "m" shortcut problem by David Bolton
Having been directed here because my previous discussion about # in chords was in another thread...
I've tried re-mapping the Shortcuts, but nothing happened. I re-mapped 'Enter a 3rd Above' to another key combo, to free up [ALT 3] (the logical place for us UK Mac users), and set that to #. Neither mapping exercise worked.
My current workaround is to use * when inputting chords, then go back and manually replace the *s with #s using the Z palette, but this is far from ideal.
I can't use a different layout because that would make a nonsense of all sorts of other things.
Is there a better method yet, please, and if not when might one arrive?
Thanks
Tom
In reply to Having been directed here by TomBliss
Same problem as above, can't fix it with any of the suggestions.
In reply to Same problem by bundu
@bundu What MuseScore version do you use and on which platform (Operating System)?
In reply to Version + OS by Thomas
Hi
I have version 1.1 and OS 10.6.8
I noticed it does not let me write º either (alt-0), although interestingly when I re-opened today, it had changed all my dim to º and superscripted the numbers, which it was not doing yesterday. It won't change the font size though, or even the font (when I hit tab, it just reverts to the original).
In reply to Version + OS by bundu
MuseScore automatically recognizes certain chords and certain chords only. The spelling that is recognized is controlled by your current Style settings. See the Handbook section on Chord names for more info. Depending on what style you are currently using, it is indeed normal that typing a recognized chord name will cause it to be reformatted apprropriately, and if you then change styles, it will change how that chord is displayed, including perhaps changing dim to the small circle if you change from a style that uses dim to a style that uses the small circle. So read the Handbook section, also search the site for my tutorial on doing lead sheets.
You never have full control over font with chord symbols, though, because the program Automatically reformats anything it recognizes (superscripting extensions and alterations, makng the root larger than other symbols, etc. again, that's all controlled by the particular Style you currently have loaded.
In reply to MuseScore automatically by Marc Sabatella
Yeah, thanks, it wasn't automatically formatting the chord symbols but it is now after a reboot.
I think this has gone a little off topic though, which is trying to get the (alt 3) to work in order to place a # sign.