Muse Port

Muse Port is an interface device that allows streaming of the data collected by Interaxon's brainwave-sensing Muse headband (http://www.choosemuse.com/) directly into Ableton Live. Five brainwave frequencies, three axes of accelerometer data, blink and jaw clench detection can all be graphed in real time along with your midi and audio recordings, as well as mapped to control any Live parameter.

To begin, follow steps 1 through 3 outlined here

http://developer.choosemuse.com/research-tools/getting-started

and then start up Ableton Live and the Muse Port, which should already be set to the correct UDP port and begin streaming data.

NOTICE: The 2016 headbands do not work with Muse IO, so the above steps will not work to get the OSC data into Ableton Live. It seems their plans are to replace Muse IO with a new app called Muse Direct. At the moment it is only available for Windows 10 (https://www.microsoft.com/en-ca/store/p/muse-direct/9p0mbp6nv07x) and notably the default port is 7000 rather than 5000, so that adjustment will need to be made. If you're not on Windows 10, for the time being the best method is to download Muse Monitor (http://www.musemonitor.com/) and use your Android or iOS mobile device as a middleman. With any of these methods all you need to do is get it sending on the same port Muse Port is listening to and you should be good to go.

The current UDP port, remaining battery life and the connection quality of the four sensors are all displayed in the top portion of the device. If there are one or more flashing circles in the headband-shaped icon, adjust the Muse on your head until all four sensors are reading well.

Mouse over any of the numbered outputs along the bottom and a popup window will appear which displays a graph of the data streaming through it. Click along the wire leading to the numbered output to hold this popup in place. You may now select options in the popup itself.

Sensor Mode

Brainwave readings from the four sensors of the Muse can either be averaged as they arrive in the device or the highest can be used and the rest discarded.

Hone Range

Sometimes it can be useful to hone the range of the incoming data, in order to magnify its effect. If selected, the device will monitor readings and use only the highest and lowest it's seen to set the limits of the data stream, rather than the absolute full range of the sensor. The duration of this monitored history can be set via the Memory Span control in the settings.

Clicking and dragging anywhere else in the popup will change the scaling of the graph. Click again on the wire to allow the popup to close.

If you click on one of the numbered outputs itself a menu will appear. This menu displays all of the current mappings. Click 'Map New...' and then click on any enabled parameter anywhere in Live and it will be remote controlled by the data leaving the output. You can simultaneously map to up to four parameters per output. After a mapping has been assigned, you can click on its name in this menu to disconnect and remove it.

Any of the data outputs may also be mapped through the main audio channel of the device itself. Click on the triangle-shaped input on the left and a menu will appear which lists all of the available connections.

Alternatively, you may also map the actual audio signal passing through the device to any parameter you wish by clicking on the triangle-shaped output on the right.

Click on the Muse Port logo to open up the settings menu.

Memory Span

For parameters with Hone Range selected, the device will look this many seconds into the past when determining the limits of its output range.

Unlimited Memory Span

The Memory Span will be as long as the time from when this, or the individual parameter's Hone Range control was selected.

Automate Parameters

The most convenient way to record Muse data in Live is to automate the parameter in question, thereby graphing it right along with your audio or MIDI recording in the arrangement view track. However, this unconventional strategy has its drawbacks. Namely the undo history will be compromised as it will perpetually fill while recording, which can be quite resource intensive both in terms of RAM and disk usage. Use with caution.

Included in this download is a small companion device which generates midi notes based on an input stream. So for example, you could hone the range of the Relative Y-Axis Position output and send it to the Midi Generator to create a beat by nodding your head. Click here for the full description: https://sellfy.com/p/ns3f/.

These are Max for Live devices. They require Ableton Live 9.1 Suite or newer and at least a trial of Max/MSP 6.1 or newer, which can be downloaded from http://cycling74.com/downloads/. Older versions of Live and/or Max may work just as well, but there are no guarantees.

I'm always glad to hear feedback on my work! Please send any questions, issues or feature requests to [email protected] And if you make something cool with one of my devices I'd really like to hear it! If you want I can do what I can to send some traffic to it, especially if it's on soundcloud. Mine's https://soundcloud.com/to_the_sun.

Version 1.2 update

Version 1.2 works with the latest OSC paths and also takes advantage of some of the newer measurements they added, such as absolute vs. relative brainwaves, as well as Concentration and Mellow scores. In addition if you click on the Muse Port logo you will see that streaming data (and therefore mapping it) must be turned on and is not on by default. Note that the five standard brainwaves report absolute values, whereas before they reported relative session values, and now there are five separate relative brainwave parameters which can be automated (graphed). The two experimental scores Concentration and Mellow can also be automated, and since version 1.2, they can be streamed in real time and therefore mapped to any parameter in Live. In the device they have taken the place of the 3rd and 5th outputs along the bottom. Previously these were the Alpha and Gamma outputs, from which Mellow and Concentration are derived, respectively. If you're savvy with Max for Live, you can access the data that is Retained In History by using a [coll ii-history] object; this is how I've been doing my experimentation.

If for some reason you want to use the previous version, it is also included in your download, along with the legacy SDKs for both Windows and OS X that are required for it.
Powered by