MelodyScript is a melody-oriented DSL for describing melodies, which can be optionally annotated with chords.

Melody Scripter parses a MelodyScript file into a Python Song object model, which can be used to generate a Midi file.

Here is "Yankee Doodle" in MelodyScript:

*song:      tempo_bpm=200, time_signature=4/4, ticks_per_beat=4

*track.melody: instrument=73, volume=120, octave=5
*track.chord:  instrument=40, volume= 50, octave=3
*track.bass:   instrument=19, volume=100, octave=2

[C] c c d e | [C] c e [G7] d g, | [C] c c d e | [C] c2 [G7] b |
[C] c c d e | [F] f e d c | [G7] b g a b | [C] c2 c1 [] r1 |
[F] a. bh a1 g | [F] a b c2 | [C] g. ah g1 f | [C] e2 g2 |
[F] a. bh a1 g | [F] a b c a | [G7] g c b d | [C] c2 c1 r1

In MelodyScript, a "melody" consists of a sequence of notes on the standard Western musical scale, together with bar lines (which must match the specified time signature) and chords, with optional bass notes where different from the chord root note.

The Song object model can generate a Midi file for the melody, for example: yankee_doodle.song.mid. You can listen to an audio version of that midi file (rendered using fluidsynth) at http://whatismusic.info/melody_scripter/.

Currently Midi output is the only functionality provided by the Song object model, but the object model would also provide a convenient representation of melody information for the purposes of scientific analysis.

MelodyScript is line-oriented. There are two types of lines:

• Command lines. Any line starting with the character * (with possibly preceding whitespace) is parsed as a command line.
• Song Item lines. All other lines are parsed as sequences of whitespace-separated Song Items.

A command line starts with a command (after the initial * character).

The command is followed by a : character, and then one or more comma-separated arguments.

Currently there are five commands, which are song, three 'track' commands: track.melody, track.chord and track.bass, and groove.

The song and track commands take arguments which are property settings, consisting in each case of a key and a value, specified as key = value.

Currently all property settings can be executed only prior to any song items, but in future they may be allowed during the song (or additional commands may be defined which are valid within the song).

Available property settings for the song command are:

The tempo_bpm and ticks_per_beat values both determine corresponding values when a Midi file is generated. "Ticks" are the unit of time in the song, and every note or rest length must be a whole number of ticks – if not, an error occurs.

The time_signature is the standard time signature used to describe a bar, when a numerator that specifies the number of beats per bar, and a denominator that specifies the length of one beat as a function of a whole note. (To keep things simple, the ticks_per_beat value must be defined so that one crotchet contains a whole number of ticks.)

If the contents of a bar do not have the correct total length, it's an error. (It's OK to have partial bars at the start and end of the song.)

The subticks_per_tick value is only relevant to the groove command, and it determines how many "subticks" there are in each tick. ("Groove" is defined in terms of sub-tick displacements.)

The transpose value raises or lowers all the note values when generating the Midi file. (An error will occur if transposition causes a note to go out of the valid range of 0 to 127.)

The three tracks, melody, chord and bass, correspond to three Midi tracks generated in the Midi output file. Each track has its own settings:

(The octave defaults are for melody, chord and bass respectively.)

The instrument and volume settings define the Midi settings for each track. Midi instrument numbers range from 0 to 127, and the actual sounds depend on the SoundFont used to play the Midi song, although there is a standard GM set of Midi instruments definitions (where the default of 0 corresponds to Acoustic Grand Piano).

Currently MelodyScript does not have any provision for per-note volume (velocity) specification. In practice there is no easy way to determine appropriate volume values, for example when typing in from sheet music. For playback it is recommended to choose suitable instrument sounds that work well with constant volume (for example see choices made in the sample song files in this project).

The octave setting determines which Midi octave the first melody note belongs to, and for the chord and bass tracks, it determines the octave of all root notes and bass notes respectively. (Melody note octave values are determined relatively, as will be described in the Song Items section next.)

Although octave values are allowed from -1 to 10, not all Midi notes in the 10th octave are allowed, and an error will occur if a note occurs with a value greater than 127.

A groove command is specified by one or more numerical "sub-tick" displacements.

The number of values given in a groove command must divide evenly into the number of ticks in the bar.

For example, a groove command might specify 0 2 1 2 where there are 4 beats per bar and 2 ticks per beat. The 4 groove values are applied to the 8 tick values per bar by repeating them twice, ie 0 2 1 2 0 2 1 2. Each value determines how many sub-ticks are added to the time of each corresponding tick in each bar.

The subticks_per_tick value in the song command specifies the length of a sub-tick. So if there are 10 subticks per tick, then a groove value of 2 corresponds to a displacement of 2/10 of tick.

There are six types of song item that can be parsed:

• Note
• Tie
• Rest
• Chord
• Bar Line
• Cut

All song items are represented by tokens that don't contain any whitespace, and song items in a line must be separated from each other by whitespace.

The components of a note are, in order:

Continued marker:

If provided, specified as ~. This indicates that a note is a continuation of the previous note.

Note letter:

A lower case letter from a to g. For the purposes of defining an octave, the octave starts at c (this is a standard convention).

Sharp or flat:

Represented by + or -, and only one is allowed.

Ups or downs (octave adjustments):

If provided, specified as one or more ' for up, or one or more , for down.

Duration:

If note duration is not specified, then it is given a default value. For the first note in the melody, and the first note in each bar, the default duration is 1 crotchet (ie one 'quarter note'). For all other notes, the default duration is the duration of the previous note. If a duration is specified, then the specification consists of the following components:

