After some more optimization of the code we have refined the interaction were it needed to be. Values of responsiveness, accuracy and consistency are the ones we experienced needed have positive impact on the user. We felt that it was working at half the capacity. Trying out different microphones and computers didn’t solve the issue rather it confirmed that the code needed to be individually tweaked for that specific computer.
We got the interface to work to our liking but had to sacrifice the function where the user would imagine a color, try producing a sound and that color would be generated. The way we thought to solve this was to assign a value to the color after some global average of what people think of color e.g. white would correspond to a low value and the most intense color would be a high value. As it was confusing and with our limited coding skills we dropped this function and chose to focus on functions for saturation and lightness in relation to frequency and loudness thresholds.
The video showcases the work and how it reacts to different sounds at different loudness.
The function is written that it randomly shows a color every time when one of the triggers are hit. So frequencies under 300Hz generates a color with low saturation and lightness, 500-2000Hz a color with medium saturation and lightness and 5000-10000Hz high values.
As we tried out this interaction a bunch of times and trying out some different values. We came to the insights that it was a bit limiting, frequency triggers and loudness thresholds alone couldn’t provide a rich quality interaction. By experiencing it we could draw the conclusion that the balance between a fluid interaction and a minimalistic output didn’t open up the design space considerably much. We needed more nuance at the input as well on the output but essentially accepted it as time was running out. More accuracy, precision and fluency in the input/output required us to focus solely on reading up on coding (as well as buying new microphone).
I believe that responsiveness, fluency and accuracy is direct relation with the practical use of the interface, possibly interfering a whole lot with nuance on both ends than anticipated.
Presentation feedback – Overall most groups got almost the same feedback with some minor individual remarks. One important feedback was to work after a set theme. That way the progress can be tracked and credibility can be strengthened. Most groups including us have just explored sound and skill without any theme. This can lead to different paths were positive insights can be found with every new experiment and found only because the aspect or point of view is constantly changing.
“What about it?”, Identify the gap and what is missing in the project is also some valid feedback given to us. Which I strongly believe is in relation with a clear theme. Overall this module has proven to be a bit challenging for us as a group as it demanded attention on coding more than focus on interaction-crafting at some periods, which felt a bit choppy as a learning experience but overall this was module was ok.