Tag: Client

Categories
Knowledge Support Support exacqVision Client Categories Products

Samsung SNB-3002 Camera Allows Only Motion Non-detection Areas

Symptom

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>

Workaround

When using exaqVision Client to configure a motion area for an SNB-3002 camera, define the area in which you want to ignore motion.

Categories
Knowledge Support Support exacqVision Client Categories Products

Axis Digital Autotracking

What is Axis Digital Autotracking?

It is an automatic tracking of moving objects. For a detailed explanation and a list of Axis devices that support this feature, go to http://classic.www.axis.com/products/autotracking/index.htm.

<br>

Axis Digital Autotracking Feature Support

exacqVision 7.0 (scheduled for June 2015) adds support for the Axis Digital Autotracking feature.

<br>

Is it enabled by default?

No, it is not enabled by default.

<br>

How do I enable Digital Autotracking?

Download autotracking from http://classic.www.axis.com/techsup/compatible_applications/autotracking/software.php. Install and enable autotracking on the Axis device, and then create View Areas on the device per the manufacturer’s instructions. When this is complete, the created views appear as multistreams in the exacqVision Client tree and on the camera’s settings page in exacqVision Client.

NOTE: Be sure to follow the manufacturer’s guidelines regarding resolution sizes for the primary and autotracking View Areas. Failure to strictly follow those guidelines will significantly impact the device’s performance.

<br>

Which Cameras Support Digital Autotracking?

For a list of devices that support Digital Autotracking, see http://classic.www.axis.com/techsup/compatible_applications/autotracking/software.php.

<br>

Expectations When Upgrading to exacqVision 7.0

If you upgrade to version 7.0, you will not see any changes to Axis camera configurations until you download, install, and enable Digital Autotracking on the device. Digital Autotracking requires that you create View Areas in the device to enable them as secondary streams in exacqVision.

If you used secondary streams before installing and enabling Digital Autotracking, you must manually add View Areas for each secondary stream to ensure they are still available. When enabling View Areas, the device will automatically enable View Area 1 as the primary stream. The device will also activate a View Area called Digital Autotracking if the Digital Autotracking application is enabled and running.

<br>

Benefits of Enabling View Areas

  1. Mirror, rotation, and PTZ functionality in each View Area is independent from other View Areas.
  2. Some devices offer more than four View Areas, which allows more than four secondary streams, which is the current limit in version 6.8 of the Axis plug-in.

<br>

Limitations When Enabling View Areas

  1. This must be done through the device’s web interface.
  2. Some devices allow you to enable View Areas only after installing the Auto tracking application.
  3. Enabling PTZ preset tours in the autotracking view will have a negative impact on performance.
Categories
Knowledge Support Support exacqVision Webservice Categories Products

Native Streaming in the Web Client

Affected platforms

exacqVision 7.2 or later

<br>

Description

exacqVision 7.2 introduces native h.264 video streaming to the web client. When a browser session connects to the web service, the browser and web service negotiate whether transcoding or native streaming will be used. The following logic describes how this is negotiated:

  1. If the browser does not support web sockets, fall back to polling (traditional method).
    • This includes IE8 and 9.
    • Since IE8 does not support the HTML5 element, it plays back by displaying the image element directly.
  2. If the user has disabled software decoding on the client configuration page, use web sockets JPEG.
    • This method is similar to traditional polling, but the delivery mechanism causes frames to be sent as they are generated.
  3. If the camera is not native H.264, use web sockets JPEG.
    • This includes digital PTZ “cameras” whose parent camera may be h.264, but as a virtual camera, they are not.
  4. If the camera’s resolution is 167% larger than the panel, use web sockets JPEG.
    • There is very little gain in rendering native h.264 on small panels.

At this point, the camera will attempt native h.264 decoding. If it succeeds, it will play back using software decoding. Otherwise, it will fall back to web sockets JPEG.

Categories
Knowledge Support Support exacqVision Client Categories Products

Line Expected Mac Client Error

Problem

When opening the Mac client the user sees an error dialog box appear stating something similar to “file, line X: ‘-‘ expected”. This is caused by a corrupted client configuration.

<br>

Steps to fix

  1. Close the exacqVision client.
  2. Open “Finder” from the Mac desktop.
  3. From the desktop menu bar, open the “Go” menu and select “Go to Folder”.
  4. Locate “~/Library/Application Support/edvrclient” and delete this.
  5. Locate “~/Library/Preferences/edvrclient Preferences and delete this.
  6. Locate “~/Library/Saved Application State/com.exacq.edvrclient.savedState” and delete this.
  7. Open the exacqVision client. Reconnect to the server on the Add Systems page if needed.
Categories
Knowledge Support Support exacqVision Client Categories Products

Browser Client behavior with privacy mode

Description

Most modern browsers provide a privacy mode for viewing web sites (e.g. “Incognito Mode” for Chrome, “Privacy Window” for Firefox, “InPrivate Window” for Edge). These privacy modes all operate on the same core principles, by not allowing any data generated by that browser window to persist once it is closed.