• The initial number of crotchets (if not given, this defaults to 1).
• h or q qualifiers, possibly repeated, which multiply the duration by a half or a quarter respectively.
• t qualifier (at most once), which multiplies the duration by a third
• . qualifier (at most once) which multiplies the duration by 3/2

At least one component must be given, otherwise the previously described default value applies.

Any note duration must be a whole number of ticks, and an error will occur if a note length is defined which is a fractional number of ticks. (In such a case, if the note length is correct, you will need to increase or change the specified ticks_per_beat song property.)

To-be-continued marker:

If provided, specified as ~. This indicates that a note will be continued by the next note.

Except for the very first note, MelodyScript does not provide for each note to specify its octave. Instead, pitch values are specified relative to the previous note. If no "up" or "down" markers are specified, the rule is to always choose the closest possibility. If this choice is ambiguous, eg when going from f to b or vice versa, then an error occurs.

If one up or one down is specified, then the next note should be the first note matching the given note letter, above or below the previous note, respectively. If more than one up or down marker is given, then go an extra octave up or down for each extra marker.

So, for example, c followed by e means go up to the next E, and c followed by e' also means go up to the next E. Whereas e'' means go up 9 notes to the E above that, e, means go down to the first E below, and e,, means go to the E below that one.

(The up and down markers are the same as used in LilyPond in relative mode, however the rule of interpretation is different – in MelodyScript one ' always means the next note up from the previous note, and similarly one , means the next note down. Also, in MelodyScript the rule defines "closest" based on the the actual semitone values of the previous and current notes as specified by letter and optional sharps or flats, whereas LilyPond applies a rule that ignores sharps and flats.)

A continuation is where one note is represented by the joining of two or more note items in the melody script. Because bar lines have to occur in the right place, notes that cross bar lines have to be represented using continuations. There may also be some note lengths that cannot be represented using the Duration format specified above, so they have to be constructed from multiple notes joined together.

In other situations, the use of continuations is optional.

There are two ways to specify that one note is to be continued by a second note:

• Either, the first note ends with ~ and the second note starts with ~,
• Or, a ~ Tie item occurs between the two notes.

It is possible for more than two notes to form a continuation – the required joinings need to be indicated in each case. This would be necessary, for example, to specify a note that filled more than two bars.

A Rest consists of the letter r followed by a duration specification. The duration specification for rests is very similar to that for notes, but there is no default duration, and at least one part of the duration specification must be given. If only qualifiers are given, then they are applied to a value of 1. So, for example, rh is a valid rest, representing half a crotchet, ie a quaver.

Chords are specified by enclosing their contents in [ and ]. Currently there are two formats:

Root note plus descriptor

The root note is given as an upper-case letter with an optional + or - for sharp or flat, and one of several standard "descriptors" from empty "" (for a major chord), 7, m, m7 and maj7. So, for example, [Cm] represents a C minor chord.

Root note plus other chord notes.

Prefixed with a :, the notes are given as upper-case letters with optional +/- sharp or flat, with the root note first. So, for example, [:CE-G] represents a C minor chord.

In each case, chords may contain an optional bass note specifier, to specify a bass note different from the root note. This is given as a / character, followed by an upper-case letter and optional sharp or flat. So, for example, [A+m/F+] represents A sharp minor with an F sharp bass.

Bar Lines are represented by |. Bar lines are used to check that the total lengths of notes and rests in each bar have the correct values. They also reset the default note duration to 1 crotchet. Bar lines do not have any direct effect on Midi output.

A Cut is represented by !. Cut means "cut out all previous song items". A Cut is useful when editing, when you want to play part of the song without starting all the way from the beginning. (There would not normally be any reason to include a Cut in a completed song.)

The main() method of song2midi.py takes one argument which is the name of a MelodyScript file, and compiles it into a Midi file, using the name of the input file with .mid appended. This Python module is also made available as a console script song2midi when MelodyScripter is installed into a Python environment.

For example:

> song2midi yankee_doodle.song

Compiling song file yankee_doodle.song to yankee_doodle.song.mid ...
Writing midi to yankee_doodle.song.mid ...
Successfully wrote midi file yankee_doodle.song.mid.

The main() method of play_song.py generates the same Midi file as song2midi.py and, after generating the Midi file, plays it using the /usr/bin/cvlc command, if that command is available. cvlc is the command line version of VLC, as installed on an Linux system, and it only plays Midi files if the vlc-plugin-fluidsynth VLC plugin is installed. This module is also available as the play_song console script.

For example:

> play_song yankee_doodle.song

Playing song yankee_doodle.song (after compiling to yankee_doodle.song.mid) ...
Writing midi to yankee_doodle.song.mid ...
Playing midi file yankee_doodle.song.mid with cvlc ...
VLC media player 2.1.6 Rincewind (revision 2.1.6-0-gea01d28)
[0x89f45a0] dummy interface: using the dummy interface module...
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.

(Console output from cvlc and the fluidsynth plug-in may be different on your system.)

An alternative playback option on Linux is timidity, however even with the --output-24bit option, on my system, the sound quality is poor at the beginning of the song.

To install the latest stable version of Melody Scripter into a Python environment, execute:

pip install https://github.com/pdorrell/melody_scripter/archive/master.zip --process-dependency-links

Notes:

• Melody Scripter depends on the midi 0.2.3 library to write files. midi 0.2.3 only runs on Python 2.x, and on Linux, the installation requires that swig be installed (eg by sudo apt-get install swig). So, for the moment, Melody Scripter has the same limitations, and it is only tested to run on Python 2.7.
• --process-dependency-links is currently required because the midi 0.2.3 dependency is not directly downloadable from Pypi.
• To install a specific tagged release, eg 0.0.5, replace 'master' in the URL above with the tag.