The classes defined in the net.charlesames.music framework model elements of musical scores which are either performance-ready or notation-ready.

See:
Description

Packages

net.charlesames.music.common	Classes in package music.common implement shared functionality.
net.charlesames.music.ensemble	Classes in package music.ensemble define the structure of scores.
net.charlesames.music.midi	The classes in this package have two missions: (1) to build a MIDI sequence from scratch and (2) to take an existing MIDI sequence and explain its contents.
net.charlesames.music.musicxml	The purpose of package music.musicxml is to generate files in MusicXML format.
net.charlesames.music.musicxml.attribute
net.charlesames.music.musicxml.notation
net.charlesames.music.score	Classes in the {code net.charlesames.music.score} package represent musical scores and the components which comprise musical scores.
net.charlesames.music.utility
net.charlesames.utility.audio
net.charlesames.utility.common
net.charlesames.utility.contour
net.charlesames.utility.date
net.charlesames.utility.entity
net.charlesames.utility.error
net.charlesames.utility.hash
net.charlesames.utility.html
net.charlesames.utility.io
net.charlesames.utility.launch
net.charlesames.utility.math
net.charlesames.utility.oops	Classes in package net.charlesames.utility.oops implement exception subclasses.
net.charlesames.utility.utility
net.charlesames.utility.xml

The classes defined in the net.charlesames.music framework model elements of musical scores which are either performance-ready or notation-ready. Together they provide the components to represent a score which is performance-ready, notation-ready, or both. The framework is not intended for compositional applications. Score instances can be saved to and loaded from data files using an XML format which mirrors the framework's object structure. They can also be exported to MIDI, MusicXML, and MusicN file formats.

These pages document framework version 1.2.9. The build date is 2015-09-24.

The vertical structure of a score is described in the Ensemble entity. Every Score is associated with one Ensemble, but a single Ensemble can be associated with many Score instances. The Ensemble defines the EnsembleVoice components, It also defines the EnsembleInstrument components that map notes to sounds, and the EnsembleContour components that control things like tempo and dynamics. The relationships between these entities are determined by nested EnsembleChoir instances. These allow one EnsembleInstrument or one EnsembleContour to be shared between multiple EnsembleVoice instances.

Author:

Charles Ames