FAQ

This mode is almost the opposite of ‘Pre-Processed Footage mode’ in operation.
When PM service is executed, it directly accesses the recorder or Recording service, accesses the recorded data and performs analysis (IDLA).
Also, this mode can do PM search with any camera (the biggest difference from Pre-processed Footage mode)

Advantages :

‘Pre-Processed Footage mode’ costs a lot when building a service, but Recorded Footage mode doesn’t require IDLA VA service and MariaDB for pre-processed VA metadata like the above configuration. (In other words, the construction cost is lower than the Pre-Processed Footage mode.)
So, if the cost of H/W is burdened, you can use this mode.
 

 Person Match / Pre-Processed Footage
Among those two modes, the one with the fastest search speed is Pre-Processed Footage. This function classifies objects in advance (pre-processing), stores them in a separate database server (MariaDB), and searches through PM service if necessary. It has the advantage of faster search speed compared to Recorded Footage mode.
Also, when PM service is running, it is good because the search session resource is not consumed because it connects to MariaDB instead of directly connecting to the recorder. Devices like NVR only have two search sessions, so if there are many users who use ISS playback at the same time, the search session of NVR full may occur and PM search of NVR may not be possible.
 
In summary, the advantages of Pre-Processed Footage are:
- Fast search speed
- It is suitable for the system environment that has the restriction of search session such as NVR or TVR.

However, this service also has its weakness.
- Increased cost: IDLA Server and MariaDB storage capacity are required because pre-processing is required using IDLA and DB is stored by building MariaDB. That incurs additional costs.
+ However, if you are a user who already uses IDLA, there is no cost issue. (You only need to add as much storage capacity as MariaDB)

- Restriction that only cameras analyzed through IDLA can be used:
+ Data analyzed in advance through IDLA are stored in MariaDB, and this data is used by PM service, so there is a limitation that only cameras analyzed through IDLA can be used. / There is a restriction that other cameras cannot use PM service.
  + But you have to think about this, there are some cameras all people must pass through. For example, building entrances, checkout counters.

Therefore, it is necessary to recognize the pros and cons of the function and introduce the most appropriate service to the customer.
 

There is an IDIS Deep Learning Engine called IDLE, and using it, we are providing an IDIS VA(Video Analytics) technology called IDLA.
This time, we would like to introduce another VA technology called Person Match, which is a type of IDLA.

IDIS Person Match (hereinafter, PM) is a function that VA directly finds the person you are looking for.
If you find the person you are looking for in the video and run PM search, you can easily find out when and where the person is.
In the days without PM technology, security officers or police officers had to manually search through numerous CCTV footage for a very long time to solve a case. But now they don't have to.

This PM is a service belonging to ISS VA (IDLA), so IDLA license is used.
This also means that customers who already use IDLA can use PM service for free.

This IDIS PM service has two main modes.
- Person Match / Pre-Processed Footage
- Person Match / Recorded Footage mode 

VA Dashboard is a graph that shows the trend of problem occurrences, which means it does not represent an exact value of the events.
 
In other words, rather than displaying the total number of events, events that have occurred during one minute are counted as Violation 1.
If all 23 mask violation events occur within 1 minute, VA Dashboard counts them as 1.
 
A customer can misunderstanding about the current interval time of 1 minute has been received, and we intend to reduce it to 10 seconds.
Then, a value similar to the customer's intended result may be displayed.

I was able to change the camera IP settings in DirectIP 1.0 NVR.

However, please note that the IP setting function in the tool is not supported after moving to the DirectIP2.0 generation.

The reason why the customer guessed that it would be difficult to meet IK10 after checking the exterior material
It is likely that the judgment was made by looking at the plastic exterior parts.
The exterior plastic parts used in this product use a PC mixed material that can easily absorb shock, and the basic thickness of 3T is applied to prevent damage to ensure safety.

ISS has a Backup service module, you can use this service and back it up and store the NVR's HDD separately as replacement HDDs.

- How to configure of ISS
 
1. Uncheck ‘Overwrite backup data when the disk is full’ 
When assign HDD storage on Backup service, ‘Overwrite backup data when the disk is full’ should be unchecked so that Overwrite feature stop. 

 
2. Check ‘Notification of Disk Almost Full’ as 90%

 
3. When setting the backup for the first time, it is recommended to set “first / summary backup or event backup”.
This is due to the network throughput performance and h/w performance limitations of the Recorder. 

 
4. If the HDD is full and needs replacement, as shown in the picture below,
Make a note of the last recorded date/time before replacement, and when you connect a new HDD and reconfigure backup, you can start recording from the time you wrote the note. 

 
5. There is currently no function in ISS that gives an alarm when starting a new HDD recording.

- how it works 
 + please refer to Page. 263 on ISS v3.5 or higher version manual.
 + the traffic flows as below : 
Camera(device) > Streaming service > RTP Streaming service > RTP Client

- how to connect to it 
 + RTSP URL rule of the RTP Streaming service is as follows:

rtsp://[RTP Streaming Service IP]:[rtsp port]/
idis?trackID=[device identifier number]&
streamID=[stream index]&audio=[0 or 1]

i.e :  rtsp://192.168.10.100:554/idis?camera=4&video=h264

- It uses the streaming service ?
 + Yes, so NVRs and cameras must be added to Streaming service

‘Optimization’ has two functions :

Optimization’ pre-tests whether the newly added HDD is appropriate for recording.

(+ set Buffer size, # of camera, etc)

If the result is pass, the newly HDD is appropriate for recording.

For example, if you set 32 cameras for optimization and it passes the pre-test, the HDD guarantees 32 recordings.
However, it doesn’t guarantee over 32 cameras. It may be possible or not.

If you set 48 channels for optimization and it passes, the HDD guarantees upto 48 cameras, so you can add 16 more cameras whenever you want.

Type 2 : X-frame method
Type 5 : LongGop & ROI method 
(It is not written in the manual, so it is written as type 2,5 in the menu.)

Type 2 : Below 3 are the unit of the compression rate. The higher the compression rate means the higher the “loss compression” rate leads to lower the traffic. However, there may be a deterioration in image quality. 
+ LOW
+ NORMAL
+ HIGH

Please check C:\IDR-system\temp folder

Common mistake is not setting the time properly. The server needs to communicate with Microsoft server, so the time needs to be set correctly.

On Smartguard, right click on time bar and change time. This is the correct way to set time on the product.

This feature is to set the storing  period of VA data(e.g. people counting data).

IDIS SSM mobile app will remain to support legacy devices.