List view
Anything which I wrote in my report as future features. These are mostly abstract so here I'm just noting them, when features are to be introduced they should be turned into milestones
No due date•0/6 issues closedissues relating to packaging the app for different OSes
No due date•5/8 issues closed- No due date•0/3 issues closed
- No due date•5/7 issues closed
Any issues relating to the creation of a GUI. whilst this isn't an objective on the list, this is considered a "universal" objective, meaning that it definitely should exist otherwise the demo will be a bit crap, and all things functionality should link to it
No due date•59/67 issues closedAny work towards making the entire system, or sections of the system, usable on machines other than Mac and portable so that new testers or contributors can install it using a 1 command or 1 click install.
No due date•3/6 issues closedSECONDARY OBJECTIVE
No due dateSECONDARY OBJECTIVE: believe this can actually be done with lilypond (\midi{} command) but output of objects to sound
No due dateSECONDARY OBJECTIVE: calculation of how hard or easy a piece is. Rating of 1-10, 1 being easy, 10 being difficult. Calculations should at first be general (i.e count things like accidentals, semi quavers etc), then if there's time be instrument specific based on player feedback
No due date•0/1 issues closed- No due date•18/19 issues closed
any issues relating to automatic extraction of info about each score - clefs, meters, piece name etc.
No due date•22/23 issues closed