OpenViBE forum

Hi, What you put in the OSC address box is up to you. In OSC protocol, all data is send to an ip/port; if you have multiple commands, they are send in the same packet, and you'll use the osc address to differentiate them. That means you just have to choose a name, and use the same one on both sides ...

Hi,

The OSC message box send data using the OSC (Open Sound Control) protocol, so you will have to "decode" it (or more accurately, interpret the data correctly).
There is several OSC library on github that you could use if you don't want to handle decoding yourself.

Hope that helps,

Hi, indeed, you do not need initialize/uninitialize files in python. However, the python scripting box still requires you to do something similar; classes created to be used with python box requires you to define an initialize/uninitialize function. You can see examples of that in python's box tutor...

Hi,

OSC is flagged as unstable, so you'll have to check the "show unstable" checkbox to make it appear.

Cheers,

Hi,

Do you have a specific constraint that requires you to use VRPN ?
If you don't, i suggest sending values with OSC box instead. You'll have to develop client side decoding of OSC, but i believe that it will be easier/faster to implement than using VRPN.

Cheers !

Hi, What exactly are you having trouble with ? You do not know hot to convert the datatypes ? You are having compile time error ? etc Without more precisions or examples, I'm afraid that all i can answer to your question is "Well, convert them". Of course it would be my pleasure to help you, should ...

Hi,

Are you getting the error from a repository in a clean state or did you modify something ?

I suggest you try compiling using the scripts (win32-dependencies.cmd and win32-build.cmd) from a clean repository; tell me if you still have the error in that case.

Cheers,

Hi, From what i see, this seems correct by OSC standard. It use bundle command (23 62 75 6E 64 6C 65 00) followed by informations relative to the commands, things like command size (00 00 00 00 00 00 00 01 00 00 00 10). Then we get an actual command (2F 61 2F 63 00 00 2C 69 00 00 00 00 01), sending ...

Hi,

it seems that you are compiling part of the project in Debug mode, and another part in Release mode. Maybe one of the libs.
After making appropriate correction, please clean your project (using the clean function of visual) to be sure.

Hope that helps,

Hi,

You'll likely want to look at the OSC box. With it you can send a signalor stimulation input over the network.
On the arduino side you would have to develop a udp server to receive that information and process it.

Is it what you are looking for ?

Hi,

Are you sure your receiving application is decoding correctly ?

You could also use OSC, and interpret this "other thing" as 1.

Cheers,

Hi,

There is indeed no timestamp in gdf files.
You can however :

• Calculate it using sampling rate and sample number
• Add a time signal into it with the "Time Signal" box and "Signal Merger" box

Hope that helps,

Hi,

It seems that you are trying to link lib compiled with another version of MVSC compiler.

Did you follow the build guide ?
Microsoft Visual Studio 2013 (or Microsoft Visual Studio 2010) is required to build OpenViBE.

Hope that helps,

You are likely right, I also think this is due to types conversion.

You will have to check how you do the conversion on your application side.

OVTK_StimulationId_Number_00 and OVTK_StimulationId_Number_01 should give you values 0 and 1, respectively.
Could you give me the actual value you get using these stimulations ?