Re: [musicxml] Add a listen element for score following and machine listening apps (#294)

Thank you for the added feedback @bhamblok! 

One clarification is that the `<listen>` element will generally not need to be written except in more unusual situations. I do not think the addition of these `<player>` and `<listen>` elements will bog down applications that do not use them. I do agree that if applications were writing `<listen>` elements for most notes, this solution would not be desirable.

Score following applications are already using MusicXML and are probably not interested in a separate performance-only format. The choices would seem to be either the status quo, where each application requires its own app-specific data, or something standardized. With a standardized approach, a music notation editing application can write one set of data that many different listening apps can use.

MNX's separation of concerns is trying to make a clearer distinction between different types of data than MusicXML does, in order to make application development easier. It is not trying to remove MusicXML functionality from MNX-Common. The proposal here follows the way that MusicXML handles this type of separation, using dedicated elements as well as attributes.

-- 
GitHub Notification of comment by mdgood
Please view or discuss this issue at https://github.com/w3c/musicxml/issues/294#issuecomment-544754642 using your GitHub account

Received on Monday, 21 October 2019 23:50:31 UTC