User:LCantoni/Draft Revised Music Guidelines
NOTE: This is a DRAFT of revisions to the DP Music Guidelines. This is part of my personal user page, so please DO NOT EDIT THIS PAGE -- instead, post comments and suggestions in this forum thread, or send them via PM to LCantoni.
The following are guidelines for DP projects containing music notation for:
Portions of these Guidelines are included or cited in the DP Official Documentation. See the Music Guidelines for Proofreaders, the Content Providing FAQ, the Project Managing FAQ, and the Post-Processing FAQ.
Links to audio and other music-related files in an e-book containing music notation provide a very rich experience for the reader. Depending on what kinds of files are provided, readers can listen to the music, download notation source files to edit and use for their own purposes, or download and print sheet music to play on an instrument.
It is required that, at the very least, projects containing music notation have audio files to accompany them.
Why do this when the original books didn't have sound? Here's why: In the days before recordings and radio and other forms of sound transmission, there were far fewer ways for people to hear music other than by going to a concert, and many had few opportunities of doing even that. But most educated people had access to a piano or other musical instrument. Knowing this, authors and publishers put passages of music notation in their books so that readers could play it for themselves and enrich the experience of what they were reading.
You don't have to know music to handle a music project. DP's Music Team and Music Coordinator, currently LCantoni, are always ready to advise you and to transcribe music (i.e., turn music notation into audio and other files). And these Guidelines are designed to help you every step of the way.
Guidelines for Content Providers
Choosing a Project
Music-related books are always welcome at DP, but you should be aware that pure music projects, such as those consisting entirely of scores or sheet music, are not feasible for DP. They are not adaptable to the distributed proofreading model, mainly because there are so few DPers who can commit to transcribing large amounts of music.
Preparing the Images
Music notation has a lot of very tiny symbols that are very important (e.g., a dot after a note, lengthening its time value; a dot over a note, indicating that it should be played short). So, to ensure that these are visible, music images should be scanned at the highest, crispest resolution possible.
If you are cropping the music images, be sure not to crop them too closely. Very often, music symbols, text directions, and even lyrics appear outside the staff boundaries. Better to have too much than too little.
Guidelines for Project Managers
Planning the Project
When you're the PM for a new project containing music, the first thing you should do is go over the project and make a note of how much music notation is in it and what form it takes. In most projects, the music consists of snippets of notation to illustrate the text. In others, there might be complete musical pieces. And some projects may use musical symbols in the course of the text. This is all information you'll want to include when #Writing the Project Comments.
If the project has musical symbols, be sure to choose the Symbols Collection Character Suite when creating the project so that the proofreaders will have access to Unicode musical symbols. Note, however, that the project may also use symbols not in that collection; see #Music Symbols below for more information on handling those.
The next thing you should do is set up a plan for how you want the music to be handled by the proofers, formatters, and post-processor. The DP Music Coordinator and/or the DP Music Team can help you with your plan.
It's a good idea to get a music-capable PPer in advance, if possible, who can help you decide how the project should look (and sound), and who may even be able to transcribe the music before or during PP.
Failing that, try to get a volunteer to transcribe the music in advance, while the project is going through the rounds. A post in the Music Team forum should get reasonably quick results. The music files can then be added to the project so that they're safely stored and ready for the future post-processor.
In the final HTML e-book, the post-processor will use, at a minimum, the original image with a link to an audio file. Some PPers like to provide multiple audio formats (e.g., MP3 and MIDI); some also like to provide a MusicXML file so that the music notation can be downloaded and imported into any music notation software. See the discussion of #Music File Formats below. It's a good idea to work with the PPer and/or music transcriber to make these decisions in advance.
A Note about E-Pub and Mobi
Many e-reading devices that use the epub or mobi e-book format still don't support links to external files, which means that readers using such devices won't be able to hear, view, or download music-related files. But PMs and PPers should still include audio and other music-related files in their projects, at least to enhance the HTML version, and in the hope that someday, epub and mobi will catch up to HTML in providing a rich e-book experience with external resources.
Writing the Project Comments
Once you have a plan in place, your Project Comments should be very specific about what you expect from the proofers, formatters, and PPer. Again, getting a PPer on board beforehand will be very helpful in formulating clear instructions. The DP Music Team can also help you with this.
The Project Comments must be clear on how to handle these issues:
- How much music is there?
- Are the music illustrations snippets, or full pieces, or a combination?
- Does the music have lyrics, titles, composer credits, or other text elements that should be proofed?
- Has the author put music illustrations in the middle of a sentence or paragraph to illustrate a point?
- Are there music symbols (flats, sharps, and so forth) in the text?
Do not simply refer to the Music Guidelines - you must give specific guidance to proofers, formatters, and the PPer based on what is in your project.
Writing Instructions for Proofers
Music images are treated the same way as illustrations, so the proofers won't be involved in formatting the markup. But if the music illustrations have text elements, you'll want them proofed.
The proofers should be proofing only these portions of music notation:
- composer, arranger, lyricist, or other credits
- copyright information or other text information about the piece
- captions such as "Fig. 1" or "(2)" or the like
Purely musical directions, such as tempo markings (e.g. Allegro), instrument designations (e.g. Voice, Piano), and dynamics (e.g. crescendo) should be excluded from proofing.
Specify in the Project Comments what the proofers can expect to find and how they should be proofed.
Lyrics present special issues. In music notation, syllables are hyphenated to match the notes, and dashes or long ellipses are often used to indicate a held note. Proofers frequently ask questions on how to handle these, so it's important to be clear about what you (and/or the PPer) want.
There are two ways of proofing lyrics:
- Match the scan. All hyphens, dashes, and ellipses are rendered as they appear in the original. The main advantage of this method is that it's the easiest for the proofers to follow. The disadvantages are that the syllable divisions won't make sense in the plaintext version without a music illustration; and hyphenation is often erratic or even wrong in the original, because it's often dependent on how much room the printer had. The default instruction for proofers - essentially, to match the scan except for ellipses - is in the official Music Guidelines for Proofreaders.
- Ignore hyphens, dashes, and ellipses. For example, if the lyrics in the original read, "Ma-ry had a lit-tle lamb whose fleece was white as snow......" they are proofed as "Mary had a little lamb whose fleece was white as snow." The main advantage of this method is that it's much easier for the reader to read.
Consult with the PPer, if one is on board, as to which is preferred, and be clear about it in the Project Comments.
Music symbols in the text will require special proofing, as they'll need to be represented in the plaintext version, and the PPer will need to be able to find them for HTML treatment.
The Symbols Collection Character Suite contains the following Unicode symbols that the proofers can use and that will appear properly in the plaintext version:
- Sharp ♯
- Flat ♭
- Natural ♮
- Quarter note (crotchet) ♩
- Eighth note (quaver) ♪
Other music symbols in the text should be proofed with the name in brackets if the proofer knows what it is, e.g. [**crescendo], or simply with [**music symbol], so the PPer can find it.
Time signatures expressed in numbers, like , should be rendered as fractions (e.g., 3/4). [**ADD: symbols for piano & forte can be italicized p & f, etc.]
Writing Instructions for Formatters
The formatters will be concerned with three issues:
- Adding [Music] markup.
- Marking lyrics as poetry, where appropriate.
- Determining whether the music illustration should remain in its original place, or be moved to the nearest paragraph break.
The [Music] Tag
Be sure to specify in the Project Comments for the formatters that music notation must be marked as [Music], not [Illustration]. This makes the music easier to find so that the PPer knows where to add links to the music files.
Text elements in the music (title, composer, lyrics, copyright, etc.) that aren't musical directions should be included within the [Music] tag. For example:
[Music: MAKING BUTTER. <sc>Emilie Poulsson.</sc> <sc>C.C. Roeske.</sc> /* 1. Skim, skim, skim, With the skim-mer bright; Take the rich and yel-low cream, Leave the milk so white. */ ]
For music continued on or from another page, formatters should use the same convention used for continued footnotes, i.e. *[Music] or [Music]*.
It's important to specify in the Project Comments how lyrics should be formatted. In general, multiple-line lyrics should be marked up as poetry, using /* tags as in the example above. Single-line lyrics will not need /* markup.
The easiest course is to the formatters to match the scan, so that lyrics in each musical staff are on one line, as can be seen in the "Making Butter" example above.
If the music image has multiple verses of lyrics, matching the scan will look like this:
/* 1. Lauriett! Ah! my 2. Fare thee well! Ah, my dearest, I will often think of thee, When dearest, Wilt thou often think of me, When I'm */
But you can also ask the formatters to separate the verses:
/* 1. Lauriett! Ah! my dearest, I will often think of thee, When 2. Fare thee well! Ah, my dearest, Wilt thou often think of me, When I'm */
Be sure to be clear in the Project Comments as to which approach you (or the PPer) prefer.
Music in the Middle of a Paragraph
Sometimes music illustrations, like regular illustrations, are moved to the nearest paragraph break. But the Project Comments should be clear that music illustrations that are used in the middle of a sentence or paragraph to illustrate a point (if they exist in your project) should NOT be moved. For example:
101. Other varieties of measure sometimes found are 9/8 and 12/8, but these are practically always taken as three-beat and four-beat measures respectively, being equivalent to these if each group of three tones is thought of as a triplet. [Music] is identical in effect with [Music]
Writing Instructions for Post-Processors
Even if you've engaged a PPer in advance, you should lay out your PPing requirements in the Project Comments, in case the project is later reassigned to another PPer. Many PMs simply ask that at least audio files be included, and leave the rest up to the PPer. If you do have further requirements for the final product, include them in the Project Comments. Most importantly, you should specify all the file formats you want included in the e-book, such as MP3 and MusicXML (see #Music File Formats).
Do not, however, specify that you want music transcribed using a particular notation program. Specifying a particular program will reduce considerably the already-small pool of available music transcribers.
For the music images, always use the original images. Not only does that stay true to the original book, it also avoids the PPer and music transcriber having to worry unnecessarily about recreating the appearance of the music.
That said, if the original images are hard to read due to poor quality, or use an archaic notation style like medieval neumes, you might like to have clean and/or modern notation images to include with the project in addition to the original images. If that's what you want, be sure to say so in the Project Comments. But don't expect the Music Transcriber to re-create the appearance of archaic notation.
PDF files can also be a useful addition where the music is a complete piece, and you'd like the reader to be able to view or print out a piece as sheet music.
Remember, the more you require, the more work for the PPer and the Music Transcriber, and the longer it will take for the project to get posted.
Adding Music to the Project Files
If you've asked for music to be transcribed in advance, it's important to have a safe repository for the music files. Keeping them on someone's home computer is far from optimal; people leave DP, their hard drives die, things get accidentally erased. And while your DPScans folder is one way to store these files, there's still the possibility of accidental deletion.
To solve this problem, you should ask Db-req to add the music files to the project's extra files. The PPer will then be able to download the music files along with all the other project files.
Here's how to do it:
- Make sure the music file filenames are all lower case.
- Zip up the music files, naming the zip file with the project ID number and the word "music", e.g., projectIDxxxx_music.zip. (Copy and paste the project ID number from the project page to avoid typos.)
- Put the zip file in your DPScans folder. If you don't have one, upload the zip file to online external storage, such as your personal webspace or Dropbox, so that a db-req Squirrel can download it. Do NOT send it as an email attachment to db-req!
- Send an e-mail to db-req asking that the music files be added to the project's extra files. Be sure to include your DP username, the project name and ID number, and the location of the zip file, e.g. DPScans, Dropbox, etc. For Dropbox or other external locations, be sure to provide the direct link for downloading the zip file.
- If you're the PM, put a note in the Project Comments telling the future PPer that the music files are in the project's extra files. If you're not the PM, mention in your email to db-req that the PCs should be updated. You can also post in the Project Discussion that you've asked db-req to add the files.
- Do not delete the zip file until you've confirmed that the music files have been added to the project.
Guidelines for Proofers
The primary directive for proofers, as for any project, is to follow the Project Comments and read the Project Discussion. The PM will, ideally, have given specific instructions on how to proof any text elements in the music.
In the absence of specific instructions, proofers should do the following when encountering music in a project:
- Treat music illustrations as illustrations; that is, leave the markup to the formatters.
- Proof text elements such as the title, composer, and any lyrics.
- Lyrics are often hyphenated to indicate that the syllables are to be sung on different notes; leave the hyphens in, unless otherwise instructed.
- You may also encounter ellipses or long dashes in lyrics, indicating that a single syllable is to be sung on more than one note (a "melisma"). These can be ignored.
- Ignore text elements that are actually part of the music, such as tempo and dynamic markings (e.g., Allegro, rit., cresc., p, f, dim., etc.). If you're not sure, leave it in, with a [**note].
- Mark music symbols in the text as [**music symbol], or, if you know the name of the symbol, include it, e.g., [**crescendo].
- Ask in the Project Discussion, or leave a [**note], for anything you're not sure of.
- See Music Guidelines re: Writing Instructions for Proofers for more information.
Guidelines for Formatters
The primary directive for formatters, as it is for proofers, is to follow the Project Comments and read the Project Discussion.
If the PM has not given specific instructions on formatting music, formatters should follow these basic guidelines:
- Mark music illustrations as [Music].
- Include any text elements (title, composer, lyrics) within the [Music] tag, e.g., [Music: Liebestraum].
- Format any lyrics as poetry, using /* markup, and match the original line breaks unless otherwise instructed. Multiple verses (usually numbered 1, 2, etc.) should be separated.
- If the music appears in the middle of a sentence or paragraph as part of the text, leave it there. Standalone music illustrations can be moved to the nearest paragraph break.
- Do not add music notation code, such as Lilypond. The music may already have been done, or is planned to be done in a different manner. If you'd like to transcribe the music — and your help would be most welcome! — contact the PM, the PPer, the DP Music Coordinator (LCantoni), or the DP Music Team, before you do anything.
- Ask in the Project Discussion, or leave a [**note], for anything you're not sure of.
- See Writing Instructions for Formatters for more information.
Guidelines for Post-Processors
Most of the considerations discussed above in the Guidelines for Project Managers apply with equal force to PPers, especially where the PM has deferred to the PPer's preferences. Please review the Guidelines for Project Managers before you start the PP process.
It's also a good idea to browse through all the page images to make sure you know where all the music images are, including music symbols in the text, before you start PPing.
The proofers should have used the music symbols character picker for the few available Unicode music symbols. As for symbols not in the picker, while you can use a generic [musical symbol] tag, it'll be a much richer experience for the reader if you give a more specific description, such as [crescendo] (which the proofers may have already provided). The Dolmetsch Chart of Musical Symbols is a handy resource, or, if you're still not sure, post in the Music Team forum.
For accessibility purposes in the HTML, be sure that the text elements in the music image (title, composer, lyrics, etc.) are laid out in the main text of the HTML. See Our Old Nursery Rhymes for an example.
Lyrics can be placed either directly below the music image, or in a separate section at the end of your document (in which case be sure to place a clear "go to lyrics" link from the area of the original image).
Use the original music images. Nothing represents the original better than the original. If the Music Transcriber has prepared an alternative image file for you, you can use it in addition to, but not instead of, the original image.
Don't crop music images too closely; keep a sharp eye out for music and text elements (such as lyrics) that are outside the staff margins.
Make sure the image resolution and size are sufficient for the reader to clearly see all of the music, including the little dots and so forth. You can display a small image and link to a larger one if necessary. Don't make the images too big, or they'll overwhelm the page. An image width of no more than 600px (where the music extends the full width of a page in the original) usually does the trick.
A simple border around the music image can be attractive. See Our Old Nursery Rhymes for an example.
When preparing the HTML version of the e-book, create a separate "music" folder containing the music files you want to include.
Create visible links to the audio files near the music notation image. You may also want to link to MusicXML or other files. Explain these links in a Transcriber's Note at the beginning of the HTML file. See Our Old Nursery Rhymes for an example of how this can be done.
Include in a Transcriber's Note that the music files are the music transcriber's interpretation of the printed notation and are placed in public domain.
As noted above, at the time of this writing, music file links will not work in mobile e-book formats like epub or Kindle/mobi. You should note this in a Transcriber's Note for users who are reading the e-book in one of these formats.
Music Symbols in HTML
You can use in-line illustrations taken from the page images for other symbols. See Music Notation and Terminology for an example.
Finding a Music Transcriber
If you need volunteers to transcribe the music for you, post in the Music Team forum. And please be sure to ask the Music Transcriber whether and how he or she should be listed in the credit line, e.g., "Music transcribed by [real name or DP name]."
Guidelines for Music Transcribers
Note: Although you need not be a professional musician to transcribe music at DP, these guidelines assume that you can read music notation, at least at an elementary level.
Before you transcribe music for a DP project:
- Look over the music and make sure that your music notation software is capable of producing at least a midi or mp3 file. If you're not sure about something, post in the Music Team forum, with a link to the music page.
- Check whether the music continues on the following page(s). A single piece of music spanning several pages has to be transcribed as one piece, so that you can produce a single audio file.
- Review the text pages surrounding the music for additional clues as to how it should be handled (tempo, instruments, etc.), if this information is not apparent from the music itself.
- Use online resources to help determine how the music is supposed to sound, if it's not already familiar to you. For example, if the music is by a classical composer whose works are in the public domain, the IMSLP/Petrucci Music Library has a huge selection of free scores in PDF format, which you can use to double-check possible printer errors in the project, determine the correct tempo, etc. YouTube is also a great resource for actual performances of just about any kind of music.
- Don't be shy about asking for credit. You worked hard on the music and deserve kudos for it. Let the PM or PPer you're working with know how you want to be listed in the project credits (e.g., with your real name or your DP name), or, on the other hand, that you'd prefer not to be credited at all.
- Please don't take it upon yourself to transcribe music for a project without checking with the PM, the PPer, or the DP Music Team first. It may well be that the music is already being, or has already been, transcribed. You don't want to duplicate efforts.
When you're asked to transcribe music for a project, you must at least provide a MIDI file. Ideally, you should provide an MP3 file and a MusicXML file, if your software is capable of producing them.
Transcribe only what you see in the notation. Don't re-orchestrate or re-arrange it. For example, if it's written for piano, use a piano sound. If it's written for voice only, use a vocal sound. Just as we don't edit the text of the books we work on, we should not be editing the music. That said, you can make two kinds of alterations to the original:
- You can correct obvious printer errors and note them in a transcriber's note.
- Where the original doesn't indicate instrument, tempo, or dynamics, you can use your judgment or, if it's a well-known piece, consult online sources to add them as needed, and note what you did in a transcriber's note.
By creating and submitting music files for a DP project, you are agreeing that the files are being placed in the public domain, and there will be a notice to that effect in the e-book. If you can't agree to this, don't work on the project.
Handling Printer Errors
Just as with text, there can be printer errors in music. Unlike with text, however, it may not be possible to just leave the error in place - the audio file may sound terrible if you don't correct the error.
First, however, make sure it's an error. Sometimes dissonances are deliberate. Sometimes a bar deliberately contains more fewer beats than the key signature indicates (as in cadenzas, or in partial or pickup bars). If you're not sure, post in the Music Team forum, with a link to the music page.
As you work, keep a running list of printer errors and embody them in a transcriber's note that the PPer can include in the project. Describe exactly where the error is (giving system, bar, and beat numbers), why it's an error, and what (if anything) you did to correct it.
The transcriber's note can be in a separate text file, or you can add it to the MusicXML file for the particular piece.
Because we work with older books at DP, you'll frequently come across archaic music notation symbols, such as old-style clefs, rests, and time signatures. If you're not sure what a symbol stands for, check the Dolmetsch Chart of Musical Symbols, or post in the Music Team forum.
Depending on your notation software, you may not be able to reproduce these symbols exactly as they appear in the original. In cases where you're creating only an audio file, that doesn't matter, as long as you can accurately reproduce the intended sound in modern notation.
If, however, you've been asked to produce a MusicXML or image file, you should note in a Transcriber's Note that your software cannot reproduce the symbol, and that you've used a modern equivalent instead.
Medieval Notation (Neumes)
You may also come across medieval music notation, also known (in its various forms) as neumes, Gregorian chant, or mensural notation. Here's an example:
In most instances, in order to create an audio file from medieval notation, you'll have to enter modern notes in your notation program. Note that, because medieval transcribers often assumed familiarity with note durations based on custom, the durations may have to be guessed. Here's how the example above would look in modern notation, with a Transcriber's Note regarding note durations:
If you can't read medieval notation, post in the Music Team forum to find someone to help you.
Note: Some handwritten medieval notation may be too unclear to decipher accurately, or may require expertise beyond our volunteers' capability. In that case, it may not be possible to create an audio file. If the tune is well-known, however, an Internet search may come up with a modern image or a sound file to help you decipher the notation.
In the Baroque period, figured bass was a shorthand way of representing accompaniment in the bass staff, by placing just one note in the staff, with one or more numbers underneath it representing the other notes in a chord or figure. Here's an example:
As with medieval notation, there is limited, if any, support for playable figured bass in most notation programs. If your software doesn't support it, the solution is to create the audio file by entering the full accompaniment into your notation software. Here's an example of figured bass in modern notation (note the use of multiple voices):
If you need help interpreting (the technical term is "realizing") figured bass, post in the Music Team forum.
Music File Formats
Below is a review of some of the most common audio/visual formats for music in DP projects. All of them are accepted at Project Gutenberg as of this writing. [**ADD note about not using proprietary file formats like mscz from MuseScore, musx from Finale, etc.]
The high-quality sound of MP3 (.mp3) files makes them ideal, especially where the music is more complex (e.g., orchestral music), and a more realistic and reliable sound is desirable. MP3 files are WYHIWYG - what you hear is what you get. Unlike with MIDI, the sound of an MP3 file is not dependent on the particular sound fonts a listener might have installed - it will sound the same on any device.
MP3 files are significantly larger than MIDI files, but significantly smaller than WAV files with no loss of quality.
See Johann Sebastian Bach: The Organist and His Works for the Organ for an example of the use of MP3s in a PG e-text.
MIDI files (.midi or .mid) have a very small file size. They used to be the standard for sharing audio, but no longer. The current popularity of MP3 and the increased bandwidth of most people's Internet connections means that MIDI is no longer ideal.
While MIDI is capable of reproducing a wide range of instrumental sounds, the quality of those sounds will depend entirely on the individual user's sound card and sound fonts. This is because a MIDI file is not really an audio recording; it's actually a set of digital commands telling a computer what sounds to play and how. In short, unlike with MP3 and other audio file formats, what you hear when you play a MIDI file is not necessarily what someone else will hear.
There is nothing wrong with providing MIDI in a project, especially if that's the only format a music transcriber can provide with his or her particular music software, but you should be aware of this limitation.
MIDI files can be imported into a number of music notation programs in order to create an editable score, but the user will have to do significant editing and add in all the text elements. #MusicXML is far better for this purpose.
Note also that many current browsers won't automatically play MIDI files. The user may have to adjust some browser settings, install a plugin, or download the file to play in an external media player.
See Navaho Legends for an example of a music project with both MIDI and MP3 files.
WAV (.wav) audio files have high quality sound, much like MP3, but with a very large file size that make them much less practical for use with e-books. MP3 is therefore preferable for e-books.
Note: Some music notation programs generate high-quality audio files only in .wav format. Use audio-conversion software, such as the free audio editor Audacity, to convert WAV files into MP3 files before including them in a project.
MusicXML (.mxl, formerly .xml) is now the primary Internet standard for sharing music notation code. It is readable and/or writable by over hundreds of music programs, enabling music notation to be widely shared and making it ideal for PG e-books. It means that just about anyone can download the notation to their preferred software to correct any errors in the music or use the music for whatever purpose they wish.
A MusicXML file contains nearly all the musical and text elements in a music piece. The code can be viewed in any text editor and most browsers, and there are even plug-ins allowing browsers to play/display MusicXML files as music.
While MusicXML import/export is generally very good, some elements may not be automatically generated, so the user who downloads a MusicXML file to his/her preferred music software is likely to have to do some editing.
See Johann Sebastian Bach: The Organist and His Works for the Organ for an example of the use of MusicXML in a PG e-text.
PDF files (.pdf) can be created with many music notation programs. They're most useful where the book contains complete music pieces, so that, if desired, they can be used as sheet music for the reader to print out. See Indian Story and Song for an example of a project with PDF files created from Finale music notation software.
The original music images can also be combined into a PDF file for use as sheet music. This can be useful where there are many pages of music, and the PPer wants to avoid long image-loading delays in the HTML. In Music and Some Highly Musical People, for example, there were 149 pages of music. The PPer opted to display in the HTML just the first page of each piece, with a link to a PDF containing the original images of the full piece.
Music Notation Software
If you're an old hand at transcribing music on a computer, you already have your favorite notation software. If you want to explore, there's a comparison of many popular ones here.
At a bare minimum, the notation software you use for DP should be able to produce a MIDI file. Ideally, however, it should also be able to produce high-quality audio (mp3 or wav) and MusicXML.
Free Notation Programs
A free notation program popular among DP music transcribers is MuseScore. It's a powerful program with a user-friendly WYSIWYG interface quite similar to professional programs like Finale or Sibelius. It can handle just about any of the music you're likely to encounter in DP projects. It's available for various platforms beyond Windows and Mac, it can produce high-quality audio, and it can import and export MusicXML.
Before MuseScore came along, some DPers used Lilypond, a free text-based notation program. Using any text editor, you type in codes for notes and other music features, then run the text file with Lilypond to produce a PDF file with the music image and a MIDI file with the sound. It's powerful and can handle just about any of the music you're likely to encounter in a DP project. But Lilypond is primarily an engraving program focused on appearance rather than sound. It has a very steep learning curve, it's very time-consuming to use without a third-party graphical interface, and it can't produce high-quality audio or MusicXML. Worse, it isn't backwardly-compatible - its code changes constantly, and older Lilypond files can be difficult or impossible to convert to newer versions. It is not recommended for DP projects.
Optical Music Recognition
Formerly known as "music OCR," optical music recognition, or "OMR," is the process of digitally recognizing musical symbols from a scanned music image and turning it into editable notation.
There are a number of commercially available OMR programs, but you should be aware that OMR is nowhere near as reliable as OCR - and we know from our work at DP that even OCR, as highly developed as it is, has its drawbacks.
It's usually much quicker just to enter notation manually than it is to edit OMR output. The error rate tends to increase dramatically with complex music or the kind of low-resolution score images we often encounter in older books.
Given these factors, at this time the use of OMR is not recommended for anything but the simplest music with the clearest images. If you do use it, be sure to check and edit the output very carefully.
Below are just a few of the vast number of music resources on the Internet.
Dolmetsch Online has an extensive collection of music resources, including:
- Chart of Note Ranges (scroll down to the two staff lines near the bottom of the page) - This is extremely helpful in rendering notes in plaintext, using either scientific notation (middle C is C4), or Helmholtz notation (middle C is c´). It's also helpful in identifying notes that are far above or below the staff line.
Scores and Performances
- IMSLP/Petrucci Music Library - Huge selection of free, public-domain scores and recordings of classical music. Helpful for error-checking or where a scan is unclear.
- Choral Wiki - Large selection of free, public-domain choral scores.
- YouTube - Free videos of music performances in all genres. Helpful in determining tempo and feel.
- OperaGlass - Large selection of opera libretti. Very useful for checking opera lyrics.
- Art Song Central - Archive of free, public-domain art-song sheet music, managed by DP Music Team founder David Newman.