OpenViBE+OpenBCI Ganglion

2»

Comments

  • I HAVE DONE THAT! As I said two times already, there is no problem with the data stopping in Python. The problem are the values of the EEG that show in the GUI but are delayed in openvibe and python. That is my problem. I am using ganglion, and I dont care if it works with a sintetic signal. I have no use for a sintetic signal. If there is no lag, that doesnt mean that there is no problem. If you cant help me, dont claim that I am reporting problems that are not there (WHEN THERE CLEARLY ARE).

  • retiututretiutut Louisiana, USA
    edited October 2019

    If you don't care to do what I asked when I'm trying to help you, you can help yourself! This goes against community standards and is unacceptable! I'm not going to argue with you when you choose not to listen and follow directions.

    The point I made with my screen recording is that when the data stops in the GUI, the data stops in Python.

    Please make a recording just like mine and share it:

    • Start GUI in synthetic mode
    • Stream TimeSeries over LSL
    • Start screen recording
    • Start data stream
    • Stop data stream
    • Start data stream
    • Stop data stream
    • Stop screen recording

    I don't want to see data just streaming with a delay. I want to see the data stream stopping in 2 applications at the same time. If they start/stop at the same time, there is no lag!

    Starting to get frustrated with people claiming there is an LSL delay without trying to replicate my results! I get the same results over and over across different applications.

    The code is almost exactly the same for streaming all data types over LSL. So there is no reason, from a coding standpoint, why one data type would have a lag and another would not. Think about it!!!

Sign In or Register to comment.