For 7.0.0.52 integrations, Geutebrück uses a variable FPS that does not include metadata with an exact timestamp per frame. This may result in a number of side effects in BriefCam, including REVIEW closeup clips and original videos playing in slow motion and the RESPOND alert original video timestamp and bounding boxes being offset. To solve this issue, the integrator should configure both the live and archive streams to be at the same resolution and configure the cameras to a constant FPS.

For 7.0.0.52 integrations, when requesting an on-demand request (REVIEW) on a Geutebrück integration, the fetching occasionally reaches the default timeout (120 seconds) and causes the fetching to fail. To solve this issue, increase the fetching timeout in the BriefCam Administrator Console’s Fetching.TimeoutInSeconds setting and restart the Fetching service.