Whenever the chordal seventh of an applied diminished chord isn’t diatonic to the project key, Hookpad starts to include nonsensical accidentals into the chord label.
Here are just some examples from C major:
Obviously every key signature will come with its own set of wrong chord labels.
Actually it seems to be the same set of chords that are causing this bug in every mode and it seemingly doesn’t matter whether the chordal seventh is diatonic to the project key or the key of the target chord, so I have no idea what causes this bug.
I also think it doesn’t make any sense how it always says “(maj)” when using applied diminished chords outside of major keys, as fully diminished chords aren’t even available in major.
1 Like
Thanks for bringing this up, I added it to our fix-list!
Regards!
Dennis
2 Likes
I just noticed that this happens with all types of applied chords. The screenshot below only shows examples of ii/x, IV/x and V/x, but it’s the same thing with iii/x and vi/x as well. It seems like applied chords erroneously inherit the accidentals of their target chords. For example dorian IV chords always have a flat in front of the seventh, so all chords that are applied to a dorian IV chord also have a flat in front of the seventh.
Ok, thanks for sharing this!
Related, and apologies if this has been mentioned before or if it’s already the way it should be: should secondary dominants and subdominants also be labeled “(maj)” when the project key isn’t major?
It seems odd that this needs a label more than V7/IV in a major project does.
Yes, I’ve been meaning to write a seperate bug report on this and I fully agree that it doesn’t make any sense.
2 Likes