Posting the Chord changes above the melody
I am posting the chords changes on top of the melody note. for example: C Dm G7, etc...
I am having a problem when I try and post " Bb". For some reasons, the MuseScore.app will not let me post the "b" in "Bb".
Is anybody aware of this problem. When posting a chord, the data field should be typed as Char and nums.
Thanks
Rob
Comments
What version of MuseScore are you using? What operating system?
In reply to What version of MuseScore are by David Bolton
Hi David:
I am using musescore version 0.9.5 and revision 2012.
my computer is a MAC OS X version 10.5.8
thanks
Rob
In reply to posting chord names above the melody by rebelrob
See New features in MuseScore 0.9.6 , "Fixes to Mac-specific bugs"
In reply to See New features in MuseScore by David Bolton
Thanks again David:
I would like to download MuseScore 0.9.6 for the MAC, but I can not seem to find it. Could you please send me a link for the
download page.
Also, I was a software developer for years, and I would be happy to report problems or upgrade suggestions. My expertise is making software as intuitive as possible.
Thanks
Rob
In reply to chord names above the melody notes using a MAC by rebelrob
There is no release for MuseScore 0.9.6. You can download a release candidate at http://prereleases.musescore.org
In reply to There is no release for by [DELETED] 5
ok, thanks - i found it and I am using it. When I post a chord name above the melody note (example Bb), I notice the program converts the "b" to a flat and inserts it next to the "B". While I am not complaining and will donate at some point, I feel the data field for the chord name should be typed char/num. This would remove the function code that converts the "b" to the flat symbol, and would allow the user to input the following: Bb, Bmaj7, Bm7, B minor 7, Bb #5/b9 or
Bb +5 -9, - etc... The developer may think it is a small point and not important, but users of this program are music people and have their way of notating a chord, and it would remove code from the program. Or, the developer could put the way the program post a chord in the "program options". This would give the user a choice. Example:
User program options:
1) Allow chord notation automated y or n
2) Allow chord notation manual y or n
Then in the source code:
if chord_auto = "y"
=chord_auto()
else
=chord_manual()
endif
Just my thoughts.
Thanks
Rob
In reply to MAC release candidate by rebelrob
There is a reason about these features. For MuseScore being able to transpose, export to MusicXML (interoperability with Finale, Sibelius etc...), support chord with different style (stacked extension) and maybe in the future melody generation from chord sequence, it's very convenient to have standardized chordnames.
If you don't want to use chords, but just text, you can use staff text (Ctrl + T) but you will loose all these features.