Josquin Humdrum encoding standards - Revision history

Craig: /* Conversion Notes */

2013-07-16T22:50:41Z

Conversion Notes

← Older revision		Revision as of 22:50, 16 July 2013
Line 342:		Line 342:
	# Data files are received in three formats (1) MusicXML file, (2) PDF file showing intended graphical notation of music, (3) original data file from music editor used to generate MusicXML file (such as a SCORE/Finale .mus file or a Sibelius .sib file).		# Data files are received in three formats (1) MusicXML file, (2) PDF file showing intended graphical notation of music, (3) original data file from music editor used to generate MusicXML file (such as a SCORE/Finale .mus file or a Sibelius .sib file).
	# MusicXML data is converted into Humdrum with the [http://extras.humdrum.org/man/xml2hum xml2hum] program		# MusicXML data is converted into Humdrum with the [http://extras.humdrum.org/man/xml2hum xml2hum] program
	# The raw conversion is processed with the [http://museinfo.sapp.org/examples/humdrum/~~jrp~~.cpp ~~jrp~~.cpp] program		# The raw conversion is processed with the [http://museinfo.sapp.org/examples/humdrum/jrpize.cpp jrpize.cpp] program
	# The previous two steps are typically handled automatically by [[Josquin MusicXML to Humdrum conversion script \| this PERL script]] which also inserts reference records.		# The previous two steps are typically handled automatically by [[Josquin MusicXML to Humdrum conversion script \| this PERL script]] which also inserts reference records.
	# The Humdrum file is manually checked for errors in the automatic translation.		# The Humdrum file is manually checked for errors in the automatic translation.

Craig: /* Conversion Notes */

2013-07-16T22:48:43Z

Conversion Notes

← Older revision		Revision as of 22:48, 16 July 2013
Line 342:		Line 342:
	# Data files are received in three formats (1) MusicXML file, (2) PDF file showing intended graphical notation of music, (3) original data file from music editor used to generate MusicXML file (such as a SCORE/Finale .mus file or a Sibelius .sib file).		# Data files are received in three formats (1) MusicXML file, (2) PDF file showing intended graphical notation of music, (3) original data file from music editor used to generate MusicXML file (such as a SCORE/Finale .mus file or a Sibelius .sib file).
	# MusicXML data is converted into Humdrum with the [http://extras.humdrum.org/man/xml2hum xml2hum] program		# MusicXML data is converted into Humdrum with the [http://extras.humdrum.org/man/xml2hum xml2hum] program
	# The raw conversion is processed with the http://museinfo.sapp.org/examples/humdrum/jrp.cpp jrp.cpp] program		# The raw conversion is processed with the [http://museinfo.sapp.org/examples/humdrum/jrp.cpp jrp.cpp] program
	# The previous two steps are typically handled automatically by [[Josquin MusicXML to Humdrum conversion script \| this PERL script]] which also inserts reference records.		# The previous two steps are typically handled automatically by [[Josquin MusicXML to Humdrum conversion script \| this PERL script]] which also inserts reference records.
	# The Humdrum file is manually checked for errors in the automatic translation.		# The Humdrum file is manually checked for errors in the automatic translation.

Craig: /* Segmentation */

2013-07-16T22:48:26Z

Segmentation

← Older revision		Revision as of 22:48, 16 July 2013
Line 333:		Line 333:

	== Segmentation ==		== Segmentation ==




			== Conversion Notes ==

			Outline of the conversion process from MusicXML into Humdrum:
			# Data files are received in three formats (1) MusicXML file, (2) PDF file showing intended graphical notation of music, (3) original data file from music editor used to generate MusicXML file (such as a SCORE/Finale .mus file or a Sibelius .sib file).
			# MusicXML data is converted into Humdrum with the [http://extras.humdrum.org/man/xml2hum xml2hum] program
			# The raw conversion is processed with the http://museinfo.sapp.org/examples/humdrum/jrp.cpp jrp.cpp] program
			# The previous two steps are typically handled automatically by [[Josquin MusicXML to Humdrum conversion script \| this PERL script]] which also inserts reference records.
			# The Humdrum file is manually checked for errors in the automatic translation.
			# The Humdrum file is converted to graphical music notation with [[muse2ps]] and manually checked for expected notation rendering.
			# A !!muse2ps: record is added to indicate the formatting information needed to produce decent automatic formatting of the music (spacing between staves, density of the music, title, composer information at start of music).
			# The Humdrum file is stored in the database (in the kern directory for a particular composer or collection
			# The work-info page is displayed. This automatically generates an incipit image. If the incipit is too short or too long, an !!!incipit: direction is added, the previous incipit is deleted and the work-info page is reloaded.
			# The entry for the work in the main work list is checked to make sure it has the correct composer, genre and voice information. For Josquin compositions, the attribution-level is checked (displayed as a color code in the work list).

Craig: /* Other Header Information */

2013-07-16T22:28:48Z

Other Header Information

@@ Line 96: / Line 96: @@
 Example list of genres and subgenres which are typically found in the data:
@@ Line 123: / Line 143: @@
     !!!AGN:	Fragment; Motet
+SCT reference records are used to indicate "scholarly catalog numbers" in Humdrum, such as KV numbers for Mozart, or Hoboken numbers for Haydn.  For the music of Josquin des Prez, the volume number and work enumeration within the volume are used in reference to the New Josquin Edition.  For other composers, the JRP catalog number is given within the SCT record.  SCA records contain the unabbreviated scholarly catalog number (useful for cases where the abbreviation would not be clear outside of a specialized field).
     !!!SCT: NJE 3.1
