Audio data generated by configurable bytecode VM

[jimd1989]

Rather than having hardcoded parameters, the program should expose variables like volume, feedback, wetness, delay time, etc to the user and allow him to use them to his own ends via a stack-based language that runs in a VM. Much of this work has already been completed in the vm directory, but it hasn't been wired to audio yet.

• The audio program is compiled from plaintext to bytecode once, and then run against every sample of left and right input.
• At the end of a program run for a given sample, the stack should contain two floats: a right sample and left sample, with left on top, since popping will allow access to left first, as is conventional.
• This will yield four floats for each sampling cycle: left/right derived from left input, and left/right derived from right input. These can be mixed down the stereo however one wishes.
• Errors should fail silently and sound should continue at all costs. Glitched audio is half the point of allowing this level of access.