OpenViBE forum

Hi,

I unfortunately cannot answer without you telling me which error you got.
I suggest you remove dist and build folders (to start from a clean state) then launch build.sh again. This time, copy the output and post it here as an attachment.

Cheers,

Hi,

to me, it looks like you used the scripts inside sdk/scripts to build the SDK.
From what you write it seems you want is the "full" OpenViBE.
The process to do that is documented in the "README.md" file in main folder.

Can you tell me which process you followed ?

Cheers

Hello, I took the liberty of merging the 2 post, are they are asking for more or less the same thing. Currently if you want to have more than 2 classes with a graz visualisation, you'll have to do some coding. hkn1304 is correct; this is the file that should be modified for 4 classes Graz visualizat...

Hi,

Can you try using this modified acquisition server ?
I compiled a version using the new sdk, bu i unfortunately cannot test it as i don't have a licence for emotiv software.

Cheers,

hi,
There is a tutorial specific to Emotiv for 1.3 : http://openvibe.inria.fr/how-to-connect ... -openvibe/
Please note that it was not tested with Xavier.

Cheers,

hi Thanks for your input. The version you have compiled is a preliminary version of OpenViBE 2.0. This version had not been tested on any fedora. Since then, we currently have a test machine that run fedora 25 x64, so fear not, fedora users are not forgotten. Updated scripts will be available upon 2...

Hi, I believe you should keep both separated. It's easier to debug that way (you can use designer for example). It should also be quicker to develop if you already know how to interface OV with VRPN. The only drawbrack will be that performance will be inferior as you have to transfer data over the n...

Hi,

currenly you can use OpenViBE as command line using the "--invisible" switch.

Note that this will still use a classical scenario file, so you will have to use some kind of network communication and/or file read/write to achieve what you are trying to do.

Cheers,

Hi, it is already possible to hide the gui of OpenViBE using "--invisible" command line switch (use "--help" for more informations). You will also be required to supply a script with "--play", like so openvibe-designer.cmd --invisible --play path_to_your_scenario As for using openvibe on an arduino,...

Hi, The error says that you can't write to the path "C:/Program Files (x86)/openvibe/share/openvibe/scenarios/bci-examples/p300-speller/signals/p300-train-[2017.09.13-15.46.33].ov". This is perfectly normal, openvibe cannot write to "C:/Program Files (x86)/" without admin rights. I would suggest tha...

Hi, I'm afraid i can't give a direct answer to your question, as i'm lacking informations about your setup, however i can give you a few pointers to debug your issue and get additional informations : - Check our troubleshotting guide . It might help you finding out what the problem is. - Try to find...

Hi,

This is not currently planned for OV2.0
This will however likely be possible in version 2.1

In any case, I wouldn't get my hopes too high about a python performance increase due to 64b version, as python doesn't benefit much from it, due to the GIL.

Cheers,

Hi,

You can use box:log(log_level, line_of_text).
Sample script from OpenViBE also suggest that io.write should work.

Cheers,

Hi, The error you are getting is explained in the third line error LNK2038: mismatch detected for '_MSC_VER': value '1800' doesn't match value '1700' in Source.obj Basically it says that you are trying to link something compiled with version 1700 of the Microsoft Compiler (ie VS 2012) against a lib ...

Hi, You actually have the boxes you are talking about; if you did not, you would have gotten a lots of errors in the log window. The boxes you don't find are in fact just renamed for scenario comprehension. Their real name is written above in small letters. So the "Debug: display" box is in fact a "...