L4COUR
commented
6 years ago I really like your idea regarding the visual part, I might just go ahead and make a version 0.2 and incorporate that idea. it is correct that it can be kind of confusing at first, and that it takes a relatively long time for it in order to maybe communicate clearly to the user. I did think of maybe adding some sort of better indicator for the completion of a cycle, but I didn't have the time ;P. In relation to your description, and this might be my somewhat unclear way of explaining it in the text, it's actually to exact copies of the same specific audio-file, however one of them has a little bit slower buffer rate, thus a change in the speed and pitch, which over a period of time will cause the phasing. I am really glad that you enjoyed my code, and took my advice with using a pair of headphones.
Cheers la Cour
In this project, you experience the auditory effect of phasing by way of two “half” throbbers, each of which is aligned with a different piece of audio and reacts according to that specific audio file.
I really like the idea behind this program. I took your advice and made good use of my out-of-ear headphones to get the full experience, and it was quite interesting and fun to listen to the audio coming at you in the strange way which you programmed it. In this case, strange is a very good thing, and it did a good job of showing the user the idea of phasing in audio.
However, the visual aspect could have been clearer, I feel. It takes a long time before you are able to detect any change in the throbbers, and even then you are left doubting if there even is any change at all. A way to remedy this could be to set the color scheme of the throbbers to change as well as the speed. That way, the throbbers would be nigh identical at first, but would slowly change over time. This, as a visual cue to change, would probably be much easier to notice for the user.
A very interesting take on the assignment. Really, really cool!