Last edited 5/5/04 by Justin King
Find this document at http://www.ncsa.uiuc.edu/Classes/MATH198/king1/
#define QUESTION ((bb)||(!bb)) - Shakespeare

A quick Tutorial on incorporating sound into your program.
A quick How-To on running sound.
Some Sample Sounds that Maestro can make

The official Formal Documentation for Maestro



Math 198 Project Abstract
Justin King, Spring 2004

The goal of this project is to provide future Math 198 students with a set of simple functions for use in sonifying their software. By simple inclusion of the header (.h) file into their code, and linking in the pre-compiled output (.o) file into the final program output, anyone can add sounds to their program without understanding any of the technical details of sound generation. This project will include development of several different types of sounds, including ambient/background sounds, triggered sounds, and even some music. Sounds can be set to depend on program variables, or stand alone, independant of what the host program is doing. Sonification of several RTICAs will be done to demonstrate how the code works, and thorough documentation will be available for future programmers to use.



Math 198 Project Report
Justin King, Spring 2004

Schedule of Project Implementation
  1. Exploring Sound
    1. Learn VSS methods for a triggered sound (Finished 4/14)
    2. Learn VSS methods for a parambient sound (Finished 4/30)
    - ***Complete by Wed, April 14*** -
  2. Developing Sound Functions
    1. Write .h file for sound function headers
    2. Write functions for sound startup/stop (Finished 4/21)
    3. Write function(s) for triggered sound (Finished 4/27)
    4. Write function(s) for parambient sound (Finished 4/30)
    5. Write function for play of sound files (Finished 5/7)
    - ***Complete by Fri, April 30*** -
  3. Implementing Sound Functions
    1. Develop Makefile to include sound functions (Finished 5/3)
    2. Put sound functions into gasketry programs (Finished 5/3)
    3. Put sound functions into a few classmate program(Finished 5/3 - Carl Press's illiPong)
    - ***Complete by Fri, May 7*** -
  4. Documenting Sound Functions
    1. Write good commentary into code (including during development)
    2. Write Readme files for each function developed (Finished 5/14)
    - ***Complete by Mon, May 10*** -
Note - dates updated/changed 4/12/04
Note - dates updated/changed 4/23/04

I like this quote, so I'm keeping it on this page - Twas brillig and the slithey toves did gyre and gimble in the wabe. All mimsy were the burogoves and the mome raths outgrabe.