ECE497 Project Music Server

Team members: Eric Ames, David Cooper

Executive Summary
This project focused on creating a music server hosted on the BeagleBone. The server contains a number of MP3 files which will be playable from the Beagle via either direct access or network access over ethernet/wireless. Currently (all from your web browser) you can upload and download songs, add to and subtract from the playlist, play your custom playlist over hdmi or headphone jack, adjust the output volume, load new media, etc.

We realize it's an odd choice to have a project that focuses solely on software, rather than a combination of that and hardware (ignoring the audio output). But when approaching the project, we wanted to build something that we would actually use afterwards, and not just relegate to the dust bin of history. I would happily say we succeeded.

Packaging
Just about everything needed is in the repo, including the needed node modules. You will need to install NPM and NODEJS on your own. May also need to install module dependencies.

Installation Instructions
1) Go to https://github.com/Guiltygate/beaglebone-classwork and clone the umbreon folder somewhere on your laptop. NOTE:Does not work on Windows. Does not play nicely with IE. Should work with Firefox, Chrome, maybe Safari.

FOR USB-Audio and browser volume control

1a) If you want to use a USB-audio device, you need to set it to default. I used the guide here http://crunchbang.org/forums/viewtopic.php?id=9852 . Also make sure that you have alsamixer, as the sound controls in-browser use command-line arguments sent to amixer, a module of alsamixer. If you don't have alsamixer, you simply won't be able to adjust the volume from the browser.

2) You will need NodeJS, v.0.8.xx or higher, along with NPM. While I include the different node_modules in the git repo, installing them through NPM also installs their dependencies. If you run into issues with the distro not allowing module installation, use node-gyp here: https://github.com/TooTallNate/node-gyp.

3) Due to the whole 'unable-to-reflash-with-Angstrom' problem, I am unable to guarentee this will work on a standard BBB. However, I only use general linux architecture features, so feasibly as long as you can install Express 3.xx on Angstrom, it should be perfectly fine.

4) I'll add another step here whenever I get the server to run on OS boot.

User Instructions
FINISH ERIC See the README for further detail, but here's the basics.

Run ./startServer.sh if you wish to automatically mount your current usb drive. Server will start at 192.168.7.2:0121. If you'd rather just start the server without auto-mounting, run node umbreonServer.js To play the current playlist (initializes to all .mp3 files in the top directory of your flash drive), hit the big arrow button. To view the current playlist/remove songs from it, hit the '-' button on the right. To view the entire directory of mp3 files and possible add them to the playlist, hit the '+' button on the left.

To swap out flash drives, physically switch them and hit the 'Load Media' button below. To stop the current playlist from playing, hit the 'Stop Playlist' button. WARNING:This doesn't always work now, but will add a second 'unload' button to properly unmount it. Should work then.

To download the current track, hit the 'Download' button at the bottom of the page. To upload, simply drag-and-drop the desired file.



Theory of Operation
Using express framework in NodeJS. Enables user to upload songs for playing, download the currently playing song, view playlist, edit playlist, add songs from the directory, change media by swapping out usb drives, etc.

Everything was planned for maximum user convenience, as I plan on using this in my dorm room once I obtain a wireless router for the bone.

Work Breakdown
I would like to point out this wouldn't have taken so long if I hadn't had to learn NodeJS, Express, NPM, alsa, CSS, html, and all the little quirks associated with them. On top of my Beagle dying Sunday and refusing to reflash to Angstrom. Spent all day trying to reflash it, had to switch to Debian Wheezy and re-dowload all the software.

Server Core---Eric--10hrs

Server Features---Eric--30hrs (minimum)
 * Beginning with Express, NodeJS, NPM, als-arch, :: 18hrs (last Friday and Saturday. Sunday was spent praying and trying to fix the Beagle. Monday was spent swapping over to express.)
 * Playlist1hr
 * Playlist viewing20min
 * Playlist editing20min
 * Radio-Stream6 hrs - partially included in the 'Beginning' section
 * Basic GUI---1hr
 * Enhanced GUI4hrs
 * Song uploads6hrs
 * Song downloads--1hr
 * Tracklist---10min

Express Test--David-1hr

Editing the Wiki/Writing Installation Guide-Eric-3.5hrs

Network accessEric--1.5hr

Future Work
1, 3, and 4 I plan on doing over break, I'll update this if I finish (grading should be done by then, so I won't impact that.)

1) Add wireless router for easy streaming, no ethernet cord hassle.

2) Fully implement the Stop and Skip buttons. Currently, they can't stop the audio stream currently outputting, only the rest of the playlist.

3) Add a 'reboot server' button, in case of server failure. Tying into this, the server needs to be able to start on boot- I lost the config files when my board self-destructed on Monday.

4) Due to not knowing CSS or html, the current GUI is a bit crap. I'd like to build a GUI I can actually be proud of, rather than the slap-a-dash affair I have now.

5) Song playback bar, graphically lets you know time remaining.

6) Button feedback. It's weird to select a song and having no feedback if it worked or not. Annoying.

7) The audio modules I use only process .mp3 files, so adding additional modules to process .ogg and other popular audio files would be something nice to add. I myself only have/use .mp3s, so no guarantee I'll do this.

Conclusions
Wish I could have done more with the hardware, like a lightshow tied to the audio or something. But it took a lot of time to learn the different languages/styles/formats I needed for the project. It was all high-leve (mostly), but there's a bunch of little gotcha's that will trip you up if you're not careful. Probably would have helped if I had a partner to double-check my work.

As time-intensive as it was, what with other classes, I had a blast learning so much, and I'm looking forward to continuing to work on this over break and into the future. I also want to look into what other useful applications I could run on the bone with nodejs/express web-servers. Many, many possibilities...