Symptom: exacqVision Server crashes when connecting to a Samsung SPE-100/400 using the native Samsung plugin. <br> Problem: This encoder is only supported for use with the Onvif plugin (device type). Additionally, the device firmware only supports HTTP version 1.0 but Live555 defaults to 1.1. <br> Solution: Connect to the device with the Onvif device type… Continue reading Samsung SPE-100/400 Causes Server Crash
Tag: Samsung
Settings for motion detection sensitity on Samsung cameras may appear different when deleting and re-adding camera
Description exacqVision displays a value 1-100 for motion sensitivity. The camera itself only uses a 1-10 scale. When the user sets the sensitivity to 23, the actual value maps to 2, but the GUI still displays 23. If the camera is deleted and re-added, the sensitivity would display 20, rather than 23. <br>
Create custom multistreams using profiles for Samsung cameras
The parameters of secondary streams (multistreams) that can be created in exacqVision are defined by the stream profiles defined in Samsung cameras. Samsung cameras ship with default profiles like H.264, MJPEG or mobile. These profiles each define a codec, default resolution and default framerate. For example the default camera profiles may not provide a second… Continue reading Create custom multistreams using profiles for Samsung cameras
Samsung Cameras Create “Account Blocked” Errors and Cause Analytic Information to be Missed
Symptom Certain Samsung camera models can cause a “490 Account Blocked” error every five minutes in the exacqVision system log. This causes the Analytics events socket to reconnect every five minutes, and analytics events are missed during the reconnection. <br> This does not affect exacqVision recording, motion events, and input triggers. Only analytics are affected.… Continue reading Samsung Cameras Create “Account Blocked” Errors and Cause Analytic Information to be Missed