OpenViBE forum

Identifiers, as their name suggests, are used to unambiguously identify objects in OpenViBE. They can be used with any kind of object. Why use Identifiers? This is the preferred way of referring to an object in OpenViBE, especially when communicating between different projects (eg. OpenViBE kernel <...

In order to build my own experiment, I need to give instructions to the subject. One way of doing it would be to display different images when specific simulations arrives. I was going to try to build this box, but maybe someone built a similar box already...? Hi Joan, no such box currently exists ...

Yes there is a compiled version that's still being tested. I'm going to PM you the address though!

Hi, I can't think of an obvious answer to your problems. Re-reading your posts, I'm not too sure what's happening on what machine. Let's concentrate on the XP ones first, which are known to be working with OV. 1/First off, did you make sure DirectX was successfully installed by launching a Direct3D ...

OK, well it'd be nice to fix the problem though ;) What exactly is the problem when drag and dropping a box? Alternately, if you recompile in debug mode (see "building the software" forum category) you'll be able to trace the program yourself. It seems your gtk/gdk installation was altered somehow, ...

For Windows users, there exists a free tool which greatly facilitates source management with Subversion. This tool is called TortoiseSVN and can be found here : http://tortoisesvn.tigris.org/ Its integration with explorer makes it easy to use : http://tortoisesvn.tigris.org/ExplorerIntegration.html

By default, OpenviBE compiles in Release mode. Users wishing to debug the software may want to switch to Debug mode. This can be done by changing the build type in the win32-build.cmd script file (linux-build.cmd for Linux developers): (...) cmake -DCMAKE_BUILD_TYPE=Debug (...) Also, when changing t...

OK, assuming you're using the svn version of OpenViBE, you can update your openvibe-applications/designer/trunc source tree which includes more robust code.

This might fix your problem after a rebuild of the software!

Bug unheard of so far!

the crash message is actually more helpful. am going to make the code more robust & investigate how this pixbuf can be NULL.

This seems to be a Gtk issue. No idea why it used to work on your machine though

First off, I'd suggest lowering the log level to Debug in the configuration manager so we can determine what's going on at the time of the crash. The configuration file is in /share/openvibe.conf (precompiled version) or openvibe-kernel-omk/trunc/share/openvibe.conf (svn version, must build again fo...

OK, does the crash occur upon a specific event/action? (scenario opening, box clicked or dropped in scenario... ?)

Don't uninstall the app for now, I believe that won't help... We'll try and fix the bug

Some testers report occasional crashes of the Designer at startup. It appears this is due to an Ogre3D-related issue on some Linux platforms (depending on what libraries are installed, this problem may or may not occur). Until this issue is resolved, a workaround consists in disabling 3D visualisati...

An archive containing sample scenarios & data can be found here : http://www.irisa.fr/bunraku/OpenViBE/sa ... narios.zip

These scenarios are intended to demonstrate the use of a number of OpenViBE Designer functionalities, and should be of great help for first time users!

Here's a pointer to the slides of the OpenViBE training course that was held in Rennes in January '09 : http://www.irisa.fr/bunraku/OpenViBE/tutorial/P-2009-01-14%20training%20course.pdf This should provide useful info for all plugin developers : general concepts as well as details about plugin deve...