These notes are based on our initial meeting on 24 January 2012. The aim was to collect some use cases and have an initial idea on what needs to be done to extend or revise the existing Audio Features Ontology.

Topics discussed (roughly)¶

• What are the main research use cases for an Audio Features Ontology (AF) ?
• Are they served well by the existing AF ?
• If not, what are the most important extensions we need to do?
• Does the fundamental structure of the ontology need to be changed?
• What is the relation of AF to existing software, including:
  • software like: Sonic Annotator, Sonic Visualiser, SAWA, AudioDB other tools...
  • and projects like: OMRAS2, EASAIER, SALAMI, new Semantic Media/Semantic Audio grants...
• Personal Objectives: what are we going to do with a modified/re-engineered ontology?

Use cases:¶

Use cases discussed so far:

Thomas:

• drive audio effects -> adaptive effect (controlling effects)
• KM like use case: association of audio effects and audio features e.g. pitch shifter won’t change onsets
• part of the AFX ontology
• more audio features
• technical classification of audio effects

Steve:

• Finding structure, repeated sequences of features
• Beat related stuff, BPM (tempo, major/minor is it an audio feature, not necessarilty)
• Chords => Chord ontology
• Melody and notes

George:

• Improve SAWA
• Facilitate the development of intelligent music production systems
• Release large content based metadata repositories in RDF
• Re-release the MSD in RDF (??)
• Deploy a knowledge based environment for content-based audio analysis based on the concept of the Knowledge Machine that can combine multiple modalities
• Research reproducibility using Ontologies as a model to exchange research data.

Open issues:¶

Some important questions to be decided on:

Domain boundaries and scope:¶

• Are Musicological concepts outside the scope of an AF ?
• How about Physical features:

  *Acoustic features,
  *Perceptual Features,
  *DSP type feature,
  *Musical Features (musically meaningful features related to acoustics)

Fundamental structure of the existing AF Ontology:¶

The Audio Features Ontology currently provides a core model

The main scope of the ontology is to provide a framework for communication, feature representation, and describe the association of features and audio signals. Therefore it does not classify features, describe their interrelationships or their computation. With re- gards to the different conceptualisations of feature representations presented in table 4.2 (see §4.2.5.1), the Audio Features Ontology deals with data density, and temporal characteristics. It differentiates between dense, signal-like features of various dimensionality, for instance a chromagrams and detection functions, and sparse features that are scattered across the signal timeline, for instance, notes, or onsets.

• Does it serve us well?
• For example, loudness is defined as a segment in AF, and it does not fit a perceptual attribute well.
• What depth do we want ? (both in terms of scope and the level of detail in describing a feature extraction workflow)
• How AF relates to the DSP workflows used in extracting them?

Existing resources :¶

Some work related to Steve's use cases, segmentation and Ontologies:¶

• SALAMI Project: Kevin Page, DaveDeRoure http://salami.music.mcgill.ca/
• The Segment Ontology: http://users.ox.ac.uk/~oerc0033/preprints/admire2011.pdf
• PopStructure Ontology: Kurt Jacobson Unpublished.
  (Example available: http://wiki.musicontology.com/index.php/Structural_annotations_of_%22Can%27t_buy_me_love%22_by_the_Beatles)
• Similarity Ontology: Kurt Jacobson http://grasstunes.net/ontology/musim/musim.html

Ideas/resources for new Ontologies:¶

• Steve has worked on Acoustics related ontology

• Creating a DSP ontology:
• include processing steps down to math operations
  (this can take advantage to the math:namespace in CWM: http://www.w3.org/DesignIssues/Notation3.html)
• describe common DSP parameters

• create an Acoustics Ontology
• describe Musicological concepts
• describe concepts related to cognitive and perceptual issues

Currently missing features¶

• MFCC-s
• Rythmogram
• RMS energy
• combined features, e.g. weighted combinations or statistical averages over features

Development issues¶

• chaining, combination, weighting
• how you associate features with arbitrary data
• summary feature types
• SM (similarity matrix) are they part of the ontoogy?
• how to describe salience, can you hear it, can you perceive, is there an agreement
• how to describe weighting, confidence
• mood, music psychology, cognition, emotion, (perception ?)
• provenance => music provenance
• deprecation and versioning

Long term objectives:¶

Some concrete tasks that can be done as the outcome of the collaboration:

• A version of Sonic Annotator that produces output adhering the new ontology
• Are we making people happier by doing so?
• gradual transition period?
• extend other software toolkits; e.g. a verison of Marsyas in C++
• multitrack processing using Sonic Annotator (this feature might come along soon)

Some immediate tasks (TODO):¶

• collect more resources
• Verify the relationship between AF as is, and other feature/segmentation Ontologies
• what other software uses it?
• papers and literature review
• relation to projects e.g. SIEMAC
• collect features that we need
• define scope (extend the diagram of the set of ontologies: )
• collect specific application examples from existing processing chain / workflow

collect software/projects that use/produce audio features:

• plugins, LADSPA, VAMP, Marsyas, CLAM, libextract, COMirva, MIRtoolbox, Supercollider, other frameworks