Measurement object for AVETO.app Visualization to export video streams to .avi files
View Usage
·
Report Bug
·
Request Feature
Table of Contents
Object: Exporter Object
Name: Video Exporter
Input: Native Image Connector named „IMAGE_RGBa8“
Output:
| Container | AVI |
|---|---|
| Codec | MJPG |
Properties:
| Property Name | Type | Default | Description |
|---|---|---|---|
| Allow Encoding | bool | true | true: allow encoding false: stop encoding |
| Frames per second | uint32_t | 25 | FPS of the exporting video; every incoming packet is one frame |
| Output Filename | std::string | „Output“ | Name of the exporting video |
| Output Directory | std::string | „C:\“ | Loaction to the output directory |
| Use Numeration as suffix | bool | true | true: Add counter to the end of the filename false: Use only „Output Filename“ property as name |
| Timeout[ms] | uint32_t | 2000 | Maximum number of milliseconds between incoming packages. If the delay is greater the export ends. |
By default after creation when data packets first come in over a connection they will be exported. After the export of a video is finished the property Allow Encoding has to be manually set to true to start another video export or a new connection has to be established.
Video export ends automatically if the delay between two packets is greater than the value of proptery Timeout[ms] or the connection to the input connector is severed.
When property Use Numeration as suffix is true the exported video on default settings is C:\Output001.avi. If it is false the video is C:\Output.avi.
Note If no file can be generated e.g. due to missing permissions at the target location there will be no warning. The only indication is that the counter gets incremented for every incoming package that could not be written and then the first working export after will start at a higher number than 001.
3rd party components:
OpenCV 4.5.3
Used binary:
opencv_world453.dll
Clone this repository and make sure you fulfill following requirements
- Installed AVETO.app >= 2.4.0
- Set AVETO_SDK_PATH as environment variable which by default points to the folder
C:\Program Files\b-plus\AVETO.app\sdk - Installed Windows SDK-Version 10.0.17763.0
- Installed OpenCV 4.5.3
- Install AVETO.app
- Clone the repo
git clone https://github.com/bplus-group/aveto_mo_videoexporter.git
- Install OpenCV 4.5.3. and set the environment variable to the installation location
- Adapt the include and library directories in the Visual Studio Solution that it finds the OpenCV dependencies
- Build the project
- Copy VideoExporter.dll to your AVETO MO directory (default:
%USERPROFILE%\Documents\AVETO\measobj\)
Right-click in the node graph editor of the configuration manager and choose Exporter Objects -> Video Exporter as seen below.
By clicking on the Video Exporter MO the output directory and output filename can be edited in the property list.
Note
Make sure to have write permissions to the output directory. C:\ may not work!
After starting a recording (with a playback) or by connecting to a live source the video source will be converted as an .avi-file to the desired location.
If you have a suggestion that would improve this, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".
Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/NewFeature) - Commit your Changes (
git commit -m 'Add some NewFeature') - Push to the Branch (
git push origin feature/NewFeature) - Open a Pull Request
Check License information. See LICENSE for more information.