Capturing video from a capture card
"Blank" frame (blank-picture)
For a correct source switch to the previous one upon its disconnection from the capture card, TrueConf Room recognizes the status signal from the capture card.
If the capture card does not support device connection status detection, TrueConf Room provides the option to configure a blank frame, which is used to detect inactivity in this case.
How it works
When launched, the program reads all reference files from a specific folder.
Each frame from the capture card is downscaled to 128×128 and compared against reference images based on brightness, image "structure", and other parameters.
If the frame matches the reference by at least one of the features, the card is considered to be transmitting no image (a blank frame).
Setting up a "blank" frame
For TrueConf Room to be able to detect a blank frame, the following is required:
Connect the capture card without displaying the image (disable the signal source).
Connect a keyboard to the PC where TrueConf Room is installed
Take a screenshot of a blank frame from the capture card. The image file must meet the requirements (this can be done, for example, in the Video settings section).
Place the file in the
../TrueConf/Room/captureCardsfolder.Restart TrueConf Room.
Check the log files.
Image requirements
Common raster formats are supported:
| Format | Extensions |
|---|---|
| PNG | .png |
| JPEG | .jpg, .jpeg |
| BMP | .bmp |
| GIF | .gif |
| Other | TGA, PSD, PNM, HDR |
The file must be a regular image. Do not use text files, Word/Excel files, compressed archives, etc. — they are not recognized as images.
Properties of a suitable image:
| Parameter | Requirement |
|---|---|
| Minimum size | at least 128×128 on each side |
| Maximum size | no more than 10000×10000 on each side |
| Maximum file size | no more than 10 MB |
| Recommended size | from 128×128 to 1920×1080, preferably in the same resolution as the map frame |
Any image is automatically scaled down to 128×128 for comparison, so the exact resolution is not critical — just make sure to meet the minimum and maximum requirements.
The image must not be monochrome (a solid fill of a single color). Such files are skipped and excluded from the comparison.
Detection threshold
In the file name, you can specify the matching threshold using the acc token followed by a number (case insensitive, with _ or - placed before the token):
| File name | Threshold | What does this mean |
|---|---|---|
stub.png | 80 (default) | standard precision |
stub_ACC90.png | 90 | the frame should almost match the reference |
stub_acc85.png | 85 | compromise option |
dexpAnycast_ACC91.bmp | 91 | an example that is initially located in the application folder |
How to choose the threshold:
- Frequent false positives (a regular frame is mistakenly considered "empty") -> increase the number, for example,
acc95. - The feature does not work (the empty frame is not recognized) -> decrease the number, for example,
acc75.
If the acc token is missing or written incorrectly, the default threshold of 80 is used. The number must be between 0 and 100.
File location path
The captureCards folder is located at the following path:
Windows:
C:\Program Files\TrueConf\Room\captureCardsLinux:
/opt/trueconf/room/captureCards
Placement rules:
| Where is the file located | Who is it for |
|---|---|
Right in the captureCards/ folder | general reference - checked for all capture cards |
In the subfolder captureCards/<identifier>/ | reference for one specific card only |
Subfolder for specific devices
To avoid conflicts when comparing blank images from different capture cards, you can create a separate folder named after the device identifier in the vid#pid format (case-insensitive) to store dedicated blank screens for specific devices. Examples of already used names: 07ca#0110, 17ef#7219, 17ef#722f.
How to find your vid#pid:
Windows: → . The string looks like
USB\VID_07CA&PID_0110, and the name of the subfolder is07ca#0110.Linux: the
lsusbcommand showsID 07ca:0110→ the subfolder name will be07ca#0110.
If the ID is unknown, use a generic reference by placing the file directly in ../captureCards.
Log files for checking the operation
After launching the program, the log should display a line similar to the following:
[BlankPicture] Loaded 3 high-priority and 1 low-priority capture card stubsSearch for the [BlankPicture] substring
high-priority— reference files in subfolders (for specific devices);low-priority- general reference files (in the root of the folder).
If the reference image fails to load, a [BlankPicture] warning with the reason will appear in the log: unsupported format, image too small, solid-color image, etc.
| Platform | Path to the TCR logs folder |
|---|---|
| Windows | %USERPROFILE%\AppData\Local<Const name='company-name'/>\Room\logs\ |
| Linux | ~/.config/trueconf/room/logs/ |
Common issues
The log does not contain the
Loaded ... stubslineMake sure that the
captureCardfolder exists and is not empty.The log shows the following message:
unsupported format or corruptedMake sure that the file with the empty frame is in an image format.
The log entry
Image dimensions too smallMake sure that the file is of the appropriate size.
In the log
Skipping uniform stubThe reference file of the empty frame was read as a solid color.
Empty frame is not detected
The reference image detection threshold is probably too high.
A regular frame is defined as "empty".
Make sure that the detection threshold of the reference image is high enough.