Skip to main content

Connecting your Muse 2016 headband to MuseLab

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 it on a macOS Catalina (10.15) and the MuseIO is unable to be opened.

On the Github instructions (which are not very thorough), said that the file needed to be opened from OpenFrameWorks and just run it. When you download the OpenFrameWorks and open it, they will instruct you to download Xcode from your Apple Appstore. The Xcode application will take around 7-9GB of your memory.

The issue with downloading Xcode from the AppStore is that they are always up to date. And if you tried downloading the latest version on a Mac with a version under 10.14, you will be unsuccessful.

So make sure that your macOS is ONLY on version 10.14.5 or 10.14, to get both the MuseLab and Xcode running at the same time. Nothing less or more. (p.s. this setting is suitable for when this post is uploaded.)

Since Muse2016 is still unable to connect directly to the MuseIO application, you have to download a third-party app, and most people recommend the Muse Monitor. But, Muse Monitor records .csv files, and the MuseIO reads .osc files.

This means that Muse Monitor cannot directly substitute the MuseIO, but instead have to be connected so that the Muse Monitor can read the user's brainwave activity in real-time, as well as sending the readings to the MuseLab app.

To connect the MuseLab app to your Muse Monitor app, you can check this for more information on the technicalities.

Once your Muse2016 headband is connected (indirectly) to your MuseLab, you will see that the application is reading your brainwave activity if it is connected correctly.

This is just the situation I was facing for a couple of days trying to figure it out. This does not mean I have successfully tried the GitHub project. Still facing a couple of issues on how to read the codes with OpenFrameWorks and Xcode.

Comments

Popular posts from this blog

TouchDesigner Experiment: Inserting OSC data with OSCIn

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.

TouchDesigner Experiment: Audio Reactive Particle Cloud

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.

Arduino Experiments (pt. 1)

Earlier this week, I bought my first Arduino Kit . Since this is week 6 of term, our lecturer has asked us to display an experiment by week 7. It could be any type of experiment, and it doesn't even have to be related to our project. The reason why I picked to try on Arduino is that I think it's the closest medium I'll be using for my actual work. But I was kind of worried about this, mainly it is because I've never used or tried it before. I've only heard about it but never actually played around with it. So this is the kit I bought. It costs SGD 70 at one of the shops in Sim Lim Tower. It contains a lot of items to try out experiments. It also includes several tutorial cards that can be successfully running with the items provided in the kit. For more detailed tutorials and the codes of each project, we are asked to go to their website and search for the complete step by step tutorials. Thus far, I have tried several projects, and for ...