The web client stores a number of user settings in local storage (e.g. which servers are enabled, any stored credentials, user preferences) so that they are restored when the user revisits the page. When accessing the web client using a privacy mode, all of this generated data is cleared, and subsequent visits to the web client will not restore any of these settings.

<br>

Platform

Web Client / All

<br>

Steps to reproduce

  1. Access the web client in a browser’s privacy mode.
  2. Change some user settings (such as those in the Gears tab->Client page).
  3. Close the browser window.
  4. Revisit the web client in the browser’s privacy mode.

<br>

Expected result

The user settings are retained.

<br>

Actual result

No user settings are retained.

<br>

Work Around

There is no direct workaround, this is behaving exactly as these privacy modes are intended. To persist user data in the web client, do not use a privacy mode when accessing the site.

Categories
Knowledge Support Support exacqVision Client Categories Products

Axis plugin motion detection alarm event might not expire

Description

Setting a Record Video via Video Motion Event will not clear on an Axis Q6114-E camera running Edge software.

<br>

Tested Version

Edge 7.6.1.93449
Firmware 6.20.1
Client 7.6.4.94409

<br>

Platform

Edge

<br>

Steps to reproduce

  • Set a Motion Window on the camera via the Client
  • Confirm Motion Detection is functional
  • Create a new Event in Event Linking – Video Motion > “Motion Test” > Record Video > Pre set to 1 > Post set to 1 > Apply
  • Trigger motion on camera

<br>

Expected result

  • Motion triggers a red border based on the Event. The event should clear 1 second after motion has ceased being detected (based on Post-Trigger timing).

<br>

Actual result

  • The red border only clears when the 127.0.0.1 input is disconnected and re-connected to the Edge server.
  • Deleting the Event while the border is present does not clear the border.
  • Setting the schedule to Event Only has no effect.
  • Soft Triggers still function as expected

<br>

Fixed Version

7.9.16.99811

Categories
Knowledge Support Support exacqVision Client Categories Products

Server may emit unnecessary duplicate config and cause the Client to flicker

Description

Particularly evident with advanced h.264 branch. On any config update from client or evAPI, StreamPI unnecessarily emits the full, cached, master config document to all connected clients/evAPI instances. This unnecessary emit will either indicate or not indicate the applied update, depending on how long the update takes to be applied. In the case of external device communications like IP cameras, it will be like receiving a “middle” document that indicates pre-existing values. In the example of a new event linkage, it will be like receiving a “duplicate” config with the updated value.

<br>

Introduced Version

7.3.14 / 7.4.0

<br>

Platform

[All]

<br>

Steps to reproduce

  • Connect an IP camera.
  • Change any setting that’s stored in camera (like adjusting brightness or contrast sliders).

<br>

Expected result

Your slider will remain at its new position without any jumping.

<br>

Actual result

Your slider will temporarily revert to its previous position, then jump back to the new position.

<br>

Work Around

User experience annoyance, so not actually broken. The config update does actually apply correctly.

<br>

Fixed Version

7.9.3 / 7.10.0

Categories
Knowledge Support Support exacqVision Client Categories Products

Illustra Essentials low quality in MJPEG

Description

When connecting to some essentials camaera’s OEM’ed by Dahua, the customer can put the camera in a mode that shows jpeg in a low quality and the quality slider has no apparent effect.

To reproduce

  • Add an essentials IES02D1OCWIYB to a >= 8.1.5.102802
  • each change of codec and bitrate mode must be made separately on this device.
  • Select H.264 and apply
  • select CBR and apply.
  • Select MJPEG and apply
    • Camera stuck in CBR and poor image quality
  • Select H.264 and Apply.
  • Select Constant Quality and apply
    • Camera still stuck in CBR and poor image.

Workaround

  • Factory default camera
  • avoid switching H.264 to CBR before selecting MJPEG.
Categories
Knowledge Support Support exacqVision Client Categories Products

Vivotek factory default codec is set to SVC

Some Vivotek camera factory defaulted codec is SVC (Scalable Video coding) which is an extension of H264 that we do not support. When the camera is in this mode, the plugin fails to stream video and stays in the “connecting” state. Also were not be able to change the codec setting from the client. The only work around is to go to the camera’s web page change the codec to H264/jpeg and reconnect the camera from our client. This affects model IP8162.

<br>

Detail on SCV video here https://en.wikipedia.org/wiki/Scalable_Video_Coding.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM needs to use port and address when building xdv for client

Description

If multiple servers share the same IP but have different ports. ESM will remove additional servers with same IP, only using one of the servers. It should include all of these servers.

<br>

Tested version

4.9.23

<br>

Platform

All

<br>

Steps to reproduce

Add multiple servers on ESM with same IP Address and different port numbers Sync ESM with thick client

<br>

Expected result

All servers on ESM should be synced to thick client

<br>

Actual result

For server with the same IP address and different port numbers, only one server on that IP is synced to the client

<br>

Work around

There is no known work around for this issue

<br>