OpenViBE Bug Tracker - openvibe
View Issue Details
0000070openvibe[openvibe-plugins] feature requestpublic2011-04-22 08:352016-12-28 13:40
jporcher 
 
normalfeaturealways
newopen 
0000070: Be able to run OpenViBE from a single process
Today, to run a BCI experiment with OpenViBE, you must start both the acquisition server and the Designer. Having those two processes makes it possible to:
- Run each on a different machine
- Guarantee that slow signal processing in the Designer does not impact the acquisition system process

This is really great and is a perfect architecture for BCI.

But, this out-of-process architecture could be optional. Once your BCI scenario is tested and validated, once you know it does not overload the system. If you know acquisition could work in the same process without being slow down (few channels, low frequency....). It would be really nice if you could have a way to run a BCI experiment using one and only one process, one and only one GUI.

I'm thinking of situations where OpenViBE would be used in a medical environment. Then, OpenViBE could be used by people not familar with computers: having to run two programs, having to configure them separetly, and then starting each one (in the right order), is source of errors and most likely those end users will fail in starting the experiment correctly.

Would it make sens to consider having a "Acquisition Server" box in the Designer? It would have the same outputs as the "Acquisition Client" box. Configuring this Box would be like configuring the acquisition server (same dialog, but no Start/Stop button). When Scenario is started, this box is started like any other and this actually starts a server acquisition thread.

It's just a matter of reusing the acquisition server code to make it be a standard box able to send data (as a file reader boxe does)
No tags attached.
Issue History
2011-04-22 08:35jporcherNew Issue
2016-12-28 13:40jtlindgrProjectopenvibe-plugins => openvibe

There are no notes attached to this issue.