#4 Wrong powerchords

[Rodrigo Rocha]

Clicking with the middle button on the melody editor
(guitar neck), in order to generate a powerchord, the
result is wrong when clicking in the D or G string. For
example, consider the standard guitar tuning. When
clicking on D string, 2nd fret, the resulting
powerchord should be xx245x (and not xx244x). When
clicking on G string, 2nd fret, the result should be
xxx255 (and not xxx244).

[Mikhail Yakshin]

Logged In: YES
user_id=46975
Originator: NO

I'm not sure that it's really a bug. We just set the tab template (0, +2, +2), not stating really (root, 7', octave). Without taking it simple, non-E tunings would instantly become a mess. How would the program know how to make "traditional" power chords on any tuning besides of E or drop-D?

I see following solutions:

1. Add (0, +2, +3) as a selectable alternative.
2. Add (root, 7', octave) as a selectable alternative, but how to produce good fingerings then?
3. Do nothing and leave it as it is.

I tend to lean to the third choice :)

[Rodrigo Rocha]

Logged In: YES
user_id=1116323
Originator: YES

I understand that it's not a bug because it works exactly as thought, but it's a little misleading. It seems that powerchords are important, because they deserve a feature, but they're not so important that they need to be implemented correctly. If this is the case, then option 3 is a good choice. Users will be disappointed and blame KGuitar the first time they need to setup a powerchord manually, though.

I prefer option 2. In this case, KGuitar could look for the fifth on the string just below the root, and look for the octave on the string just below the fifth. The result will always sound correct. Some users of strange tunings will still be disappointed if KGuitar doesn't find a good fingering, but most users will be happy. :)

Anyway, this is a low priority bug/feature-request, in my opinion.

[Mikhail Yakshin]

Logged In: YES
user_id=46975
Originator: NO

Okay, I'm adding it as low-priority task.