Closed ratnanil closed 5 years ago
Thanks for sharing. Yeah that is not ideal. And no, I didn't make this plotting function with guitarChords
in mind; it's more general purpose. As it says in the help docs, "under development and subject to change". Given that, I just improved the function, including fixing some glaring bugs so it works better now when you have a fret range that does not include zero, and took the liberty of changing the name to plot_fretboard
. More to your concern, I added a corresponding plot_chord
wrapper that is more tailored to individual chord fretboard diagrams like this use case. Going forward you should use that for specific chord diagrams and use plot_fretboard
for more general patterns.
See the updated help file for examples and details. plot_chord
will take the simple fret notation like xo221o
(or x02210
). You can also leave off any leading x
: (02210
). If you have two-digit fret numbers, the simple format won't work but you can use spaces or semicolons (like LilyPond format) such as "x 8 10 10 10 8"
or "8;10;10;10;8"
. For plot_chord
muted strings are inferred from the x
.
Given that guitarChords
is specifically for guitar chords I think it makes sense to have this variant of the function that works with this. No need to convert the concise fretted strings notation into two arbitrary vector sequences yourself as if you were defining a long scale run.
I'd like to plot some Chords with
fretboard_plot()
based on the datasetguitarChords
. I prefer to usefretboard_plot()
overtab()
since the latter only outputs to pdf, and I'd like to display the chords in a markdown file as simply as possible.Anyway, is it true that the dataset
guitarChords
is not really optimized forfretboard_plot()
or vice versa? What I'm currently doing is something like this:Created on 2019-11-04 by the reprex package (v0.3.0)
Is there a better way?