Is the accelerometer supported of the Muse 2?

[Peter Gamma]

A miracle happened. The code is here again :

https://github.com/MuSAELab/muse_osc

[Peter Gamma]

But muse-io.exe from Muse SDK from Interaxon is still not available .

[James]

Muse-io hasn't worked since 2016 anyway as it only worked with the 2014 Muse, but the OSC from Muse Monitor will likely be in the same compatible format.

[Peter Gamma]

OSC, Open Sound Control network protocol. A sound protocol for transmitting brain waves? That s confusing.

The most popular application for the Open Sound Control protocol which I could find is this one:

https://www.youtube.com/watch?v=pFPTlWSUL9s

Muse-io hasn't worked since 2016 anyway, good to know. The OSC from Muse Monitor will likely be in the same compatible format, so it should be possible that Muse Monitor can speak to the muse_osc from R_Cassani?

https://github.com/MuSAELab/muse_osc

Then that would be Muse Matlab canditate 1 interface.

Then we have Muse Matlab canditate 2 interface using Java:

https://0110.be/posts/OSC_in_Matlab_on_ ... using_Java

Canditate 2 has a bit more text to read and explanations, that s the advantage.

[Peter Gamma]

Regarding the SDK, yes I've seen the message. I'm still holding out hope they will bring back the SDK soon, but in my spare time I'm working on my own SDK.

I wrote the Interaxon support to get a copy of the MuseSDK, but unfortunately, i had now luck. Here is the answer I received from the Interaxon support. I published it here:

https://github.com/sccn/labstreaminglayer/issues/30

Here is a citation:
"Unfortunately, as you might be aware, we are no longer offering the SDK. The Muse SDK and research tools have helped make Muse into the bestselling EEG system in the world. They have also required a volume of technical support that has been difficult for us to sustain. As we’ve grown, we’ve struggled to provide the kind of support for developers that we believe our community deserves. For this reason, we’ve had to make the difficult decision to stop actively supporting the Muse software development kit (SDK)."

You say, I'm still holding out hope they will bring back the SDK soon. On which facts is your hope based? "Interaxon stopped actively to support the Muse software development kit (SDK)", in their own words. In the answer I received from the Muse support, there was nothing written that they intend to bring back the Muse software development kit (SDK).

[James]

Hope isn't fact based. Don't forget the rest of what I said : "but in my spare time I'm working on my own SDK."

[Peter Gamma]

That s fine! And don't forget, the best solution is to be free from hope and fears .

[Venryx]

Just wanted to mention that if someone was looking for the old versions of the Muse SDK, libmuse-ios, and libmuse-android, you can find a copy of them here: https://github.com/sccn/labstreaminglayer/issues/30

EDIT: Oh, here's a more direct mirroring, seemingly with more/all of the files available: https://web.archive.org/web/20190703020 ... se.com/sdk

Also, this third-party group appears to be looking into creating their own SDK for Muse: https://petal.tech/sdk-for-muse

@James How is your Mind Monitor app currently accessing Muse data?

Are you using...
1) The old Muse SDK.
2) The custom Muse SDK you mentioned you were building in your free time.
3) Some third-party SDK (eg. the one linked above).
4) No SDK; using lower-level access to the raw Bluetooth data, and parsing it manually.

[paul78]

+1 on the questions from Venryx in regard to what you currently use for Mind Monitor?

Also, is there any API available to get data from a muse headband (model: MU-02) on a Linux PC?
I tried the muse-io under Linux (after compiling all required libraries by hand) and windows 10 and got no results. Never managed to actually connect to a headband, it just keeps search for devices endlessly.

I also bought the Mind Monitor APP but unfortunately figured out that it is of no use for use in our current scenario, because we need to connect to 2-6 headbands and gather data from all of them at the same time. With mind monitor not allowing to select a specific headband to connect to (at least I did not figure out how) there was no way to get six phones / android devices to consitently pair with the same device in an automated.

Anyway we would prefer to skip the step in the middle to have six phones that send data to a central server and rather directly connect to multiple headsets from a single PC (sorry If this is a bit off-topic...basically I wanted to upvote Venryx's questions

[James]

I'm using the Interaxon SDK.

If you have multiple Muses and Multiple devices you just need to power them on in sequence. Power on Muse #1 and load Muse Monitor on phone #1, once paired, power on Muse #2 and open the app on the next phone etc.

99% of my users only have one Muse, so the ability to select between multiple devices isn't something I'm going to implement, sorry.

Regarding Mac/PC/Linux connectivity, technically it's possible, but Bluetooth comms are a terrible minefield on these platforms. I went through 5-6 different Bluetooth LE USB dongles before I found one that would connect to the Muse 2 and even then the data was sporadic. I think it just has too much data and BLE comms are just not something that is used much on these platforms so I imagine they are far behind mobile devices in terms of maturity. I'm speculating, but this may be why a lot of wireless mice and keyboards come with their own wireless usb dongles that use their own proprietary wireless protocols.