Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with grace + tuplet conversion #5

Open
ahankinson opened this issue Apr 26, 2016 · 5 comments
Open

Issue with grace + tuplet conversion #5

ahankinson opened this issue Apr 26, 2016 · 5 comments

Comments

@ahankinson
Copy link
Member

From @rigaux on September 21, 2015 13:19

This score:
http://neuma.huma-num.fr/opus/timbres:cdc:0037
MusicXML: http://neuma.huma-num.fr/rest/timbres/cdc/0037/score.xml
MEI: http://neuma.huma-num.fr/rest/timbres/cdc/0037/mei.xml

Measures 5 and 9: each time, one note from the tuplet is missing, as well as the grace note

Copied from original issue: music-encoding/music-encoding#259

@ahankinson
Copy link
Member Author

I believe this one is fixed now.

@ahankinson
Copy link
Member Author

From @pe-ro on September 28, 2015 17:42

Partially fixed, I believe. The stylesheet raises an error --

"Description: The attribute axis starting at an attribute node will never select anything
Start location: 10431:0"

and the problems reported in #258 aren't completely resolved; that is, the beamed grace notes in m. 4 and m. 5 aren't beamed properly.

@ahankinson
Copy link
Member Author

From @kepper on September 28, 2015 17:46

will look into this asap. Paid no attention to #258 (yet).

Am 28.09.2015 um 19:42 schrieb pe-ro [email protected]:

Partially fixed, I believe. The stylesheet raises an error --

"Description: The attribute axis starting at an attribute node will never select anything
Start location: 10431:0"

and the problems reported in #258 aren't completely resolved; that is, the beamed grace notes in m. 4 and m. 5 aren't beamed properly.


Reply to this email directly or view it on GitHub.

@ahankinson
Copy link
Member Author

From @pe-ro on September 28, 2015 17:49

Sorry, didn’t mean to get ahead of you.

p.

From: kepper [mailto:[email protected]]
Sent: Monday, September 28, 2015 1:47 PM
To: music-encoding/music-encoding
Cc: pe-ro
Subject: Re: [music-encoding] Issue with grace + tuplet conversion (#259)

will look into this asap. Paid no attention to #258 (yet).

Am 28.09.2015 um 19:42 schrieb pe-ro <[email protected]mailto:[email protected]>:

Partially fixed, I believe. The stylesheet raises an error --

"Description: The attribute axis starting at an attribute node will never select anything
Start location: 10431:0"

and the problems reported in #258 aren't completely resolved; that is, the beamed grace notes in m. 4 and m. 5 aren't beamed properly.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com/music-encoding/music-encoding/issues/259#issuecomment-143818267.

@ahankinson
Copy link
Member Author

From @kepper on September 28, 2015 17:50

All good. I hadn't noticed #258 as separate issue, so it's good you pointed me at it :-)

Am 28.09.2015 um 19:49 schrieb pe-ro [email protected]:

Sorry, didn’t mean to get ahead of you.

p.

From: kepper [mailto:[email protected]]
Sent: Monday, September 28, 2015 1:47 PM
To: music-encoding/music-encoding
Cc: pe-ro
Subject: Re: [music-encoding] Issue with grace + tuplet conversion (#259)

will look into this asap. Paid no attention to #258 (yet).

Am 28.09.2015 um 19:42 schrieb pe-ro <[email protected]mailto:[email protected]>:

Partially fixed, I believe. The stylesheet raises an error --

"Description: The attribute axis starting at an attribute node will never select anything
Start location: 10431:0"

and the problems reported in #258 aren't completely resolved; that is, the beamed grace notes in m. 4 and m. 5 aren't beamed properly.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com/music-encoding/music-encoding/issues/259#issuecomment-143818267.

Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant