Add support for reading multinote markings from MusicXML #32
Assignees
Comments
otsob
changed the title
otsob
added a commit
that referenced
this issue
May 24, 2019
Use same methods for reading scores in all tests where possible. Do not unnecessarily validate scores that can be expected to be valid.
otsob
added a commit
that referenced
this issue
May 24, 2019
otsob
added a commit
that referenced
this issue
May 24, 2019
Change tie beginning container to have a more generic name so that it can sensibly be used for other connections between notes.
otsob
added a commit
that referenced
this issue
May 24, 2019
Add support for reading markings that span multiple notes within the same voice in the same part.
otsob
added a commit
that referenced
this issue
May 24, 2019
otsob
added a commit
that referenced
this issue
May 24, 2019
otsob
added a commit
that referenced
this issue
May 24, 2019
Trying to read articulations from other types of nodes is unnecessary and leads to logging warnings.
otsob
added a commit
that referenced
this issue
May 24, 2019
Issue #32: Add support for reading markings from MusicXML Adds support for reading markings (slurs, glissando) from MusicXML. The implementation only supports markings that occur between notes in the same voice. Handling of slurs that cross parts and voices is more complex and is to be handled in issue #109
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to read multinote markings from MusicXML
as a user
I want MusicXML reading to correctly add multinote markings to Scores
Acceptance criteria:
The text was updated successfully, but these errors were encountered: