Linux Audio Mangler Project Design Presentation Yu Chong Hector Urtubia Tony Zuliani

Introduction Why did we choose an audio editor as our project? Why did we choose to use Linux for development purposes? Why did we choose GTK+ as our windowing toolkit?

Overview (What is LAMP?) A program used to edit audio files of various formats Features the ability to dynamically load filters and sound generation libraries Intuitive, graphical user interface Open source

Demonstration

Project Breakdown Plugin AudioIOSound Driver Utility GUI

Audio Input/Output Module Interfaces with other libraries Currently supported file formats: WAV, AIFF, AU Extendable design

Plugin Module LADSPA overview Plugin interface –Calls LADSPA plugins directly Plugin utility –Analyzes the system for available plugins Plugin GUI –Generates a graphical interface to the available plugins

Sound Driver Module Interfaces with the operating system sound API Basic, hardware-level functionality

Utility Module Provides the GUI with an abstract interface to the lower-level modules –File management –Edit functions –Application of plugins –Playing and recording of audio data

GUI Module Top level module Handles most user interaction Interfaces with other modules –Utility module –Plugin module Visual display of audio file data to the user

Project Difficulties Interaction of the different modules Learning the APIs for the different libraries we used Efficient management of audio data Graphical interaction with audio file data Personal conflicts

Delegation of Responsibility Yu –Sound driver module –Utility module Hector –Audio input/output module –Plugin module Tony –GUI module

Project Management CVS (concurrent versioning system) –source code management Coding standards Project web page and mailing lists provided by sourceforge.net – Weekly meetings (Sunday, Wednesday)

Project Status

Questions and Comments? LAMP home page