Closed craigsapp closed 2 years ago
The cantus part starting is weird:
The opening looks like it is colored, but the transcription is not (and I don't know why/if it should be colored).
Also note a special fliter called kernview
which is used to view selected parts, but still allow graphical editing in the SVG image (using extract -k 3
for the same score will not allow graphical editing since the data is filtered before it is rendered in verovio, causing the xml:ids to be messed up compared to the original digital score in the text editor).
The coloration seems to be an error, because beside alignment with the other parts, there are two quarter notes (semi-minims) in the third measure that are not colored (according to the transcription), but they look like the previous "colored minims".
Zooming in on the notes in the Cantus part, it looks like they were filled in by hand with ink:
So maybe someone's kid got ahold of the book and was trying to fill in all of the notes....
It would be useful to encode these three links into the digital score as well (for much faster access to the musical content that the digital score is based on)
Okay, I added them to the source. Sadly there does not seem to be a (localization neutral) permalink for the direct links to the pages. But without the locale it does seem to redirect to your language (https://www.digitale-sammlungen.de/view/bsb00075346?page=11). Since I'm not sure if this will work permanently I just stick to the german link for my project.
The cantus part starting is weird
Yes I also noticed this. But I think I encoded it correctly since otherwise it does not fit to the other voices. "Modern” editions on IMSLP (https://imslp.org/wiki/Teutsche_Psalmen_(Lassus,_Orlande_de)) seem to transcribe it the same way. So as you said I also think the coloration seems to be an error.
Is there a way to express this difference in humdrum? Semantically or maybe with a note.
So maybe someone's kid got ahold of the book and was trying to fill in all of the notes....
That's a nice theory :-) .
There are multiple digital representation of this pice on digitale-sammlungen.de. I just checked another one and it seems to be correct there: https://www.digitale-sammlungen.de/de/view/bsb00072990?page=11. I will link to this version as soon as I find the other voices. I just found Cantus for now with the other digital representation.
Is there a way to express this difference in humdrum? Semantically or maybe with a note.
The best would be with a note. One possibility would be using !!!ONB:
:
!!!ONB: Starting notes of the Cantus part have been filled in by hand with an ink pen.
I use this form the most, since they are easy to locate later with the command-line command:
grep ONB *.krn
Or a non-formatted comment (which I would place above the first note that is filled in):
!! Starting notes of the Cantus part have been filed in by hand with an ink pen.
There is also a local comment method (other spines would have single !
):
! notes filled in with ink pen in source
In any case, there is not much semantic information in this observation since it is clearly not from the original print nor a correction afterwards but rather doodling.
I have implemented a "sic" system for Humdrum files, which is a special form of correction, but in this case it would not be useful:
Would something like this be a valid syntax?
!!!YOR: https://mdz-nbn-resolving.de/details:bsb00075346
!!!YOR-alt: https://mdz-nbn-resolving.de/details:bsb00075346
!!!YOO: München, Bayerische Staatsbibliothek
!!!URL-scan: https://www.digitale-sammlungen.de/de/view/bsb00075346?page=11 Cantus
!!!URL-scan: https://www.digitale-sammlungen.de/de/view/bsb00075346?page=71 Tenor
!!!URL-scan: https://www.digitale-sammlungen.de/de/view/bsb00075346?page=127 Bassus
!!!URL-scan-alt: https://www.digitale-sammlungen.de/de/view/bsb00072990?page=11 Cantus
!!!IIIF: https://api.digitale-sammlungen.de/iiif/presentation/v2/bsb00075346/manifest
In general, how free am I to add my own extensions to existing reference records? E.g. something like !!!URL-scan-alt
, !!!YOR-alt
, !!!OTL-incipit
, !!!voices-OPR
or similar.
Yes, that looks good.
The general rule is that official reference records use capital letters, numbers and sometimes #
(and maybe _
). For non-standard or user-defined records, lower case letters should be used (preferably no spaces in reference record keys or other non-letter characters).
URL
is a semi-standard (it is not in the official list at https://www.humdrum.org/reference-records/index.html), but it makes sense to treat it as an official one. I am putting IIIF in capitals although it is not in the official list (and it has four letters, while all standard ones have three) — and an "I" often looks similar to a "!", so maybe !!!iiif:
might have been a better choice... This record will be important for cross-application support, so that is probably why I decided to make it capital (so currently semi-official since I have not added it to the official list).
A dash following the reference record means a "subcategorization":
There is no official list of subcategorizations, so you can make up your own (but if you make up your own, then they should be in lower case).
!!!URL-scan-alt
Adding multiple categorizations (or subcategorizations as in this case) is no problem.
Regarding:
!!!URL-scan: https://www.digitale-sammlungen.de/de/view/bsb00075346?page=11 Cantus
!!!URL-scan-alt: https://www.digitale-sammlungen.de/de/view/bsb00072990?page=11 Cantus
I don't think that alt
is too necessary here and you could put the quailfication in the optional text description after the link:
!!!URL-scan: https://www.digitale-sammlungen.de/de/view/bsb00075346?page=11 Cantus
!!!URL-scan: https://www.digitale-sammlungen.de/de/view/bsb00072990?page=11 Cantus (without doodles)
One reason is that I don't think that VHV will show a link if there is the extra -alt
added? In any case I would suggest making the alt
link the primary URL-scan
entry, since that is the one without the filled in notes. And otherwise, this is the same print (in theory they should be identical, although there could be corrections in one if they are from different printings).
A more sophisticated sub categorization would be useful if you have multiple source editions used to create the Humdrum digital score. In that case there is usually a "principle" source that most of the digital score is based on, with occasionally corrections from other sources.
Something like this would be useful in such situations
!!!URL-scan-ms1a: https://www.digitale-sammlungen.de/de/view/bsb00075346?page=11 Cantus (ms1a)
!!!URL-scan-ms1b: https://www.digitale-sammlungen.de/de/view/bsb00072990?page=11 Cantus (ms1b)
where ms1a
is a tag for some manuscript (or print) called ms1a
(or 1a
) and the ms1b
is for manuscript ms1b
(or 1b
).
The link:
links to the URL:
which in turn has a thumbnail for the cover of the scan:
clicking brings you to the full scan of the front cover:
https://www.digitale-sammlungen.de/en/view/bsb00075346?page=,1
And then here are the pages in the scan for Beatus vir (not conveniently adjacent since this is three different part books):
https://www.digitale-sammlungen.de/en/view/bsb00075346?page=11 https://www.digitale-sammlungen.de/en/view/bsb00075346?page=71 https://www.digitale-sammlungen.de/en/view/bsb00075346?page=127
It would be useful to encode these three links into the digital score as well (for much faster access to the musical content that the digital score is based on):
After the URL in this reference record, there is an optional title for the URL, such as "Cantus" for the first scan link. VHV detects such records, and creates a list of links on the left side of the first toolbar for them:
If you mouse over one of the scan icons, the title of the URL will be displayed as a tooltip:
And clicking on the scan icon will open the webpage for the scan (in this case directly to the Cantus music):