-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LSL with Open Ephys Acquisition Board and Kinect 2 #60
Comments
The Kinect is, in fact supported, but the project is a bit of a stub (https://github.com/labstreaminglayer/App-KinectMocap/tree/09675fabb2dd8be15e5bacde535fafd397c25ae7). The binaries are available in the old apps archive here: ftp://sccn.ucsd.edu/pub/software/LSL/Apps/Microsoft%20KinectMocap-1.10.zip. I am not sure about Kinect 2. The Open Ephys is not supported, but their software is completely open source and written in C++. I took a quick look at the filter node project and it looks like it would be fairly straight forward to forward incoming data to LSL (https://github.com/open-ephys/plugin-GUI/blob/master/Plugins/FilterNode/FilterNode.cpp#L260-L270). I'd guess the hard part would be configuring the LSL outlet according to the device and matching it all up in the gui. |
I wrote this LSLOutlet plugin for Open Ephys a while back and it has been used to acquire LFP data for several publications already. |
In our system we use PulsePal driven by Simulink (in Matlab) to send stimulation commands and this signal can be piped into LSL as well. For the acquisition we used Open Ephys->LSL and everything gets saved into an .xdf file. That being said, you may be able to drag a stimulation source into the Open Ephys gui and connect it to a second LSL outlet, I never tried that but it seems possible. pubs: |
Hello!
I want to use LSL with an Open Ephys Acquisition Board (ideally two at a time) and Kinect 2. I couldn't find these devices in the supported device list. Is there a method to use them together anyway?
The text was updated successfully, but these errors were encountered: