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

Missing explicit accidental for Trm0047m #18

Open
emilianoricciardi opened this issue Apr 3, 2017 · 3 comments
Open

Missing explicit accidental for Trm0047m #18

emilianoricciardi opened this issue Apr 3, 2017 · 3 comments

Comments

@emilianoricciardi
Copy link
Contributor

C, m. 4 (second c sharp is not showing in the PDF)

@craigsapp
Copy link
Contributor

This is a bug in the MuseData printing system or the converter from Humdrum into Musedata.

Problem measure in MuseData-generated PDF, 4th measure canto part:

screen shot 2017-04-03 at 12 54 16 pm

In the verovio rendering it is correct:

screen shot 2017-04-03 at 12 55 17 pm

And the Humdrum data is correct:

=4	=4	=4	=4	=4	=4
1r	.	2a	ma-	4cc#X	.
.	.	.	.	2dd	.
.	.	2a	-no	.	.
.	.	.	.	4cc#X	.
1G	Non	2r	.	2dd	-li
.	.	2g	Che	4.b	A-
.	.	.	.	8b	-ven-
=5	=5	=5	=5	=5	=5

The X on the second C# in the second to last column means to show the accidental in the printed notatation.

The MuseData conversion also seems correct, as there is a "+" marker in column 33, which means to show the accidental:

measure 4
C#5    4      1 q               +          -
D5     8      1 h                          -
C#5    4      1 q               +          -
D5     8      1 h                          li
B4     6      1 q.                         A-
B4     2      1 e                          ven-

So not likely to be a bug in the hum2muse converter, and muse likely to be within the muse2ps converter from MuseData to PostScript.

@emilianoricciardi
Copy link
Contributor Author

emilianoricciardi commented Apr 3, 2017 via email

@craigsapp
Copy link
Contributor

You don't have to reply to such messages @emilianoricciardi (or this one :-). They are just notes in the progress of tracking down the problem.

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

2 participants