OpenViBE forum

Hi,

You can surely use these datasets to validate your tool.

Cheers,
Thomas

Hi Jeff, The .vhdr file (that you can open in a text editor) contains a DataOrientation field. From what I found online, its value can be VECTORISED or MULTIPLEXED. OpenViBE only supports the MULTIPLEXED format, meaning: "The data for all channels are written sequentially in one line for one samplin...

Hi, This is puzzling! The scenario is very simple, and I have tried it on two different machine with OpenViBE 3.5.0 and the vhdr files are generated as expected. I'm short of ideas without seeing more. If you don't manage to get it working, you can drop me an email (http://openvibe.inria.fr/contact/...

Hi Jeff, You should be able to read the BrainVision format with OpenViBE using the BrainVision Format File Reader. You can change scale settings by double-clicking on the SignalDisplay box to access its settings. You can also change them when the scenario is playing by clicking on the magnifier at t...

Hi Jeff,

I guess you meant OpenViBE 3.5.0 ?

It's difficult to understand what goes wrong exactly and I did not manage to reproduce the issue you are facing.

Could you share your scenario, and simple-sinus.ov file so that I can try reproducing the issue ?

Thank you,

Thomas

Hi Jeff, What version of OpenViBE are you using ? In order to understand if the problem comes from the location, or the actual writing, I would set the output file in the BrainVisionWriter box to a full path file. This way you will know it's a box issue if the file doesn't appear where you want to. ...

Hi Filippo, Thanks for the detailed post. I could reproduce the issue you are facing, and there is a way for OpenViBE to recognise your stimulations. When using the BrainVision Writer box, you need to provide a "Marker to OV Stimulation dictionnary" file (I'll detail the format below). Indeed, the R...

We are pleased to announce the release of OpenViBE-3.5.0 ( download ). This release brings a NEW Driver: Shimmer3 GSR+ physiological sensor As long as some updates and fixes: BrainProducts actiCHamp driver setting interface fixed ANTNeuro EEGO SDK updated to support the EEGO mini-series 24 channel T...

Hi Nathan, Thanks for the new logs. Although Python is detected and the boxes are built, the OpenViBE build is failing because of the Signal Flattener code (from the tutorial I guess ?). The fact the the build is interrupted could be the issue. Can you fix the build error, have the build complete an...

Hi Nathan, Thank for the build logs. What I see is that both the Python3 and Polybox have been built, that's why they exist and the Designer tries to load them. I can see the python version used is installed from Anaconda, and I have heard of issues finding python when installed from Anaconda... Cou...

Hi, @Jedi_monk, the Unity application hello-bidirectional that EvheMary is trying to use could be a good starting point to understanding how to send from Unity to LSL. It is similar to the hello-sender application (that only sends), and you can find it here. @EvheMary, I think I have a solution to y...

Hi Jedi_monk, You can send markers from Unity to the OpenViBE designer using the LabStreamingLayer library (LSL). There is a wrapper around it called LSL4Unity, and an OpenViBE fork for it. You can see how it is used here to send markers to OpenViBE in this exemple project The scenario that interact...

Hi Nathan,

Would you be able to share your build logs ?

The best would be the logs of a fresh build, running the following:
I hope to find information in there.

Thank you,
Thomas

Hi, Thanks for sharing the scenario. The issue I was worried about is actually not happening here, and the scenario seems fine. If I understand well, you are sending the stimulations from OpenViBE to Aurora, via the LSL Export Box, which seems to be sending way too many stimulations, right? Could it...

Hi Lisa, In the controller script, there is a using directive "using LSL4Unity", which contains the liblsl class. I'm guessing LSL4Unity is therefore not present (although it should have triggered an error on the using directive before the use of liblsl). It should be in the following folder: Assets...