Bug in cchords_nrb.xml style rendering?

• May 19, 2013 - 19:36


I'm trying to use the cchords_nrb.xml style but it's not working on Xyy7(#9). For example, I enter "Gmi7(#9)" or "C+7(#9)"(without quotes) and it does not convert to the style (remains in normal font). Other chord names seem to be correctly rendered, including "G7(#9)", "Gmi7", "C+7".

Version - 2.0.0 Rev 3c35a97
OS - Ubuntu 12.04


EDIT: It also does not work for "X6/9", e.g., "E6/9". If I enter this chord name then unselect it, then re-edit, it changes the name to "E6".


I've got bad news and good news, but mostly good news.

The first bit of bad news is, MuseScore has a very specific list of chords it recognizes (borrowed from Band in a Box), and if the chord you are trying to enter isn't on the list, it won't be recognized.

The first bit of good news is, 2.0 - and I see you are using a 2.0 build - will have some important improvements over 1.3. You may have noticed already that 2.0 is now much more forgiving of *how* you enter a chord. So to get a minor seventh chord, you can now type "m", "mi", "min", or "-", and it will be recognized as minor and rendered according to cchords_nrb or whatever chord description file you are using. Whereas 1.3 requires you to type chords exactly the way your chord description file intends to render them. So a big gain in flexibility of input.

But even in current 2.0 builds, the basic chord you are trying to enter has to be on the list, or it just won't work. And "minor seventh sharp nine" (by any spelling) is not on the list, nor is "augmented seventh sharp nine", although "dominant seventh sharp five sharp nine" is. Also, "six nine" is, but the second bit of bad news is that entering chords with slashes won't work - MuseScore will misinterpret it as a slash chord.

Now, the next bit of good news - I'm working on, and just about done with, a further improvement that will let you type just about anything you want and have it rendered as you typed it - no need for it it to match something on the predefined list. It will just have to be something the parser can work with. Once that is in place, Gmi7(#9) and C+7(#9) will both start working. Even though, when you think about it, Gmi7(#9) doesn't really make sense the #9 is going to be the same note as the minor third of the chord.

OK, last bit of good news - even though you won't be able to *type* "E6/9", it is already possible, and will remain so, to configure things so you can type "E69" but have it *rendered* as E6/9. Just edit the cchords_nrb.xml file. I'd explain how, but that's going to get easier too when these changes go through. So for now, just type "E69" and accept that it won't display with a slash (unless you feel like figuring out the syntax of the cchords_xml file for yourself, which actually isn't all that hard).

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