4 ms·
This looks perfect for research or OS programs. But you can forget commercial applications without the consent of emotiv. Also, perhaps someone can clarify thi
by hbt 16y ago
This looks perfect for research or OS programs. But you can forget commercial applications without the consent of emotiv.
Also, perhaps someone can clarify this for me. This doesn't guarantee you will end up with something better or similar to emotiv.
After determining which bytes correspond to which signals, do you have to write the algorithm for pattern recognition? do you have to reverse engineer the whole SDK or is it just a matter of calling the existing/proprietary algorithms using the signals?
Anyway, I think this will force them to accelerate their development for the Linux platform and perhaps be more open about it.
I'm not sure if they're not open about their development because they're stuck (I haven't seen any major improvements in their videos from 2008 to now... same stuff) or if they're scared from competition because they don't have the resources.
If they can recognize what a bunch of _very_ ambitious developers can do for free, why keep this thing locked?
- daeken 16y agoOnce the sensor data is completely decoded (currently digging through that with the advice of several people in the EEG field), the reversing is really over. From there, you can write your own processing libraries or simply utilize something existing, such as OpenViBE. Part of Emokit will be an acquisition module to feed data into OpenViBE, so that'd be the path of least resistance for most cases.
- hbt 16y agoThanks for replying. I didn't know about OpenViBE. In your opinion, how is it compared to emotiv SDK? (I'm referring to the API, quality and things you can do with it -- with minimal coding)