OpenViBE forum

Hello all.

Firstly, congratulations on the recent 0.6.0 release of OpenViBE.

Last month on the OpenEEG mailing list this message mentioned an Emotiv EPOC EEG headset was on order by the main development team, with the intention of producing a driver for OpenViBE:

From: Yann Renard <yann.renard@ir...> - 2010-03-22 09:58
Re: [Openeeg-list] Emotiv EPOC recommendations

Regarding the Emotiv headset, we have purchased one and should receive
it in the next few weeks. I'll come back to this list has soon as it is
integrated in OpenViBE, which is LGPL.

I was wondering what the status of this driver might be currently? It was not mentioned in the "What's coming in the next release(s)" section of the 0.6.0 release announcement (but other drivers were).

Has the headset arrived and any development work begun?

I have the hardware and a basic Developer SDK but would be willing to upgrade to their "Research" level for access to the Raw EEG signals in order to help with the OpenViBE integration work - even if only in a QA/Tester capacity.


As an aside, I am lead developer on an Open Source project geared towards K-12 student projects to build, control, and race robots assembled from LEGO Mindstorms via EEG. It is my desire to replace dependence on the closed Emotiv SDK in favour of OpenViBE routines, in order to ensure hardware independence in the long term.


Cheers

Steve Castellotti

Hello cycon, and thank for your interest with the project !

Indeed, we plan to have an Emotiv driver for openvibe as soon as possible.
The problem is that we don't received the headset yet.
Emotiv had a "paypal problem" last time we tried to order, and I don't really know where our order is. Lost in the internet maybe.

We didnt mentionned Emotiv driver in the last release because we don't know when it will be possible to actually do something about that.

I'm keeping the pressure on our purchase department...

I'll keep you posted, thanks for your patience.

Laurent

lbonnet wrote:Indeed, we plan to have an Emotiv driver for openvibe as soon as possible.
The problem is that we don't received the headset yet.

Any updates Laurent?

Either way, I will be bringing my headset to next week's BCI Conference in Monterey. I noticed you are attending and we're in at least one of the same workshop groups together. Perhaps you can help steer me in the right direction towards contributing a driver myself.


Cheers

Steve Castellotti

Hi Steve,

Any updates Laurent?

Unfortunately, no news :'(
Our purchase department has not a clear view of our order. It's somehow lost on the Internet.
I won't bother you with details, but for now, I'm just waiting... and mailing... and waiting...

Either way, I will be bringing my headset to next week's BCI Conference in Monterey. I noticed you are attending and we're in at least one of the same workshop groups together. Perhaps you can help steer me in the right direction towards contributing a driver myself.

Nice ! Of course I can help you, and if you want to contribute it's even better

See you soon in California !

Laurent

lbonnet wrote:

Either way, I will be bringing my headset to next week's BCI Conference in Monterey. I noticed you are attending and we're in at least one of the same workshop groups together. Perhaps you can help steer me in the right direction towards contributing a driver myself.

Nice ! Of course I can help you, and if you want to contribute it's even better

See you soon in California !

Laurent

It was certainly a great time meeting you all at the conference!

Just checking in, I have been pretty busy continuing work on my own project, but am still interested in contributing to OpenViBE when I'm a little further down the track.

Not sure if you guys picked up on it, but BCI2000 recently produced a first-draft driver for the Emotiv EPOC headset:

http://www.bci2000.org/wiki/index.php/C ... ons:Emotiv


I'm not going to go anywhere near the potential licensing concerns between examining their work as an aid for developing an OpenViBE driver, but it might be useful to someone with a more clear understanding of what sort of restrictions and conflicts would apply (and its always nice to see progress on support of consumer-grade equipment).


Cheers

Steve

Hi Steve !

It was nice to meet you at the Conference ! I hope you're doing well with your project

Not sure if you guys picked up on it, but BCI2000 recently produced a first-draft driver for the Emotiv EPOC headset:

http://www.bci2000.org/wiki/index.php/C ... ons:Emotiv

Thanks for the link !
I see they restricted this plugin to Emotiv Research Edition. The Openvibe driver will also be limited to this SDK and the superior SDKs (I think the Research Edition is about $750 - headset included).

On our side, we just received the headset (Alleluia) and the license for the SDK !
I will start developing the driver as soon as possible.

I'm not going to go anywhere near the potential licensing concerns between examining their work as an aid for developing an OpenViBE driver, but it might be useful to someone with a more clear understanding of what sort of restrictions and conflicts would apply (and its always nice to see progress on support of consumer-grade equipment).

I am not a specialist on the BCI2000 platform,but I'm pretty sure that we won't be able to use this code, legally and technically But the Emotiv SDK seems quiet clear, and I hope that the development of the driver won't take too much time. Wait and see...

Best Regards

Laurent

Hi Everyone.

I'm just another person interested in driver for Emotiv EPOC.
I'd like to know what's the status now?

Hi ilja.kuzovkin, and welcome on board !

The Emotiv EPOC driver for OpenViBE is running nicely on our latest tests.
It will be integrated in the next release of the software, scheduled for the end of september.

If you or Steve want to give it a try, you can build the branch openvibe-application/acquisition-server/branches/wip-lbonnet-emotiv
NB : This branch is based on the latest trunk, which uses the new Gtk builder dependencies.

If you have any problem building/using the driver, please tell me !


Regards

Laurent

