OpenViBE Bug Tracker - openvibe
View Issue Details
0000162openvibebug reportpublic2014-10-16 14:592015-02-27 14:41
zstas_mks 
jtlindgr 
normalmajoralways
resolvedfixed 
x86_64Windows7
0000162: "Signal display" box works incorrect with data from MCS NVX amplifier driver
We tested OpenViBE acquisition server v0.17.1 with MCS NVX amplifier driver and OpenViBE Designer worked correct, but using the same driver with OpenViBE v0.18 showed the next issues:
1) We tested Acquisition server v0.18 with MCS NVX amplifier driver with 36-channel amplifier. An external signal generator was connected to the first channel and all other channels was not connected at all. Everything seemed ok (figure 1). But when we disconnect the generator from the first channel and connect to any another (for example to the second), we don't see any signal in "Signal display" box and OpenViBE Designer console throws message: "(openvibe-designer.exe:3316): Gdk-WARNING **: gdkdrawable-win32.c:1352: Polyline failed ..." (figure 2).
2) If some channel is not connected to the amplifier, the driver sends INT_MAX sample value. We changed it to the NaN value. Then, if run the test scenario with all the channels disconnected, everything seemed to be ok (figure 3). But if connect some channel, acquisition server starts to send OVTK_GDF_Incorrect and OVTK_GDF_Correct events (figure 4). If disconnect, it stops.
Changing the "NaN value replacement" parameter has no effect.
 
No tags attached.
zip Screenshots.zip (583,623) 2014-10-16 14:59
http://openvibe.inria.fr/tracker/file_download.php?file_id=27&type=bug
Issue History
2014-10-16 14:59zstas_mksNew Issue
2014-10-16 14:59zstas_mksFile Added: Screenshots.zip
2015-02-12 10:10jtlindgrAssigned To => jtlindgr
2015-02-12 10:10jtlindgrStatusnew => assigned
2015-02-27 14:41jtlindgrNote Added: 0001195
2015-02-27 14:41jtlindgrStatusassigned => resolved
2015-02-27 14:41jtlindgrResolutionopen => fixed
2015-02-27 14:41jtlindgrNote Edited: 0001195bug_revision_view_page.php?bugnote_id=1195#r21

Notes
(0001195)
jtlindgr   
2015-02-27 14:41   
1) OpenViBE doesn't support runtime removal of channels. The correct way to address this is for the server driver provided by MCS to send e.g. a zero signal on the channels that it has declared but that have vanished runtime. If this is not the case, we are happy to accept a patch.
2) This should be fixed now. The server was unintentionally sending too many stimulations. In its correct behaviour, it sends OVTK_GDF_Incorrect when a NaN segment starts, and OVTK_GDF_Correct when the NaN segment has ended.

Thank you for the bug report!