@@ Line 130: / Line 150: @@
     !!!SCA: New Josquin Edition 3.1
 <tt>SCA</tt> is an unabbreviated scholarly catalog number.
     !!!voices: 4

Craig: /* Header reference records */

2013-07-16T21:54:24Z

Header reference records

@@ Line 43: / Line 43: @@
-==== Work Information ====
+==== Title Information ====
-Work-related reference records in Humdrum typically start with the letter "O" which stands for <i>Opus</i>.
+Work-related reference records in Humdrum typically start with the letter "O" which stands for <i>Opus</i>.   Here are the work-related reference records used in JRP Humdrum scores:
     !!!OPR: Missa Ave maris stella
@@ Line 66: / Line 87: @@
     !!!OTL@ENG: Holy Mother! pierce me through
 When a reference record is only followed by a single at sign (@), the language code which follows is a language into which the reference value has been translated into.  In this case the title is translated into English, and also it implies that English was not the original language for the reference record.
     !!!AGN: Mass; Kyrie
 <tt>AGN</tt> (''analytic genre'') is used to encode the genre within the data.  This is useful for selecting or grouping works by genre for analysis.  Multiple analysis genres are separated by semicolons, such as in this case where the work is a part of a mass, but is more specifically a kyrie.
     !!!SCT: NJE 3.1

Craig: /* Work Information */

2013-07-16T21:28:57Z

Work Information

← Older revision		Revision as of 21:28, 16 July 2013
Line 44:		Line 44:

	==== Work Information ====		==== Work Information ====

			Work-related reference records in Humdrum typically start with the letter "O" which stands for <i>Opus</i>.

	!!!OPR: Missa Ave maris stella		!!!OPR: Missa Ave maris stella

Craig: /* Reference records */

2013-07-16T21:27:55Z

Reference records

← Older revision		Revision as of 21:27, 16 July 2013
Line 3:		Line 3:
	== Reference records ==		== Reference records ==

	Reference records are lines which start with three exclamation marks followed by a reference key, then a colon, and then the value for the reference key.		Reference records are lines in Humdrum data which start with three exclamation marks followed by a reference key, then a colon, and then the value for the reference key. The standard Humdrum reference record keys are listed on [http://www.humdrum.org/Humdrum/guide.append1.html Appendix 1 of the Humdrum Users' Guide]

	=== Header reference records ===		=== Header reference records ===
Line 29:		Line 29:
	A CDT (Copmoser's dates record) should Immediately following each COM/COA record. If the COM/COA record has an optional number attached to it, the CDT tag should optionally have the same number.		A CDT (Copmoser's dates record) should Immediately following each COM/COA record. If the COM/COA record has an optional number attached to it, the CDT tag should optionally have the same number.

			For works composed or attributed to Josquin des Prez, there is an comment in the file trailer called "!!attribution-level:" which categorizes the attribution quality for the work (see the reference record trailer section below for more details). Other composers in the JRP database do not posses such an attribution comment.

	Example composer-related reference records:		Example composer-related reference records:

Craig: /* Header reference records */

2013-07-16T21:20:52Z

Header reference records

@@ Line 7: / Line 7: @@
 === Header reference records ===
-Reference records which occur before the start of the data:
+Reference records which occur before the start of the data.
     !!!COM: Josquin des Prez
@@ Line 17: / Line 40: @@
     !!!CDT: ~1450-1521/08/27
 <tt>CDT</tt> is the Composer's birth and death dates.  Josquin was born in approximately 1450 and died 27 August 1521.  Note all dates in Humdrum reference records are in the form year/month/day[/hour:minute:second].  A tilde character before a number such as the year means ''circa'', or an approximate date.
     !!!OPR: Missa Ave maris stella
@@ Line 49: / Line 75: @@
     !!!voices: 4
 <tt>voices</tt> is the number of voices in the work/section.  This value is usually the same as the number of spines (columns) in the Humdrum data, but is occasionally different, such as in the case where one of the original parts has been lost.
 === Trailer reference records ===

Craig: /* Metrical considerations */

2011-10-07T01:25:23Z

Metrical considerations

← Older revision		Revision as of 01:25, 7 October 2011
Line 210:		Line 210:

	<!-- Table data generated 20111003 with: grep -h "^\met" .krn \| sed 's/\t/\n/g' -->		<!-- Table data generated 20111003 with: grep -h "^\met" .krn \| sed 's/\t/\n/g' -->

			=== primary mensuration ===

			When different parts have different mensurations at the same time, a global comment can be added at that point in the score to indicate the primary mensuration for performance tempo determination. For example, if three out of for parts are in Cut-C and one is in C, then the global record starting with "!!primary-mensuration:" and followed by the main mensuration used to determine the tempo of the following music. For example:

			M2/1 M2/1 M2/1 M2/1
			met(C\|) met(C) met(C\|) met(C\|)
			!!primary-mensuration: met(C\|)

	== Segmentation ==		== Segmentation ==

Craig: /* Tempo interpretation */

2011-10-03T20:42:17Z

Tempo interpretation

@@ Line 108: / Line 108: @@
 == Augmentation and diminution ==
-== Tempo interpretation ==
+== Metrical considerations ==
 == Segmentation ==