!!!!! [POST EDITED - 01 dec 2010] !!!!
The procedure explained below is not possible anymore.
The Emotiv driver has been integrated in the main trunk
Check here for more details.
--


The emotiv driver will be soon integrated in the project trunk. If you want to try it now, here is the procedure :

0. NB : The driver only works on windows, and needs the Emotiv SDK Research Edition

1. Checkout the source code using SVN.
Check this doc for the procedure.
I assume you are on windows, thus you can install TortoiseSVN (a user-friendly application to use SVN). Please note that you need to checkout the project in a new folder with no whitespace in its path (example : c:/openvibe/repository is good, c:/My documents/openvibe repository is bad).
As you are not a developer, the address to checkout from is simply : svn://scm.gforge.inria.fr/svn/openvibe/trunk. You just need to right click the folder, and do a "SVN checkout" with this address.

2. install the dependencies. You must use the install_dependencies executable

3. Copy win32-init_env_command.cmd-skeleton and rename it to win32-init_env_command.cmd

4. modify the new file win32-init_env_command.cmd on line 38 must be : 5. execute win32-build.cmd. It should build everything, including the emotiv branch.
In this step, when the script tries to build the emotiv driver, it checks if you have the Emotiv SDK installed on your computer. This SDK must be installed in the folder C:/Program Files/Emotiv/Emotiv Development Kit_v1.0.0.3-PREMIUM or in C:/Program Files/Emotiv Development Kit_v1.0.0.3-PREMIUM.

6. execute dist/test-acquisition-server.cmd

Tell me if you have any problem !

Laurent

In addition to what Laurent said, of course, you will need Visual C++ Express 2008 in order to compile the software

Yann

Thank for existing guys!

Hi guys!
I tried to see a simple signal viewer but this is what happened

Setting environment for using Microsoft Visual Studio 2008 x86 tools.
[ INF ] Created kernel loader, trying to load kernel module
[ INF ] Kernel module loaded, trying to get kernel descriptor
[ INF ] Got kernel descriptor, trying to create kernel
[ INF ] Adding configuration file(s) [../share/openvibe.conf]
[ INF ] Adding configuration file(s) [C:\Documents and Settings\blondpc/openvi
be.conf]
[ INF ] Adding [../bin/OpenViBE-plugins-*.dll]
[ INF ] Added 2 (0x2) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-acquisition-dynamic.dll]
[ INF ] Added 6 (0x6) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-classification-dynamic.dll]
[ INF ] Added 1 (0x1) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-classification-gpl-dynamic.dll]
[ INF ] Added 1 (0x1) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-feature-extraction-dynamic.dll]
[ INF ] Added 13 (0xd) plugin object descriptor(s) from [../bin/OpenViBE-plugi
ns-file-io-dynamic.dll]
[ INF ] Added 8 (0x8) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-samples-dynamic.dll]
[ INF ] Added 25 (0x19) plugin object descriptor(s) from [../bin/OpenViBE-plug
ins-signal-processing-dynamic.dll]
[ INF ] Added 19 (0x13) plugin object descriptor(s) from [../bin/OpenViBE-plug
ins-signal-processing-gpl-dynamic.dll]
[ INF ] Added 16 (0x10) plugin object descriptor(s) from [../bin/OpenViBE-plug
ins-simple-visualisation-dynamic.dll]
[ INF ] Added 10 (0xa) plugin object descriptor(s) from [../bin/OpenViBE-plugi
ns-stimulation-dynamic.dll]
[ INF ] Added 18 (0x12) plugin object descriptor(s) from [../bin/OpenViBE-plug
ins-stream-codecs-dynamic.dll]
[ INF ] Added 1 (0x1) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-streaming-dynamic.dll]
[ INF ] Added 4 (0x4) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-tools-dynamic.dll]
[ INF ] Added 2 (0x2) plugin object descriptor(s) from [../bin/OpenViBE-plugin
s-vrpn-dynamic.dll]
[WARNING] Registery key Software\VB and VBA Program Settings\Brain Quick - Syste
m 98\EEG_Settings is not initialized
[ INF ] Connection succeeded !
[ INF ] Connecting to device [Emotiv EPOC]...
[ INF ] Received new connection...
[WARNING] Dropping connection - acquisition is not started
[ INF ] Starting the acquisition...
[ INF ] Now acquiring...
[ INF ] Stoping the acquisition.
[WARNING] After 4.683 seconds, theorical samples per second does not match real
samples per second
[WARNING] Received : 600 (0x258) samples
[WARNING] Should have received : 600 (0x258) samples
[WARNING] Drift was : 0 (0x0) samples (0%)
[WARNING] The driver did not try to correct this difference
[WARNING] Please submit a bug report (including the acquisition server log fil
e or at least this complete message) for the driver you are using
[ INF ] Disconnecting.
[ INF ] Connection succeeded !
[ INF ] Connecting to device [Emotiv EPOC]...
[ INF ] Received new connection...
[WARNING] Dropping connection - acquisition is not started
[ INF ] Disconnecting.

and so on...
under the emotiv's control panel everything was fine (green).

Hello,

I am currently working on a something with really close deadline so I'm afraid you will have to wait few days for my feedback about your problem.
I will do my best to help you, but I just can't now sorry...

Best regards !

Laurent

Dear MarcoRotonda,

just start the acquisition before trying to connect the designer.

Kindest regards,
Yann

Yep!
Sorry !!!

Works GreaT

Thanks!!!