˗ˏˋ ChristineDinata ˎˊ˗

From one of my last experiment , I tried to change the data input. Instead of using audio, I replaced it with OSC data from my Muse headset. To connect your OSC device to TouchDesigner, make sure that the IP address and port number is the same so the data transfer can be accurate. In this case, I use a third-party app called Mind Monitor (available on iOS devices) to connect my Muse headset to the TouchDesigner software. Below are screenshots and videos from my experiment. You can see that the brainwave data is already recorded in real-time in the software. Then I used the alpha, beta, and theta brainwave to change the movement of the visuals (the chosen brainwave data I used are just placeholders for now to see the movement). Then the data is connected with 'noise', which is like the fluid/abstract visuals you see on the background. I also set the colors to be moving/changing over time.

Trying to figure out how to fix the problem I faced on my last post, this time I tried to change the input source into the ZIGSIM-related data shown on the video below.  However, I think the data appointing (which source data is supposed to be which) is still wrong from my side. I have to figure out which is which. Note: The ZIGMSIM on my phone is connected correctly (therefore the two moving graphs on the upper part of the video). Then after trying to changing the source data, the rectangle box is moving but not moving the way I want it to move. It can't really go vertically upwards.

Since Muse headset can deliver brainwave data in the form of OSC, I wanted to try out how to input OSC data to TouchDesigner. To try it out, I searched for how-to's video and article and found this article posted by the TouchDesigner group themselves. In this post, they mentioned that there are several ways to insert the OSC data stream to TouchDesigner by an iOS application; TouchOSC and ZIGSIM. When I searched for both applications, the TouchOSC app is a paid app, while ZIGSIM is free. So I decided to try ZIGSIM. Unfortunately, the article did not explain in detail on how to use the ZIGSIM app on TouchDesigner. So from there, I searched for any ZIGSIM - TouchDesigner related posts and found this . This post from ZIGSIM explains that we can send motion data from our device to PC. There are basically two 'tutorials' that the article showed. The first one is using another app called ZIG Indicator which can help visualize sensor values. However, ZIG Indicator can onl...

This time, the experiment I did with TouchDesigner is creating this audio-reactive abstract wave visual by following Bileam Tschepe 's tutorial on Youtube. This time, Bileam Tschepe's video thought us how to convert an audio spectrum directly to TOPs using the CHOP to TOP and compositing. Following his tutorial, here is my version of the project.  Song by Muskatt .

When creating the visuals for my final project, I was inspired by a 'Spectrum to TOPs' tutorial created by Bileam Tschepe on Youtube (I did a post about it here ). The tutorial teaches the audiences explicitly to convert an audio spectrum directly to TOPs using the CHOP to TOP and compositing. Since Bileam Tschepe used audio as the source information for the visuals, I changed the former portion of the tutorial from audio data into OSC data (blog post  here ). Since OSC and Audio data are in the CHOP section, and to create visuals are in the TOP section, a 'CHOP to TOP' node is required. Initially, the node is represented by one pixel high and in black and white; to adjust it, simply change the data format if necessary (for the color), and adding a composite node changes the pixel size. A Noise node is added because it is responsible for the output resolution of the project. The Noise node is also where the author attaches the OSC data in the transform section. This all...

My second experiment with TouchDesigner is creating this audio-reactive particle visual by following Bileam Tschepe 's tutorial on Youtube. Again, I just followed his tutorial step by step. This tutorial is a little different because it uses both audio and visuals. The visual follows the music in real-time. Other than audio, we are also introduced with the element 'Math' to add the channels of the audio together. This is the end product. Music is FriendsV2 by Muskatt.

My first experiment with TouchDesigner is creating this particle displacement visual by following Bileam Tschepe's tutorial  on Youtube. His tutorial is pretty clear on how to create this project, however, I'm going to show a little on how it goes. This is my result.

This post is to update my experiment on the Thinker Blinker project. Thus far, I had been trying to 'install' the appropriate node.js that are necessary for this project to work. The first thing I need to make sure is the file being in the right folder. In the following picture, we can see that the file I wanted to run is called 'index.js' that is located in /Users/christinedinata/index.js . So I typed 'node index' on my terminal/command prompt page (read more from this post I uploaded previously) to call the file to get it running. However, there are some 'errors' because it says that the computer can't find the osc module. Upon more research on how to handle this problem, it turns out another node is needed.  npm install node-osc (more information h ere ) But when I wanted to install this, there are a lot of issues and errors as well.  This prompt lead me to search more on why I can't install this node-osc. This  per...

So I want to try the Thinker Blinker project from my previous post. As mentioned, they use an Arduino Pro Mini 328 - 5V/16MHz. So hence that is what I bought. Since I already have my Arduino Uno, I wanted to just use it to program my ProMini instead of having to buy USB to serial converter. Basically, the ProMini will act as the IC board of the Uno, which is the board crucial to make the Uno running. After searching the tutorial on how to connect your ProMini to your Uno, it turns out it is pretty simple. I found someone that created the tutorial here . Step 1: Remove the IC from the Arduino Uno board. This is important because we have to 'incapacitate' the Uno so that all the 'power' will go to the ProMini. Now we just have to connect the Uno to the ProMini. I'm using a solderless breadboard to help me do this because it allows me to join other external components like an LED bulb, etc. to try whether the codes actually work. Ste...

So, recently I've tried to connect my Muse 2016 headband to MuseLab / MuseIO. The reason why I did it is to try out the Ristiaallokko experiment. So far, I haven't successfully built it. There are many factors to it. Being unfamiliar with C+ codes is one of them. I really don't know where to start and what to do to fix it. The second thing would be no familiar with Xcode. I don't know where are the options to fix the things they app warned. There is a lot of Googling needed to be done to even understand the errors the app mentioned.  One of the first things you would notice when using a newer version of Xcode or building a new system with an older version legacy map is that the Always Search User Paths (ALWAYS_SEARCH_USER_PATHS) setting is set to YES, but is not supported by the new build system. Make sure to change the ALWAYS_SEARCH_USER_PATHS to NO and migrate to using modern header include syntax (for more info click  here ). Changing it to NO helps ...

Earlier this week I mentioned an interactive art I found that uses the Muse headband as their EEG reader. It is called Ristiaallokko. The creator (or someone related in working on the project) shared the codes to Github . They also clearly state that they are using a 2014 Muse headband. They said that they: build it on top of MuseIO to access data and Muse command-line tools to send data via OSC to OpenFrameWorks and they are building the project on Mac. However, if you check the official  MuseIO website , you will notice that Muse said that they are currently not supporting the MuseSDK. Basically, we cannot download the MuseIO or access the Muse command-line officially from Muse. (Which is the most important application to get this project running) Then I scoured the internet and found someone posted the MuseLab content to be downloadable ( here ). Note that the version provided is only compatible with macOS Mojave (version 10.14.5) and under, cause I tried downloading ...

Upon researching further on how to use Muse headband's brainwave in real-time, I stumbled upon two mobile applications that can support this. One is called Muse Direct, created by the company Muse themselves, the other one is called Muse Monitor, which is a third-party app created by fellow Muse enthusiast, James Clutterbuck. He created this app to help users to record their brainwave activity in real-time and saving those files in .csv (excel form). These .csv files will then be uploaded to the Muse Monitor website  and they can produce colorful graphs that will allow users to read them. These graphs consist of 5 important waves such as Delta, Theta, Alpha, Beta, and Gamma. As you can see here, the app is reading the user's brain activity in real-time. It will change according to how the person is thinking, feeling, doing. There are a lot of factors contributing to the reading as well, such as how the headband is worn on the head, any rough or forced blinking of th...