1 / 15

L inux A udio M angler P roject

L inux A udio M angler P roject. 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?).

terenceh
Télécharger la présentation

L inux A udio M angler P roject

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LinuxAudioManglerProject Design Presentation Yu Chong Hector Urtubia Tony Zuliani

  2. 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?

  3. 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

  4. Demonstration

  5. Project Breakdown GUI Utility Plugin AudioIO Sound Driver

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

  7. 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

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

  9. 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

  10. 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

  11. 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

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

  13. Project Management • CVS (concurrent versioning system) • source code management • Coding standards • Project web page and mailing lists provided by sourceforge.net • http://lamp-project.sourceforge.net • Weekly meetings (Sunday, Wednesday)

  14. Project Status

  15. LAMP home page http://lamp-project.sourceforge.net Questions and Comments?

More Related