Woodcut Design Pt. 2

Following the change to the map concept (to differentiate between neighborhoods, both in the physical experience and the music gathering), the physical design has been updated:
StreetBeat is now designed with 3 layers of full sized (90X120cm) wooden plates with additional, smaller, plates showing neighborhoods added on the front layer:

With the resting place of the display devices being moved to the Map Layer (formerly "Front Layer").

Currently, adding more details as another means of separation between neighborhoods.

Generalizable Map Designs

In order to be able to reproduce our design to any location (and any scale) in the world, we have created a small program (html + javascript) that shows just the outline of a map (based on the Google Maps API v3).

Using this program to create an illustrator design of the high-level map and any neighborhoods that should be used for the StreetBeat is a quick and simple process.

Hardware Solutions & Data Flow

Below are 3 possible designs for the physical display and a few advantages and disadvantages for each of them.

Design one shows a dedicated device for each output on the map. This "Station" accesses the Web Server and gets it's specific playlist from there. It then outputs the audio via an Audio Jack and the song & artist name via an Arduino connected to a 16X2 display.

Design two has a PC at the physical display. This PC controls all 16X2 displays via Arduino boards to show song and artist names. This PC also controls all the audio outputs via Arduino boards.

Design three has a PC that, similarly to design two, controls the 16X2 displays via Arduino boards. The PC in this design houses a professional grade audio card with several outputs. The control of what audio channel goes to which output is managed via dedicated low-level software (Java).

Overview of the data flow:

The main DB and Server are cloud-based and are accessed by dedicated REST functions. The types of clients are the "Stations" at the physical display (or the physical display if other solutions are chosen) and the Android App.

Database

Below is a DB diagram for the server DB that holds all collected data for playback and statistical analysis purposes. Key icons indicate Primary Keys and orange lines indicate Foreign Keys.

The DB is accessed solely by the WebServer which in turn publishes the relevant functions for each client (the "Stations" at the physical displays and the Android App).

App Developments

Ran is keeping busy this semester vacation and has seriously bumped up the current apps' functionality.

See it live:

Ran presenting the functionality of the newly developed.
In here we can a list of songs on the player (currently simulated, later on to be delivered from server) and when Ran chooses a song, it is played, with its' respective video from YouTube.