Hi,
I have troubles running OptiCapture.exe (OptiTrack DirectShow Filter) which I downloaded from naturalpoint.com. Due to a buffer overrun, the program crashes immediately after it has been started. Unfortunately, debugging is not possible (OptiCaputure.exe does not come with any debug info compiled in).
I am using OptiTrack SDK 1.3.037 beta 1, but I also experienced the same problem with the offical release versions 1.3.034 and 1.3.035. The camera is a flex:v100 that is connected to a Win XP professional machine. MS Visual C++ 2005 Redistibutable is installed (Version 8.0.50727.42) on that machine as well as the "OptiTrack DirectShow Filter". MS Visual Studio 2008 Professional is also installed.
Did anybody experience the same problem? And more importantly, have you been able to solve it?
I appreciate any help, comments, hints,
HerrJeh.
OptiCapture.exe crashes
Re: OptiCapture.exe crashes
Try using OptiTrack SDK version 1.1.034, as the application may need to be recompiled with the latest version of the SDK.
Re: OptiCapture.exe crashes
Hi,
the OptiTrack SDK version 1.1.034 fixes the problem partially, i.e. the DirectShow Filter does not cause buffer overruns anymore and I can see the video output from the felx:v100 in AMCap and in OptiCapture.
However, my own application does not work properly with version 1.1.034 anymore. This is because of two issues:
(a) Camera.FrameAvailable() is not called anymore (with version 1.3.035 it used to be invoked whenever new blobs are recognized by the camera.
(b) I make use of the ClearBlockingMask(), AddBlockingRectangle() and UpdateBlockingMask() functions that had been introduced in SDK version 1.3.035.
Would it be possible for you to recompile the "OptiTrack DirectShow Filter" (OptiTrack.ax) with OptiTrack SDK version 1.3.035 (or 1.3.037 beta 1) and publish it on your website?
Could you also add some info regarding this issue on your download site (at the moment, the website claims that OptiTrack.ax works with "1.1.034 or higher" which apparently is not true).
Kind regards,
HerrJeh.
the OptiTrack SDK version 1.1.034 fixes the problem partially, i.e. the DirectShow Filter does not cause buffer overruns anymore and I can see the video output from the felx:v100 in AMCap and in OptiCapture.
However, my own application does not work properly with version 1.1.034 anymore. This is because of two issues:
(a) Camera.FrameAvailable() is not called anymore (with version 1.3.035 it used to be invoked whenever new blobs are recognized by the camera.
(b) I make use of the ClearBlockingMask(), AddBlockingRectangle() and UpdateBlockingMask() functions that had been introduced in SDK version 1.3.035.
Would it be possible for you to recompile the "OptiTrack DirectShow Filter" (OptiTrack.ax) with OptiTrack SDK version 1.3.035 (or 1.3.037 beta 1) and publish it on your website?
Could you also add some info regarding this issue on your download site (at the moment, the website claims that OptiTrack.ax works with "1.1.034 or higher" which apparently is not true).
Kind regards,
HerrJeh.
Re: OptiCapture.exe crashes
We don't have the new version of the DirectShow filter posted as a standalone download yet, but you can get it on your system by installing the latest version of Arena.
Before running the Arena installer make sure to de-install the previous version of the DirectShow filter.
The new DirectShow filter does not rely on the OptiTrack SDK, however the same restriction does apply - do not run OptiTrack based applications at the same time as the DirectShow filter.
Before running the Arena installer make sure to de-install the previous version of the DirectShow filter.
The new DirectShow filter does not rely on the OptiTrack SDK, however the same restriction does apply - do not run OptiTrack based applications at the same time as the DirectShow filter.