We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First off - great, fun library.
Your example of the C-chord in some tuning:
>>> print(c_chord.fingering(fretboard=fretboard)) (0, 0, 0, 3, 3, 3)
It was not clear which tuning this was, but modifying your example to standard tuning, the C-chord could be:
>>> print(c_chord.fingering(fretboard=fretboard)) (0, 3, 2, 0, 1, 0)
or is the orientation reversed?
>>> print(c_chord.fingering(fretboard=fretboard)) (0, 1, 0, 2, 3, 0)
You can see the uncertainty in both tuning and orientation. I think returning a namedtuple would clear up these confusions:
namedtuple
>>> print(c_chord.fingering(fretboard=fretboard)) Fingering('E'=0, 'A'=3, 'D'=2, 'G'=0, 'B'=1, 'e'=0)
The text was updated successfully, but these errors were encountered:
This was @kennethreitz's project. What happened?
Sorry, something went wrong.
Hi @pylang ,Kenneth just moved all of his projects to volunteer developers. The new maintainer of this project is @Zelgius
This is a good idea! Sorry that I'm just seeing this
No branches or pull requests
First off - great, fun library.
Your example of the C-chord in some tuning:
It was not clear which tuning this was, but modifying your example to standard tuning, the C-chord could be:
or is the orientation reversed?
You can see the uncertainty in both tuning and orientation. I think returning a
namedtuple
would clear up these confusions:The text was updated successfully, but these errors were encountered: