So I experimented with playback and it indeed sounds horrible. What I want to do now, is something like the Explode command. This I'll have musescore translate the encoded Figured Bass into notes on a staff which the user can then manipulate manually.
With regard to your question of how to interpret ambiguous notation. Yes of course you are correct. I suspect the final solution will have a GUI to allow the user to control the meanings of certain ambiguous items. The first ambiguity I encountered is that sometimes lack of a FB under a note means "don't play a chord", but sometimes it means "play the obvious chord". I was thinking of using a rule of thumb: No notation under the tonic, dominant, or subdominant means "play the obvious chord", otherwise it means "no chord". On the other hand, it is easier to delete a wrong note than enter a correct note. -- View this message in context: http://dev-list.musescore.org/programmatic-access-of-figured-bass-tp7579343p7579371.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
