Wekinator part 2
Three Wekinator Projects:
Reflection: (300 word)
- This assignment was much more difficult for me than I anticipated. I had some easy wins, but many difficult battles when it came to getting this assignment done. Some aspects such as learning how Wekinator itself worked, had a setback with the initial steps but eventually became easy to understand. However, the most difficult part for me by far, was the difficulty of trying to decide what to make, and how. I knew that many of the other softwares either had issues with start-up for my laptop, or were unfamiliar to me and would have been an issue of learning how to use it for the first time individually with no promise of if it would work, if I even had an idea of what to do with it. More than that, trying to find a balance between what was creative, and what was simple, and what would fit within the scope of time needed for 3 projects was a huge hassle. That is clearly seen in what I did do and why they are so similar. They all use the same software, and have similar premises but with different uses and goals. The most difficult choice however was by far what to do for the musical instrument one. I knew it had to be linear regression, and I knew it had to have continuous inputs. I had plenty of ideas for classification-type tasks or gesture recognition ideas, but nothing I could come up with for the music one. I tried my hardest to come up with ideas, but that was the project of this assignment that left me lost every time. I would barely make progress unsure of what to do. And how to move forward in a way that made sense. I kept getting ideas that didn’t fit the restriction, would have already started on that idea then realized part way that it wouldn’t work. This happened with the other projects a little bit, but nowhere near where it hit for this. That being said, I did come up with some ideas, and more than anything I am just glad to be done so that I can shift focus to the many finals and end-of-quarter crunchtime priorities ahead.
- I used the tutorial video provided for a quick start on the Wekinator website. For the tools, I used the provided tools/code in the class assignment website for the starter codes and the camera face gesture recognition software.
Vic - 2/27
- So far my explorations have been fun but not super inventive or creative yet. Mostly I have been working on getting things to work and exploring possibilities. I had an idea that I thought would be fun to make a program that figures out where you are and then maps the sound so that even when wearing headphones it seems like the sound is coming from the laptop. That was my goal for this first wekinator experiment. It was partly a learning exercise and partly an idea I tried. While it was helpful for me as far as understanding wekinator, and osc, it did not end up being as fun as I thought it would be. And the recording I did I couldn’t get the recording to work through headphones so it is coming from the laptop, but ideally, this concept is supposed to be for headphones. (So that you can have all of the effects of not wearing headphones, while still having them on.)
- Other than this particular project I have been trying out the unity software, looking at the example code and projects, and trying the project I just did with different inputs (I did the 2D mouse before I tried the camera), and attempted to use different machine learning options in wekinator to get an idea for what they are and what the differences are. I also started a project with emotion recognition, which worked really well so far with wekinator, I am hoping to expand it to include some unity visuals as well, and have an emotion reader be my second thing, and then have a musical instrument as my third.