Tom Conti-Leslie
Tom Conti-Leslie
There are a number of improvements to the code which would make it more easily maintainable and executable. - [ ] Swap out ungodly lists of function arguments for `**kwargs`,...
Currently the first element of the list of interpreted notes is considered the root, and the following notes are considered the important ones. I suggest we make the interpretation function...
See `interpret.py`. Chord alterations are handled blindly, without taking any context from the given chord. This is fine if the alteration is `(#5)`, for example, since `5` is unambiguous. However,...
Chord alterations get added to the end of the list of target notes (see `interpret.py`). On instruments with few notes this means the altered note may not appear. Altered notes...
In the interpretation phase, if the chord does not match any qualities, there should be a last resort to check if the string ends in `sus`, `sus4`, `sus2`. In these...
Have a part of the README (or the Wiki) just have a list of a load of command line usage examples. Start by saying you should add ``` alias tc="python3...
So that other users can contribute more effectively, we should create some explanatory documents showing - perhaps in the form of a flowchart - the full process of handling a...
Matching a chord quality is case sensitive because we need to be able to distinguish between `M` and `m`. However, if a chord request string has a quality which doesn't...
Currently, ranking of diagrams is done by looking at which notes are low, and how "stretched" the chord is (via various metrics). How can we get the algorithm to recognise...
In `output.py`, the `text` option indicates muted strings with an `x`: ``` x =========== | | | | O | | | O | | | | O | |...