Tell the story of the visualizer, in the visualizer

[C-Kenny]

As a new curious user, I want to know the origins of why this visualizer was born.

Explain:

• inspiration of visualizer
• where the shape elements come from (i.e. the H3 emblem)
• ability to break the visualizer into smaller disgest-able chunks

While demo'ing the visualizer to a friend, it became clear that the visualizer combined with its story was more powerful than the visualizer itself.

Going forward, I'm anticipating a 'start-up screen state' which lays out the context of how this was born.

[C-Kenny]

Need to think about how to approach different states the visualizer can be.

• Visualizing
• Song selection
• Story explanation

As of writing once in the "visualizing" state, it will continue to loop the selected song. It would be nice to be able to jump back, clear any memory and restart with a new song.

[C-Kenny]

Could we specify the states like:

static final int SONG_SELECTION = 0;
static final int VISUALIZER_STORY = 1;
static final int RUNNING_VISUALIZER = 2;

So that when switching between 'states' the variables make more sense?

[C-Kenny]

Attached meta data files to be used in story telling.

[C-Kenny]

In 265077f we added the ability to toggle visualizer elements. This will help for explaining the build up + to digest what's happening from a fresh perspective.