ECE 346: Digital Signal Processing Spring 2013

Term Project Due Date: Midnight May 08, 2013

This term project is expected to help you better understand some of the material learned in the class. Because of the length of this document, it is imperative that you pay close attention to all the rules and regulations as well as submission instructions concerning this project.

Short Description of the Project

This project, which is worth 10% of the course grade, deals with audio equalization in the digital domain. The fundamental assumptions underlying this project are the following: You are dealing with a high quality single-channel audio signal that has been sampled using a sampling frequency fs = 44.1 kHz. The input le, satisfying this sampling rate, is in wav format. Similarly, the output le generated as part of the project and satisfying this sampling rate is in wav format. As part of this project, you are required to design and implement an 8-band audio equalizer in Matlab. All ltering operations as part of this project need to be carried out using linear-phase FIR digital lters. The desired equalizer frequency bands are given in the following table: Table 1: Design specications for the audio equalizer Band number 1 2 3 4 5 6 7 8 Low end of the band (frequency, in Hz) 0 200 400 800 1600 3200 6400 12800 High end of the band (frequency, in Hz) 200 400 800 1600 3200 6400 12800 22050

2
2.1

Project Details
Team Composition

This project is a team project. Each team must consist of at least 2 members, but cannot have more than 3 members.

2.2

Team Goals

1. Design and implement an audio equalizer according to the specications in Table I. The implemented audio equalizer must satisfy the following constraints: (a) The attenuation or amplication of each band should be adjustable anywhere between 10 dB. Note that a setting of 0 dB in each band leaves the signal unmodied in that band. (b) The FIR lters used in the implementation should not be longer than 512 taps (length of FIR lters). (c) The Matlab implementation should have a graphical user interface (GUI), somewhat (not necessarily exactly) along the lines of the following gure:

(d) The main implementation of this part of the project should be in a Matlab m-le, with equalizer.m as the name of the implementation le. 2. State one or more methods by which you could measure the frequency response of the implemented equalizer. Plot the equalizer frequency responses and the used set of lter coefcients for the following gain vectors g = [g1 , . . . , g8 ], where gk , k = 1, . . . , 8, represents the gain in dB in band k : (a) g = [0 (b) g = [8 (d) g = [3 0 6 0 2 2 0 0 0 0 1 0 1 2 0 3 2 0] 6] 10 10 5 8] 10 10] 3

(c) g = [10

10

10

10

3. Test your implementation with real audio signals of your choice. (a) Make use of (and provide along with your submission) sample input and output signals for several cases, including high bass, high treble, attenuation of vocals, etc. (b) Plot both the ideal frequency response based upon the equalization settings and the frequency response obtained with your lter coefcients.

Project Deliverables
1. A project report written collectively by all the team members. The report must satisfy the following constraints. (a) Report should be in two-column format on a letter paper with 1 inch margins on all sides. (b) Report should be written using a font size of 11 pt. (c) Report should be no longer than 5 pages and no shorter than 3 pages. (d) Report should be submitted in pdf format. 2. A zip le containing the Matlab implementation les. The zip le should include at least the following items. (a) The main implementation les, with proper comments. (b) The input audio les used to test the implementation. (c) The output audio les generated from the test les. (d) A main, commented script (Matlab .m le) with the code that was used to test the implementation. (e) A short manual (word .doc or .docx le) that describes how to run the code.

There are two main deliverables for this project.

Submission

The submission of this project will take place on the Easy Chair Conference System. Please, do not submit your project on sakai. Please note the following instructions. 1. The submission will take place on the website https://www.easychair.org/conferences/?conf=spru13 and should be done by only one of the team members. 2. All team members, however, should register on the Easy Chair Conference System (the reason will become apparent below).

Project Grading

This project will be graded partially by the instructor and partially by your peers in the class. Please note the following in this regard: 1. 75% of the project, in other words 7.5% of the course grade, will be awarded to the overall project and all members of the team will receive the same grade for this part of the project. 2. Each student in the class will be asked to peer-grade 3 projects in the class using the Easy Chair Conference System. Each project in the class will end up having anywhere from 6 to 8 students grading it and the nal grade for the project portion will be based upon average of the peer-grades.1 3. 25% of the project, in other words 2.5% of the course grade, will be awarded to individual students based upon the thoroughness and thoughtful nature of their individual peer-grading. This part of the grading will be done solely by the instructor. In particular, grades submitted by the students who carefully read the project reports, meticulously ran the submitted code, and gave constructive feedback to the submitting team will receive higher grades for this portion of the project and vice versa.
1 Please

note that the instructor reserves the right to ignore a peer-grade if animosity, cronyism, or lack of objectivity is noticed in the grade.

Timeline
Finalization of the team composition using the Sign-up tool on Sakai: April 5, 2013 (11:59 PM) Submission of the project deliverables on the Easy Chair Conference System: May 08, 2013 (11:59 PM) Assignment of projects for peer grading on the Easy Chair Conference System: No later than May 11, 2013 Peer-grades (along with complete justication/feedback) due on the Easy Chair Conference System: May 18, 2013 (11:59 PM)

Plagiarism Warning

While students are expected to use the Internet for this project, no material (written or code) should be used by the students without explicit attribution. In particular, any team involved in plagiarism will be immediately awarded 0 points for the project and the team members will be referred to the School of Engineering for disciplinary actions, regardless of whether the plagiarism was on a small or a large scale (even a single line of code copied from another place will count as plagiarism).