You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A bit of testing is needed to determine if precise timing information can be derived.
There is a possibility that it may be a fairly lossy format.
It's also not totally clear whether MusicXML supports a novel 'marker' element type. It appears be treated as generic text which means that various DAWs may encode or interpret it differently.
In practicality, using MusicXML may not be as worthwhile as other potential formats.
Preliminary Observations
For example, a MusicXML xml file exported from Digital Performer 10 is summarized below.
It contains two markers: one at 1:00:00:00, and another at 1:00:01:00
DP exports markers as Direction markings. The <direction> element with inner element <words> are used.
Similar to a MIDI file, it contains tempo, time signature, and PPQ information.
However, no frame rate or origin timecode information is included and would need to be supplied separately by the user.
Proposal
Add support for reading and authoring MusicXML.
Support for markers will be the main priority.
Considerations
A bit of testing is needed to determine if precise timing information can be derived.
Preliminary Observations
For example, a MusicXML xml file exported from Digital Performer 10 is summarized below.
<direction>
element with inner element<words>
are used.References
https://github.com/w3c/musicxml/blob/799e2defb2ece0ae7bafe08dcbcac25b2c631d53/schema/direction.mod#L83-L97
https://github.com/w3c/musicxml/blob/799e2defb2ece0ae7bafe08dcbcac25b2c631d53/schema/direction.mod#L117-L127
The text was updated successfully, but these errors were encountered: