As many of you already know, I’m a Finale refugee and am working diligently to learn Dorico as I work. The purpose of this “topic” is to address chord creation and spark a discussion aimed at making the “Dorico way” better.
First and foremost, the Dorico/Steinberg engineers have decided to create chord definitions that are 1. Carved in stone, 2. Cannot be altered without changing the definition on a global scale, and 3. Dorico does not allow the individual user to create their own chord definitions. While this might be a European system, there are far too many non-Europeans using Dorico to not consider a different path.
First, chord definitions should never have been tied to individual notes/tones. Finale allows the user to add a playable suffix to any of the 12 chromatic notes and to define new chords suffixes as needed. Inputting chords is easily done by typing in the base note of the chord then either typing in or selecting from a menu the desired chord suffix (min, min7, min7b5, etc). The mere notion that the only chord definitions I can utilize when composing, arranging, or transcribing are the ones the Dorico/Steinberg engineers allow or have already programmed is ludicrous at best. Additionally, requiring engineers to program Cmaj7, C#maj7, Dmaj7, Ebmaj7, ect. is, IMO, enormously time consuming. Especially when you have to add any number of chord extensions to each of the “base” chords. Far better to have a library of chord suffixes that can be attached to any of the 12 chromatic tones.
Further, the user should be able to select any chord suffix (see above), duplicate it, change it to suit their needs, and have it automatically added to their chord suffix library for future use. The original remains unchanged and there’s no adverse effect on music/files already created.
Finally, the user/creator absolutely must be allowed to create chord definitions suited to the music they’re composing, arranging, or transcribing. LOL… how dare some software engineer tell me what I can and cannot write.
I realize this is, in some ways, “beating a dead horse” but the desire is to make the software more adaptable to everyone’s use rather than being forced into workarounds because programmers have already created the system they want and have no desire to upgrade or change. Yes, I know, it’s time and money. I get it… but there are several million of us using the software who’ll be paying for upgrades in the future. I’m not suggesting Dorico become Finale; far from it. There are any number of things Dorico does better than Finale and I think we all realize there are some things Finale does/did better than Dorico.
Please do give this some consideration.
Thanks,
Kerry
MacBook Pro, OSX 14.5, Dorico 5.1.6