search

TassoInMusicProject / tasso-scores

Tasso in Music Project digital scores in the Humdrum format: musical settings of the poetry of Torquato Tasso (c 1470-1540)
https://www.tassomusic.org
5 stars 0 forks source link

Missing explicit accidental for Trm0047m #18

Open emilianoricciardi opened 7 years ago

emilianoricciardi commented 7 years ago

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

craigsapp commented 7 years ago

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 commented 7 years ago

OK

On Mon, Apr 3, 2017 at 4:03 PM, Craig Stuart Sapp notifications@github.com wrote:

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:

[image: screen shot 2017-04-03 at 12 54 16 pm] https://cloud.githubusercontent.com/assets/3487289/24629100/b7385606-186c-11e7-8827-308954ad500c.png

In the verovio rendering it is correct:

[image: screen shot 2017-04-03 at 12 55 17 pm] https://cloud.githubusercontent.com/assets/3487289/24629134/d3039666-186c-11e7-9464-b3aca6d7e9d1.png

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 http://muse2ps.ccarh.org converter from MuseData to PostScript.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TassoInMusicProject/tasso-scores/issues/18#issuecomment-291257170, or mute the thread https://github.com/notifications/unsubscribe-auth/AZZl9ybZoG1JtEPUmfL1qToEjjREEppJks5rsVB6gaJpZM4Mx7YZ .

craigsapp commented 7 years ago

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.