Difference between revisions of "ECE597 Project Music Visualizer"
Line 31: | Line 31: | ||
If time permits, we plan to expand the LED matrix by adding a third dimension. | If time permits, we plan to expand the LED matrix by adding a third dimension. | ||
− | + | We are able to control the 10x10 LED matrix using the beaglebone, using the LEDscape package and its examples. | |
+ | We extended LEDscape with open pixel control, separating the software that controls the pattern from how the software interfaces with the beagle. | ||
+ | We wrote our own patterns in javascript, and have successfully executed the code on the LED matrix. | ||
Give two sentence intro to the project. | Give two sentence intro to the project. |
Revision as of 10:40, 27 October 2014
Embedded Linux Class by Mark A. Yoder
Team members: Zhihao Xue, Ying Ying Zhou
Contents
Grading Template
I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!
00 Executive Summary 00 Installation Instructions 00 User Instructions 00 Highlights 00 Theory of Operation 00 Work Breakdown 00 Future Work 00 Conclusions 00 Demo 00 Late Comments: I'm looking forward to seeing this. Score: 10/100
(Inline Comment)
Executive Summary
This project is a music visualizer implemented with an 10x10 LED matrix controlled by Beaglebone Black. The LEDs light up in response to the frequency and volume information in a MIDI file on the host. If time permits, we plan to expand the LED matrix by adding a third dimension.
We are able to control the 10x10 LED matrix using the beaglebone, using the LEDscape package and its examples. We extended LEDscape with open pixel control, separating the software that controls the pattern from how the software interfaces with the beagle. We wrote our own patterns in javascript, and have successfully executed the code on the LED matrix.
Give two sentence intro to the project.
Give two sentences telling what works.
Give two sentences telling what isn't working.
End with a two sentence conclusion.
The sentence count is approximate and only to give an idea of the expected length.
Packaging
If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.
Installation Instructions
Give step by step instructions on how to install your project.
- Include your github path as a link like this to the read-only git site: https://github.com/MarkAYoder/gitLearn.
- Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
- Include a Makefile for you code.
- Include any additional packages installed via opkg.
- Include kernel mods.
- If there is extra hardware needed, include links to where it can be obtained.
User Instructions
Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.
Highlights
Here is where you brag about what your project can do.
Include a YouTube demo.
Theory of Operation
Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.
Work Breakdown
List the major tasks in your project and who did what.
Also list here what doesn't work yet and when you think it will be finished and who is finishing it.
Future Work
Suggest addition things that could be done with this project.
Conclusions
Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.
Embedded Linux Class by Mark A. Yoder