I have completed MusicXML import & export of unrecognized chords and issued a pull request:
https://github.com/musescore/MuseScore/pull/381 This turned out to be much more involved than I had hoped, but I have tested extensively and it is working beautifully. The upshot is, chords can now be imported from MusicXML and will render correctly regardless of whether or not they are recognized as matching anything in the predefined chord id list, and unrecognized chords typed by the user will also export to MusicXML correctly (if they are syntactically "legal", anyhow) Combined with my previous changes that allow chords typed by the user to be recognized, transposed, and rendered correctly regardless of whether or not they are recognized as matching anything in the predefined chord list, there is now no reason to need a predefined chord id list any more. And with no predefined chord id list, the WYTIWYG behavior I have been talking about (recall the video I posted a while back, or see http://musescore.org/en/node/21202) happens automatically. I believe this is all ready for prime time. I would like to make this new WYTIWYG behavior the default for new scores. That is, I propose that we stop loading chords.xml by default, and that we change the default chord description file from stdchords.xml - or cchords_muse for the "Jazz" templates - to new ones I will provide that contain only token-rendering instructions, no predefined chord id list at all. I'd retain the ability to explicitly specify a different chord description file, so if *want* your chords to be "coerced" into rendering a particular way, you can continue to do so as before. And I'd make it so there would be no impact on existing scores or on people who have existing custom chord description files and/or custom templates. Before I actually do this, I thought I would open it up for discussion. I realize I've been pushing hard for what are some fairly big changes in chord symbol handling. This is one is small in that it is essentially just flipping a switch - the support for WYTIWYG is totally implemented and working - but it's bigger in impact. I got the sense there was some buy-in but also some reservations when I first announced that this was where I was going and showed it in action. FWIW, this would be the last significant change I would be proposing for chord symbols in 2.0. I'd still want to think about adding support for lower case chord names and "do, re, mi" naming, but that should be pretty trivial. And of course, I'd continue actively testing and fixing bugs. Marc -- View this message in context: http://dev-list.musescore.org/chord-symbol-import-export-tp7578124p7578167.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
