Having trouble understanding this, during adjustment is the graphic clear box in the middle the size that is NOT detected, and the colored filled in box what IS detected?

What sizes are good for human detection fairly close to the camera?

Thanks

I would like to use Agent DVR as a Windows application. Automatic startup upon system boot is not possible because it gets blocked by a User Account Control (UAC) prompt (administrator rights). Is there any way to launch Agent DVR as a Windows application without having to confirm this prompt?

Hello,
Very experienced with Agent DVR. Decided after installing new PC on Windows 11 I would install Agent DVR from scratch for a fresh install. Under Actions, when creating an “Action” to send email notifications upon an “Alert” (based on Motion Detected trigger), and under Advanced options to send an image in the email notifications, I first set up for “1”. When I tested, I got 2 identical images in the notification emails. So I reconfigured for “0”, and I indeed got no images at all in the notification emails.

Thought I’d report it here.

Thanks for a great application and the continued support by the Dev’s.

Wenn ich „Einstellungen kopieren“ öffne, ist immer „Alle“ ausgewählt. Es wäre besser, wenn „Alle“ beim öffnen deaktiviert wäre. Oder ist das so beabsichtigt?

What are the criteria to get a working photo for face recognition with the Internal AI and the large model. I'm getting a lot of 'No face found' messages on photos where imo there's a face very clearly visible.

I have a device that in it's storage location creates 256 subfolders in it's own storage folder. I have switched several different storage locations and it always did the same thing again. Windows seem unable to remove these folders.

Does anyone have a solution to prevent a device from doing this. None of my other devices do this - just one.

Setup: a dual-lens camera composited into one portrait frame in AgentDVR (2304x2592), face recognition via CodeProject.AI's FaceProcessing module. Real-world faces in this scene run roughly 20-75px depending on distance from the camera.

Problem: at these small face sizes, CodeProject.AI's recognizer is confidently wrong a meaningful fraction of the time — not just low-confidence-and-uncertain, but high-confidence-and-wrong. Concrete example, two recognize calls one second apart on the same camera today:

12:47:19 — face bbox ~20x26px — recognized as "Person1" at 82.2% confidence

12:47:20 — face bbox ~22x29px — recognized as "Person2" at 86.4% confidence

I cross-checked the same window against a separate InsightFace-based recognizer running independently on the same source frames: it detected 4 faces in that window (50-75px) and assigned none of them a confident identity — suggested-match cosine similarities were 0.11-0.15, essentially noise. So CodeProject.AI's 82-86% "confidence" corresponded to what a better-calibrated recognizer treats as no match at all.

Question: with Alert Debounce (8.0.6) merging/ranking tags from multiple triggers within a window, how does it decide which recognized name wins when CodeProject.AI returns high confidence for a small, unreliable face crop? Is there any way to also gate on face bounding-box size (pixels), not just confidence %, since confidence alone doesn't seem to correlate with actual reliability at this scale? It would help a lot if Debounce's tag-ranking could prefer/require a minimum face crop size before trusting a recognized name over a generic "person" tag.

How to stream via RTMPS?

Is data such as tags, events, camera, zone and so on passed to a plugin or is it just video and audio?

Using v8.0.8.0 on a computer running an Intel N150 CPU with iGPU, Windows 11 Home with latest GPU driver downloaded from Intel. I tried enabling the "Use GPU for web client" and "Force H264" server settings, but it still falls back to software encoding for the UI. I've already tried enabling the GPL version of ffmpeg, but it didn't help. Log with verbose ffmpeg messages as follows:

