Before being able to manage motion windows from the exacqVision Client the following actions need to be performed within the camera’s web GUI.
You should now be able to manage existing areas and draw new areas from within the exacqVision Client
Note: It may be necessary to factory reset the camera first.
<br>
When updating ExacqVision Server straight to 21.03 from a version prior to 9.8 the mechanical PTZ tab disappears.
On the previous version below 9.8, update to ExacqVision Server 19.12 and verify the mechanical PTZ tab is there.
Then update to ExacqVision Server 21.03 and verify the mechanical PTZ tab is there. If it is not, downgrade back to 19.12 and repeat the process.
A related behavior is also being reported of fresh installs of Samsung cameras ranging from 21.03 up to 23.09.9.0 server. If this is seen the work around best used at this time to provide working PTZ are the following.
Workaround:
First , check the cameras xml to see if it has the PTZ settings set to “1” (seen below). If it does not, edit the file on the current version. Make sure to follow steps 2-8 seen below here to apply the change properly. If this fails then proceed with following steps 1-10.
1. Downgrade to 19.12 (when doing so make sure to have a good config or know the credentials for the cameras.) Later on when updating back to a current version you will need to re add the password to the camera.
2. Disable camera from client.
3. Stop the server service.
4. Edit the camera xml.
5. Edit the line starting with PTZ Pan, Tilt, Zoom, Focus, Iris Enabled and Supported.
Edit the “0” and make all of them “1” <PTZ Pan="1" Tilt="1" Zoom="1" Focus="1" Iris="1" Enabled="1" Supported="1">
6.Save the file.
7. Start the server service.
8.Enable the Camera in the client.
9.Check to see if the Mechanical tab is viewable in the camera settings page of the client.
10. Update to any version.
This is being backpatched to 24.06_RC
Samsung SUNAPI2 support is release in r102309 dev build 7_9_38_102356 and RC 8.0.0.102418.
<br>
– coordinate information for privacy mask and motion regions provided from the camera are inconsistent. Samsung is to provide updated fw that from what we understand is the sensor coordinate for different pixel modes the camera supports. This results in the privacy mask an motion region calculation error especially in corridor modes for some models. The work around is to set the cameras in normal mode when create the regions. Or use the camera web page to create the regions. This should be fixed when the updated fw is consistent across all the SUNAPI2 models.
– The current release does not support H265 modes. As a result, camera with H265 profiles might have issue in adding back missing custom created profiles from the cameras. The use case is, additional profiles could be added to the list other than the build-ins. The plugins “remembers” all the profiles and will add back the ones that are missing on a re-connection. This would be fixed when we support H265 profile. This is not very common but just in cases when user create their own profiles and delete them.
With newer Samsung models that supports SUNAPI2. Only the first input trigger is activated for cameras that have multiple trigger inputs.
<br>
<br>
All platforms for IP Cameras using Samsung plugin
<br>
<br>
<br>
<br>
exacqVision Server 8.1.4.102781
<br>
Samsung SNB-3002 cameras allow you to define non-detection motion areas. This is the opposite of most Samsung cameras, which allow you to define detection areas. There is no indication in exacqVision Client that an SNB-3002 camera motion window defines non-detection areas.
<br>
When using exaqVision Client to configure a motion area for an SNB-3002 camera, define the area in which you want to ignore motion.
Issue seen with SNO-8081R/SNV-8081R
<br>
This is caused by the camera reporting codec of h.265 profile that we do not currently support with our Samsung plugin. This does not affect other profiles. The message can be ignored.
Samsung PTZ functionality loss in exacqVision Server 20.03
<br>
Re-enable mechanical PTZ for the camera, via exacqVision Client.
<br>
20.03
<br>
Fixed in 20.03.111 and forthcoming 20.03.7 RC
Some Samsung models are not supported in regards to motion window configuration.
<br>
Configure motion windows via the cameras web interface.
<br>
Capability added to exacqVision.
<br>
exacqVision Server versions prior to 20.03.123
<br>
20.03.123
The standard form for exacqVision camera addresses is as follows:
{host}{?parameter_1=value_1}…{?parameter_n=value_n}{#override_1=value_1}…{#override_n=value_n}
<br><br>
| Plugin | Option | Usage |
|---|---|---|
| ACTi | transport=http | HTTP stream support for legacy platforms and user data |
| ACTi | transport=rtsp | RTSP stream with separate metadata socket for motion/input trigger/video loss/etc. |
| Axis | zoom=config | By default zoom only cameras support. |
| Axis | zoom=operation | Force zoom only operation and controls as part of PTZ and live view. |
| Axis | blocksize=off | On by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues. |
| Axis | transport= {udp,tcp,rtsph,rtsphs} | Transport overrides for use with Secure Streaming |
| Axis | tunnelport={1025-65535} | Override for tunnel port when not the same as CGI port. Use as a workaround for only having 1 port input box/XML attribute. |
| Axis | timestamp={server,trusted} | Override timestamp to server time(server) for problem cameras or to camera adjusted by RTSP/RTCP per RFC(trusted) |
| Arecont | none | |
| Dahua | transport= {udp,tcp,rtsph} | Transport overrides for use with Secure Streaming |
| Dahua | timestamp = server | Stamp with server time. |
| Dahua | timezone=camera | Allow camera to retain timezone when connected to exacq (do not push GMT as we normally do). |
| Dahua | timezone=utc | push GMT to device, this is also default if not provided. |
| Hikvision | timestamp=rtp | Force to camera timestamp without waiting for RTCP sync. |
| Hikvision | transport={tcp,udp,rtsph,rtsphs} | Transport overrides for use with Secure Streaming |
| Hikvision | getparameter_override=true | Needed for HQHI-SATA encoder to prevent stream interruption. |
| Hikvision | osd_override=off | Allow camera time OSD to be displayed (when enabled on camera) |
| Hikvision | timezone=camera | Allow camera to retain timezone when connected to exacq (do not push GMT as we normally do). |
| Hikvision | timezone=server | Push GMT timezone to camera (because Illustra standard does NOT do this as default) |
| Hikvision1 | timestamp=server | Stamp with server time. |
| Hikvision1 | timestamp=rtcp | Stamp with server time until sync with RTCP server report. |
| Hikvision1 | support=legacy | Support original CGI interface. |
| Hikvision1 | support=isapi | Support ISAPI interface. |
| Illustra3 | transport=udp | Stream RTSP session with UDP protocol. |
| Illustra3 | zoom=operation | Force zoom only operation and controls as part of PTZ and live view. |
| IllustraFlex | none | |
| Illustra | none | |
| Ioimage | none | |
| Ipx | none | |
| IQEye | none | |
| Onvif | transport=udp | 1 TCP socket for RTSP and up to 6 UDP sockets for video, audio, and application data and their RTCP streams. |
| Onvif | transport=rtsp | 1 TCP socket for RTSP with all other streams interleaved in it. |
| Onvif | transport=http | Default 2 TCP sockets for RTSP over HTTP over TCP. ( 1 long POST and 1 long GET ) |
| Onvif | Profile=x | Connect to a specific profile number. |
| Onvif | nat=1 | Support nNAT translation to WAN address. |
| Onvif | timestamp=server | Stamp with server time. |
| Onvif | bank=x | Select 4 channel encoder banks. |
| Onvif | http=1.0 | For Samsung SPE-100/400 that requires http1.0 for live555. |
| Onvif | support=profile-s | Force Profile-S implementation for cameras that do not fully support Profile-T. |
| Onvif | events=pull or stream | Select metadata event mode when the manufacturer option is ALL. |
| Onvif | use_caps={on,off} | Use deprecated GetCapabilities for when GetServices is poorly implemented. |
| Onvif | tunnel_alive = auto,get_parameter,set_parameter,options,none | Keep alive mechanism during RTPS-over-HTTP, defaults to auto. |
| Panasonic | transport=udp | Stream RTSP session with UDP protocol. |
| Panasonic | timestamp=server | Stamp with server time. |
| Pelco | transport=udp | Stream RTSP session with UDP protocol. |
| RTSP | transport=udp | Stream RTSP session with UDP protocol. |
| RTSP | transport={tcp,udp,rtsp,rtsph,rtsphs} | All Transport overrides. |
| RTSP | timestamp=server | Stamp with server time. |
| RTSP | timestamp=rtcp | Stamp with server time until sync with RTCP server report. |
| RTSP | timestamp=trusted | Stamp with cameras time adjusted by RTSP/RTCP per RFC. |
| RTSP | stream=x | Select specific stream number. |
| RTSP | track=x | Select specific track number. |
| RTSP | tunnelport={1025-65535} | Tunneling port replacing the :portnum on URL. |
| RTSP | embed_port=* | Forced RTSP URL format in tunnel. |
| RTSP | http=1.0,1.1 | Forced RTSP URL version number. |
| RTSP | bc_audio=supported | Backchannel audio out. |
| RTSP | bc_samplerate=xxxx | Backchannel sampling rate. |
| RTSP | bc_samplesize=xxxx | Backchannel sampling size. |
| RTSP | bc_mode=ts | Backchannel timestamp mode(duration(default)/timestamp using RTCP adjustment). |
| Samsung | transport={tcp,udp,rtsp,rtsph,rtsphs} | Transport overrides for use with Secure Streaming |
| Samsung | tunnelport={1025-65535} | Tunneling port if different than one used for CGI. |
| Samsung | http=1.0,1.1 | Fix for some older devices. |
| Samsung | embed_port=* | Fix Internal URL inside tunnel if needed. |
| Sanyo | none | |
| Sony | timestamp=server | Stamp with server time. |
| StarDot | none | |
| UDP | none | |
| Vivotek | support=legacy | Use legacy API and support. |
| Vivotek | support=onefw | Use OneFW API and live555 stream. |
1 The use of these overrides requires the use of IPv4 dotted address, FQDNs cannot be used.
<br><br>
| Override | Description |
|---|---|
| transport | Stream session with the specified protocol { TCP | UDP }. |
| timestamp | Stamp frames with server or camera time. |
| timezone | { UTC | camera | server } Determine if camera timezone is set to UTC+0, left as camera or set to that of server. |
| zoom | Override configuration or operation zoom function. |
| blocksize | On by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues. |
| profile | Connect to profile number N; N is a number from 1 to the number of profiles supported by the camera. |
| nat | Support NAT translation to WAN address. |
| bank | Select 4 channel encoder banks. N is 1 – number of banks, usually in set { 1 | 2 | 3 | 4}. |
| support | Override support API. For example, used by Vivotek to support either legacy or oneFw. |
| stream | Select a specific stream ID for devices supporting multiple streams. |
| track | Select a specific track for devices supporting multiple media tracks. |
| tunnelport | Workaround for our XML and GUI only giving us one box for port. Used if tunnel port is different than CGI and does not come from CGI. |
| embed_port | Value does not matter. Forces RTSP URL inside tunnel to put port in the URI if it is default. A small selection of cameras need ip:554 even when in a tunnel over 80 |
<br>
exacqVision Server crashes when connecting to a Samsung SPE-100/400 using the native Samsung plugin.
<br>
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>
Connect to the device with the Onvif device type on the ‘Add IP Cameras’ page.
Add the ‘#http=1.0’ override option to the ‘Hostname/IP Address’ field.
If the device IP is 192.168.0.5, change it to read 192.168.0.5#http=1.0
<br>
Samsung-SPE-100-400-Causes-Server-Crash.pdf