Difference between revisions of "MuseData"
| Line 1: | Line 1: | ||
<i>MuseData</i> is a dynamic environment for music encoding, printing, and archiving. It was conceived and has been developed since 1984 to the present by Walter B. Hewlett. <i>MuseData</i> seeks to support the creation, editing, and use of full scores and their by-products (scores, short-scores, parts; datasets for music analysis; and linkage with sound output). Its focus, originally limited to conventional music notation (1600-1860), has been extended selectively to support projects involving mensural and other early notations. | <i>MuseData</i> is a dynamic environment for music encoding, printing, and archiving. It was conceived and has been developed since 1984 to the present by Walter B. Hewlett. <i>MuseData</i> seeks to support the creation, editing, and use of full scores and their by-products (scores, short-scores, parts; datasets for music analysis; and linkage with sound output). Its focus, originally limited to conventional music notation (1600-1860), has been extended selectively to support projects involving mensural and other early notations. | ||
| − | + | The MuseData dynamic score-generation system | |
| − | + | <i>MuseData</i> is a <b>dynamic system</b>. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. <i>MuseData</i> has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past. | |
| + | The score-generation site [https://www.musedata.org musedata.org] supports <b>virtual online editing</b>. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full [[MuseData: file format]] file specification. | ||
| + | |||
| + | ==MuseData Encoded Repertories== | ||
The Center for Computer Assisted Research in the Humanities ([https://www.ccarh.org CCARH]), currently hosted by the Packard Humanities Institute and physically based at Stanford University, has used <i>MuseData</i> extensively in the encoding of classical repertories. The production of performing materials is undertaken selectively (see below). Currently, more than 1,100 works have been encoded to a common, documented format. | The Center for Computer Assisted Research in the Humanities ([https://www.ccarh.org CCARH]), currently hosted by the Packard Humanities Institute and physically based at Stanford University, has used <i>MuseData</i> extensively in the encoding of classical repertories. The production of performing materials is undertaken selectively (see below). Currently, more than 1,100 works have been encoded to a common, documented format. | ||
| + | |||
| + | |||
See http://www.musedata.org for access to the musical data. | See http://www.musedata.org for access to the musical data. | ||
Revision as of 23:17, 25 August 2024
MuseData is a dynamic environment for music encoding, printing, and archiving. It was conceived and has been developed since 1984 to the present by Walter B. Hewlett. MuseData seeks to support the creation, editing, and use of full scores and their by-products (scores, short-scores, parts; datasets for music analysis; and linkage with sound output). Its focus, originally limited to conventional music notation (1600-1860), has been extended selectively to support projects involving mensural and other early notations.
The MuseData dynamic score-generation system
MuseData is a dynamic system. Its implementation is the work of Craig Sapp. In traditional print-oriented scenarios, musical scores can be updated only with difficulty. The data ifself can be modified to capture new information, changing interpretations, and new arrangements. MuseData has maintained backward compatibility since its inception. This combination sets its overall operation apart from situations in which continuous software development orphans much data encoded in the past.
The score-generation site musedata.org supports virtual online editing. It is largely used to make PDFs that identify editors and date of printing in the footer. Users wishing to alter that data for personal use should consult the full MuseData: file format file specification.
MuseData Encoded Repertories
The Center for Computer Assisted Research in the Humanities (CCARH), currently hosted by the Packard Humanities Institute and physically based at Stanford University, has used MuseData extensively in the encoding of classical repertories. The production of performing materials is undertaken selectively (see below). Currently, more than 1,100 works have been encoded to a common, documented format.
See http://www.musedata.org for access to the musical data.
See pages such as Corelli, Beethoven, Handel and Vivaldi for musically-oriented access to the data.
Older scores can be found on http://scores.ccarh.org