Summary
The fretboard plugin's overlay hardcodes a 6-string grid (FB_STRINGS = 6 in screen.js) and maps chart note string indices straight onto those 6 rows without ever calling highway.getStringCount(). On a 4-string bass arrangement this puts highlighted notes two rows off from where they're actually played (and the string labels e/B/G/D/A/E don't apply to a bass at all); 7/8-string GP imports have the inverse problem.
Tracked upstream in the plugin's own repo: got-feedBack/feedBack-plugin-fretboard#19
Repro
Play a bass (4-string) or extended-range (7/8-string) arrangement with the fretboard overlay toggled on — highlighted fret/string dots don't line up with the string the note is actually on.
Why here too
This repo vendors plugins/fretboard/ — filing here as well so it's visible against this deployment's plugin set until the upstream fix lands and gets synced in.
Summary
The
fretboardplugin's overlay hardcodes a 6-string grid (FB_STRINGS = 6inscreen.js) and maps chart note string indices straight onto those 6 rows without ever callinghighway.getStringCount(). On a 4-string bass arrangement this puts highlighted notes two rows off from where they're actually played (and the string labelse/B/G/D/A/Edon't apply to a bass at all); 7/8-string GP imports have the inverse problem.Tracked upstream in the plugin's own repo: got-feedBack/feedBack-plugin-fretboard#19
Repro
Play a bass (4-string) or extended-range (7/8-string) arrangement with the fretboard overlay toggled on — highlighted fret/string dots don't line up with the string the note is actually on.
Why here too
This repo vendors
plugins/fretboard/— filing here as well so it's visible against this deployment's plugin set until the upstream fix lands and gets synced in.