mediamonks/spinnaker-spout-cinder

Spinnaker Spout sender in Cinder

Publishes the feeds from all connected FLIR (Point Grey) cameras to Spout. Tested with Blackfly BFLY-PGE-31S4C and BFLY-PGE-09S2C cameras.

Download

Download the executable here. Before running it, see the instructions below.

Running

• First download and install the 64 bit Spinnaker SDK from FLIR/Point Grey (requires creating an account):
  • Make sure to choose to install the full SDK (don't choose Camera Evaluation)
  • For Visual Studio Version, choose Visual Studio 2015 instead of 2013
• Run this app

Developing

Note about submodules

When cloning this repository, make sure to recursively check out all submodules. Cinder is included as a submodule and itself contains submodules.

You can use git clone --recurse-submodules on the command line or the submodule options of your GUI git client.

Note when working with a Visual Studio version higher than 2015

You will need to have the VC++ v140 toolset installed. This can be done for instance with the Visual Studio installer (for instance by going to Programs and Features in the Control Panel, selecting Visual Studio and clicking Change), where you can choose to Modify the installation and check the VC++ v140 toolset checkbox.

Before compiling the binary

• Only build targets Debug and Release are tested. However Debug_ANGLE may be selected by default, in that case you need to change it.
• Download and install Spout from: http://spout.zeal.co/download-spout/
• Make sure that this repository's bin64 folder is in your PATH environment variable (don't forget to restart Visual Studio after modifying the PATH).
• If you have the Spinnaker SDK installed while developing, make sure you don't have a different version installed than the dlls in this repo's bin64 folder (currently 1.20.0.15) as this may cause conflicts trying to access the camera
• If you have the Spinnaker SDK installed, make sure the bin64 folder of this repo is above the folders of the SDK in the PATH variable, otherwise you may get a procedure entry point location error.

Setting logging properties

The only way to get rid of a logging configuration error message on every launch seems to be to configure an environment path variable GENICAM_LOG_CONFIG_V3_0. You can point it to \logconfig\Logging.properties

Distributing the binary

When distributing the exe, make sure the dlls in the bin64 folder are next to your exe, and there is an assets folder containing a settings.xml next to the exe.

Misc

Consider donating to Spout: http://spout.zeal.co/download-spout/