All dictionary objects in MNX can now have a _c<\/strong> object (comment), which can be a string. Adrian has added some comments to a few of the examples by means of demonstration (e.g. here<\/a>).<\/p>\n\n\n\n Adrian has also added the _x<\/strong> object (extension) to every object for vendor-specific extensions, and as the first example of its use, the MNX documentation now uses the _x<\/strong> object to define areas that can be highlighted in examples to draw attention to particular parts of the encoding.<\/p>\n\n\n\n The documentation now also lists the globally-available attributes in a special section at the bottom of each object page, rather than listing them as if they were specific to that object, which you can see e.g. here<\/a>.<\/p>\n\n\n\n Adrian has also changed the word “keys” to “attributes” throughout the documentation as this seems to fit better with our use of the word “object”.<\/p>\n\n\n\n Adrian discovered via Reddit a new GitHub project from Oliver Paddock called Capo-Compose<\/a> that defines a new text-based language for describing music notation that compiles to MNX.<\/p>\n\n\n\n Up next, Adrian plans to complete the encoding of multi-note tremolos, which the co-chairs discussed in the London workshop<\/a> back in July (issue #119<\/a>).<\/p>\n\n\n\n The attachment of directions to grace notes was discussed (#602<\/a>) and it was confirmed that the documentation is correct.<\/p>\n\n\n\n The next co-chair’s meeting is scheduled for Thursday 9 October 2025<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":" MNX All dictionary objects in MNX can now have a _c object (comment), which can be a string. Adrian has added some comments to a few of the examples by means of demonstration (e.g. here). Adrian has also added the … Continue reading MusicXML<\/h2>\n\n\n\n
Next meeting<\/h2>\n\n\n\n