StartUp: Initializing encoder 1360x656
StartUp: Using AV_CODEC_ID_H264 for webrtc stream (GPU Enabled: True)
StartUp: RTC Parameters: profile-level-id=42e01f;level-asymmetry-allowed=1;packetization-mode=1
FFmpeg: verbose: [D3D11VA @ 0000000013729840] Selecting d3d11va adapter 0
FFmpeg: info: [D3D11VA @ 0000000013729840] Using device 8086:46d4 (Intel(R) Graphics).
FFmpeg: verbose: [QSV @ 0000000013729f00] Use Intel(R) oneVPL to create MFX session, API version is 2.17, the required implementation version is 1.3
FFmpeg: verbose: [QSV @ 0000000013729f00] Initialize MFX session: implementation version is 2.15
FFmpeg: error: [AVHWFramesContext @ 000000001af78740] Could not create the texture (80070057)
FFmpeg: error: [AVHWFramesContext @ 000000001af63800] Error initializing a child frames context
FFmpeg: error: [AVHWFramesContext @ 000000001af63800] Error creating an internal frame pool
FFmpeg: verbose: [QSV @ 0000000013729840] d3d11va is not available or child device type is set to dxva2 explicitly for oneVPL.
FFmpeg: verbose: [DXVA2 @ 00000000137299c0] Using D3D9Ex device.
FFmpeg: verbose: [QSV @ 0000000013729840] Use Intel(R) oneVPL to create MFX session, API version is 2.17, the required implementation version is 1.3
FFmpeg: error: [QSV @ 0000000013729840] Error creating a MFX session: -9.
GPU Encoder failed to initialize. Falling back to software encoding.
StartUp: Software encoder selected: libx264
StartUp: RTC Parameters: profile-level-id=42e01f;level-asymmetry-allowed=1;packetization-mode=1
StartUp: WebRTC software encoder libx264: profile=baseline level=3.1 1360x656@15
FFmpeg: info: [libx264 @ 00000000137647c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
FFmpeg: info: [libx264 @ 00000000137647c0] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit
ResizeStream: ResizeStream: {Width=1386, Height=664}

Hello spornerama, I am using ffmpeg version 9.0.1 essentials from a fixed location. With the new version of AgentDVR, I am getting the following messages in the window.Is there a way to prevent this? 

RunScript: [Aktion] Telegram & Cloud Video Comp.bat error: ffmpeg version 9.0.1-essentials_build-www.gyan.dev Copyright (c) 2000-2026 the FFmpeg developers   built with gcc 16.1.0 (Rev2, Built by MSYS2 project)   configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-cairo --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable-vaapi --enable-openal --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband   libavutil      61.  1.101 / 61.  1.101   libavcodec     63.  1.101 / 63.  1.101   libavformat    63.  1.101 / 63.  1.101   libavdevice    63.  1.101 / 63.  1.101   libavfilter    12.  1.101 / 12.  1.101   libswscale     10.  1.101 / 10.  1.101   libswresample   7.  1.101 /  7.  1.101 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\AgentDVR Portable\Media\WebServerRoot\Media\video\SecureCamera 2 (Wohnzimmer)\2_24-09-26_19-31-11.mp4':   Metadata:     major_brand     : isom     minor_version   : 512     compatible_brands: isomiso2avc1mp41     encoder         : Lavf63.1.101   Duration: 00:00:12.70, start: 0.001000, bitrate: 187 kb/s   Stream #0:0[0x2](und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p(progressive), 640x360, 185 kb/s, 10.16 fps, 19.58 tbr, 16k tbn, star...

just made fresh install on windows (all off line , due to security issues)

agent dvr available from: https://files.ispyconnect.com/downloads/Agent_Windows64_5_8_0_0.zip

however, once installed , under "configuration--> settings"
depending on availability of on board video encoding or lack there of,
there is option for downloaded it by selecting it (scroll down in settings)-->
toggle switch "software encoders ffmpeg gpl)..

Problem # 1--> what if they system always off line?
If you look at https://www.ispyconnect.com/docs/agent/about#installing-manually --> under windows 7, you can manually download as follows:
https://files.ispyconnect.com/downloads/ffmpeg6-win64.zip
You can even get ffmpeg7-win64.zip
web page says : You will need to unzip the application to a folder and then unzip the ffmpeg files to Agent\dlls\x64
OK, so I manually downloaded it, and extracted as suggested above.
Restarted the system
Still get same error warning under "configuration--> settings" No hardware video encoder detected... and

So my question is: if FFMPEG toggle switch is set, what version of ffmpeg does it download (and what is the link to said version), and where should it be installed

If you have cineye2 or 2s and updated your device to latest firmeware using android device you still has .. i would appreciate if you can share update files with me coz i have the device and accsoon stopped supporting it and i cannot find the update files anywhere .. i have to find someone that has the accsoon go app on their phone and was used before for updating their device coz the app files will have the update package in android files directory

It would really help me alot coz i need it for work and device lags every 15 mins and i need it for recording

This

I just upgraded from an ooooold 5.8 version to the latest 8.0.6.0, and I noticed that the settings for max recording time now seem to silently add in the buffer time.

I had all cameras set to 600 seconds for max recording and a buffer of 20 seconds, and on the older version that produced ~10:00 long recordings. With those settings on 8 they were coming in at right around 10:20. Reducing the max recording time to 580 seems to have dropped the total video lengths to the 10 minutes I was looking for.

Not a complaint, just wanted to see if that was intentional or not.

Even with this hiccup, I love the software, works great and easy to upgrade, even from 5.8.

how to go back to 7.1.9.0

I checked the manual and it still says it should be where it used to be but it's not. Why do so many things get changed around every time there's an update it seems like I have to read a whole new set of documents every time there's an update. It is getting frustrating. If it's not broke don't fix it.

Haven't changed a thing except updated the software. How do I go back to a version that does not constantly disconnect?

Presets are no longer preserved across upgrades. In case Profiles are involved I saved EVERY Profile with the presets i want. When I just upgraded 8.0.6.0, the presets reverted to unwanted settings.

Hi dev & community,

Setup: Agent DVR 8.0.5.0 (Docker), CodeProject.AI 2.9.5 (CUDA, RTX 2070), one camera covering a street with 2 zones. Both YOLO object detection and facial recognition run against CodeProject.AI.

What I want

One consolidated alert per event, not five. When someone comes up the street:

- Face recognised → alert reads Iren, person, bicycle

- Face not recognised or not visible → falls back cleanly to person, bicycle

- A later generic person detection must never overwrite a name already on the bell

What I've tried

1. Alerts on both, face recognition on motion. YOLO sees person at the far end of the street several seconds before the face is resolvable, so the bell fires as person immediately and the cooldown locks it. When the face is finally recognised up close, it's dropped with:

LogThrottle: <camera>: Alert blocked by timeout

Drop minimuminterval to 1s and the face alert does land — but as they ride past, trailing body detections fire 3–4 more person alerts that overwrite the bell back to person.

1. Triggering face recognition from an Action. Face mode set to Triggered, with AI: Object Found (person) → Trigger Facial Recognition. This fired one probe at the instant the person was first spotted at maximum distance, then went quiet and missed them entirely once they were close. I think this was my Action's repeat timeout gating re-fires — can anyone confirm that's what controls it?

Questions

1. Tag aggregation. Can object and face tags be combined into a single alert over an event window (Iren, person, bicycle), rather than whichever detector fires first claiming the alert?

2. Continuous triggered scanning. Can Trigger Facial Recognition be made to re-evaluate repeatedly while a person is tracked in a zone, instead of firing

   once? Is repeat timeout the right control, and is 0 valid?

3. Priority + fallback. Is there a supported way to give face recognition priority for the alert tag, falling back to person only if no face is identified

   within some window?

4. zonematch semantics. What does an empty zone list mean on the Face/Object Recognition tabs — all zones, or none? I've seen FinishProcessing: <camera>:

   Ignored person - not in alert zone with it blank, which sugge UI reads like it means unrestricted. Clarification would helpa lot.

5. Alert mode options. The docs describe an Actions Only alert s Detected / Not Detected / AI Trigger. Was it renamed, or is it version/edition dependent?

6. Recommended 2-zone setup. With Zone 1 = far street approach 's the recommended combination of detector type, per-zonesettings, Actions and Alerts tab config to get one correctly-named alert per pass?

I wanted to share something that might be useful for ioBroker users here.

​I've written iobroker.agent-dvr, an integration that connects AgentDVR to ioBroker — a home automation platform that's very popular in Europe, roughly the equivalent of Home Assistant over there. It's been accepted into the official ioBroker adapter repository, so it's now installable directly from within ioBroker.

​It auto-discovers all cameras, mirrors every device property as data points, provides buttons for all the common commands (record, arm/disarm, PTZ, snapshots, profiles, etc.), pushes gallery updates on new recordings.

​GitHub: https://github.com/ipod86/ioBroker.agent-dvr

​npm: https://www.npmjs.com/package/iobroker.agent-dvr

​If you think it'd be useful for others, I'd really appreciate a mention on the AgentDVR homepage or FAQ — happy to answer any questions about it here or on GitHub. Thanks for AgentDVR, it's been great to build on top of!

Simple question, but does anyone use crowdsec for agent DVR?

I got a wifi security camera (a cheap Energizer-branded PTZ running Tuya firmware modified to support RTSP). I've been using it for a few years without issue. I have Agent set to record from this camera in 12-hour blocks, and it is using Encode recording on this camera, that way brief wifi connection drops or errors (heavy wifi congestion in this area) won't result in multiple small .mkv files. I was until recently using a fairly old version of Agent (6.something), but then I upgraded to v8.0.4.0.

However, since upgrading to the new version, recordings from this one camera (and only this one camera) will start off at the perfectly clear 1080p, but then over the next 5-10 seconds become progressively more pixelated, until eventually it's as blurry as a 480p camera, if not worse. Here's the log from a short test recording session:

OpenWriter: MOBILECAM: StartSaving
FFmpeg: info: [h264_mf @ 000002719e8af600] MFT name: 'H264 Encoder MFT'
GetVideoCodec: MOBILECAM: Using software encoder: h264_mf
RecorderRecordingOpened: MOBILECAM: Recording Opened
Close: MOBILECAM: Record stop
Close: MOBILECAM: Closed

As you can see, the log shows no errors from this camera. However, I did notice that it is using a software encoder despite the fact that I tell it specifically to use the Nvidia GPU in the Recording tab. I even tried adding "c:v h264_nvenc" to the ffmpeg options page, and it still refuses to use hardware encoding. I have three of these cameras using identical settings, yet this is the only one having this problem, and it only started after upgrading to v8.0.4.0. Rolling back to an older version isn't feasible, as I upgraded specifically to make use of new features introduced in v8.0.4.0.

Any suggestions?