A few issues I hope you can help with.

[ph123uk]

Hi all,

Great program, love it, very easy to get installed in docker on a bare metal OMV install.

Specs:

Ryzen 5800x
32GB RAM
Quadro P1000
Cuda image of viseron
Only Running 2 cameras, both RTSP:

Reolink e1Pro (works perfectly in every way)
EZVIZ L1C1 - A few issues

A couple of issues:

1: On the LC1C it "skips" frames when viewing live and also on the recordings, signal is good, its only a 1080P stream with low substream - strange thing is, Im running synology surveillance station and that works perfectly with the camera, no skips, signal is great on the camera, I've also thrown a trial version of Blueiris on a little Mini PC, again connecting to the same streams, no issue with that either, also no skipping on the EZVIZ app, VLC stream etc - so its something within viseron I can work out.

2: Scrolling in chrome through "Events" after 2 seconds of scrolling I get a "Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings." - Both cameras from the web view.

Sometimes, when playing back recordings in the timeline / events i get a "Playback stalling due to low buffer" followed by "Nudging xxxxx"

Config is:

ffmpeg:
  camera:
    camera_1:  # This value has to be unique across all cameras
      name: Back Door Camera
      host: !secret camera_one_host
      port: 554
      path: /H.264
      username: !secret camera_one_username
      password: !secret camera_one_password
      #frame_timeout: 2
      #codec: h264
      fps: 22
      #width: 1920
      #height: 1080
      #substream:
      #  path: /Streaming/Channels/102/
      #  stream_format: rtsp
      #  port: 554
      recorder:
        lookback: 10
        idle_timeout: 30
        events:
          max_age:
            days: 30

    camera_3:  # This value has to be unique across all cameras
      name: Kitchen Camera
      host: !secret camera_three_host
      port: 554
      path: /h264Preview_01_main
      username: !secret camera_three_username
      password: !secret camera_three_password
      substream:
        path: /h264Preview_01_sub
        stream_format: rtsp
        port: 554
      recorder:
        lookback: 10
        events:
          max_age:
            days: 30

darknet:
  object_detector:
    cameras:
      camera_1:  # Attach detector to the configured camera_1 above
        fps: 1
        scan_on_motion_only: true  # Scan for objects even when there is no motion
        labels:
          - label: person
            confidence: 0.75
            trigger_event_recording: true
          - label: dog
            confidence: 0.75
            trigger_event_recording: true
          - label: cat
            confidence: 0.75
            trigger_event_recording: true
          - label: car
            confidence: 0.75
            trigger_event_recording: true

      camera_3:  # Attach detector to the configured camera_1 above
        fps: 1
        scan_on_motion_only: true  # Scan for objects even when there is no motion
        labels:
          - label: person
            confidence: 0.75
            trigger_event_recording: true
          - label: dog
            confidence: 0.75
            trigger_event_recording: true
          - label: cat
            confidence: 0.75
            trigger_event_recording: true


## You can also use motion detection
mog2:
  motion_detector:
    cameras:
      camera_1:  # Attach detector to the configured camera_1 above
        fps: 2
        trigger_event_recording: true
        threshold: 10

      camera_3:
        fps: 1
        trigger_event_recording: true
        threshold: 15

nvr:
  camera_1:  # Run NVR for camera_1
  camera_3:  # Run NVR for camera_3

Any ideas welcome, as you can see above, ive commented out mulitple things trying to resolve, adding stream details etc, even on a "basic" config, still the same

[john-]

2: Scrolling in chrome through "Events" after 2 seconds of scrolling I get a "Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings." - Both cameras from the web view.

Same error here on Firefox with single camera. I am not running the most recent dev on this machine.

I do not know if number of seconds is the trigger or some other condition when scrolling. Maybe the speed of the scroll? Number of items scrolled through? Rate of scroll? I am not sure yet.

I noticed that at start of day with smaller number of events I cannot reproduce it. If I go back to a prior day with 99+ events I can reproduce it. From my experience it does not happen with timeline only events.

[ph123uk]

2: Scrolling in chrome through "Events" after 2 seconds of scrolling I get a "Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings." - Both cameras from the web view.

Same error here on Firefox with single camera. I am not running the most recent dev on this machine.

I do not know if number of seconds is the trigger or some other condition when scrolling. Maybe the speed of the scroll? Number of items scrolled through? Rate of scroll? I am not sure yet.

I noticed that at start of day with smaller number of events I cannot reproduce it. If I go back to a prior day with 99+ events I can reproduce it. From my experience it does not happen with timeline only events.

Exact issue here, fine on "timeline" breaks on Events.

[ph123uk]

Two clips showing the difference to aid in suggestions, for clarity, the synology is running on a potato, DS418 and 4tb Spinning HDD, the Viseron is running on a 5800x and a Nvidia p1000 on a dedicated 2TB SSD:

Viseron clip: https://youtu.be/dC26mYXH_Uk

Synology Clip: https://youtu.be/96jWPckquWs

[roflcoopter]

Thanks for giving Viseron a spin!

Was just gonna ask for some clips so thanks for that.

Regarding the skipping, it can be hard to figure out. We probably need to tweak the FFmpeg command a little to find something that works. Since i dont have access to your particular hardware i am not really sure how to proceed. If you are up for it you can enable debug logging and snag the generated ffmpeg command and start playing around with it manually to see if we can find the culprit.
Lemme know if you are up for that.

Regarding the other issue, "Minified React error" i dont see that behaviour. How many events(ish) do you guys have in a day?

[john-]

Regarding the other issue, "Minified React error" i dont see that behaviour. How many events(ish) do you guys have in a day?

My system is focused on data collection right now and not minimizing false positives and removing redundancy. Therefore, my event counts may not be realistic for what should be targeted. I am OK with the "Minified React error" error as it is not a practical issue for me. Others will need to chime in.

Not sure if this is a valid way to get the counts:

select date(created_at) as day, count(*) as events from events group by day order by day;

If so:

    day     | events 
------------+--------
 2025-06-13 |  12620
 2025-06-14 |  43605
 2025-06-15 |  33083
 2025-06-16 |  44791
 2025-06-17 |  47654
 2025-06-18 |  96313
 2025-06-19 |  23008

[ph123uk]

Thanks for giving Viseron a spin!

Was just gonna ask for some clips so thanks for that.

Regarding the skipping, it can be hard to figure out. We probably need to tweak the FFmpeg command a little to find something that works. Since i dont have access to your particular hardware i am not really sure how to proceed. If you are up for it you can enable debug logging and snag the generated ffmpeg command and start playing around with it manually to see if we can find the culprit. Lemme know if you are up for that.

Regarding the other issue, "Minified React error" i dont see that behaviour. How many events(ish) do you guys have in a day?

Not many events, video attached, happens on all cams.

https://www.youtube.com/watch?v=RGilwaGHnZg

[roflcoopter]

The events table is storing internal system events, not used for much atm.

The events that are shown in the UI are spread out on multiple tables so can be tricky to make a query for it

[roflcoopter]

Thanks for giving Viseron a spin!
Was just gonna ask for some clips so thanks for that.
Regarding the skipping, it can be hard to figure out. We probably need to tweak the FFmpeg command a little to find something that works. Since i dont have access to your particular hardware i am not really sure how to proceed. If you are up for it you can enable debug logging and snag the generated ffmpeg command and start playing around with it manually to see if we can find the culprit. Lemme know if you are up for that.
Regarding the other issue, "Minified React error" i dont see that behaviour. How many events(ish) do you guys have in a day?

Not many events, video attached, happens on all cams.

https://www.youtube.com/watch?v=RGilwaGHnZg

Thanks, I will generate some fake events and see if I can reproduce

[ph123uk]

Regarding the skipping, it can be hard to figure out. We probably need to tweak the FFmpeg command a little to find something that works. Since i dont have access to your particular hardware i am not really sure how to proceed. If you are up for it you can enable debug logging and snag the generated ffmpeg command and start playing around with it manually to see if we can find the culprit.
Lemme know if you are up for that.

I am up for that, but you will need to be patient, im rather new to all this, let me know how to proceed.

[ph123uk]

Does this help:

2025-06-20 11:39:38.467 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - Getting stream information for rtsp://*****:*****@192.168.1.9:554/H.264
2025-06-20 11:39:38.467 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_3] - Getting stream information for rtsp://*****:*****@192.168.1.11:554/h264Preview_01_main
2025-06-20 11:39:38.467 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - FFprobe command: ffprobe -hide_banner -loglevel error -print_format json -show_error -show_entries stream=codec_type,codec_name,width,height,avg_frame_rate -rtsp_transport tcp rtsp://*****:*****@192.168.1.9:554/H.264
2025-06-20 11:39:38.468 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_3] - FFprobe command: ffprobe -hide_banner -loglevel error -print_format json -show_error -show_entries stream=codec_type,codec_name,width,height,avg_frame_rate -rtsp_transport tcp rtsp://*****:*****@192.168.1.11:554/h264Preview_01_main
2025-06-20 11:39:40.126 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - Closing LogPipe
2025-06-20 11:39:40.126 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - Stream information from FFprobe: Width: 1920 Height: 1080 FPS: 22 Video Codec: h264 Audio Codec: aac
2025-06-20 11:39:40.127 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - LogPipe thread ended
2025-06-20 11:39:40.127 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - Getting stream information for rtsp://*****:*****@192.168.1.9:554/Streaming/Channels/102/
2025-06-20 11:39:40.127 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - FFprobe command: ffprobe -hide_banner -loglevel error -print_format json -show_error -show_entries stream=codec_type,codec_name,width,height,avg_frame_rate -rtsp_transport tcp rtsp://*****:*****@192.168.1.9:554/Streaming/Channels/102/
2025-06-20 11:39:40.140 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_3] - Closing LogPipe
2025-06-20 11:39:40.141 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_3] - Stream information from FFprobe: Width: 2880 Height: 1616 FPS: 20 Video Codec: h264 Audio Codec: aac
2025-06-20 11:39:40.141 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_3] - Getting stream information for rtsp://*****:*****@192.168.1.11:554/h264Preview_01_sub
2025-06-20 11:39:40.141 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_3] - FFprobe command: ffprobe -hide_banner -loglevel error -print_format json -show_error -show_entries stream=codec_type,codec_name,width,height,avg_frame_rate -rtsp_transport tcp rtsp://*****:*****@192.168.1.11:554/h264Preview_01_sub
2025-06-20 11:39:40.141 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_3] - LogPipe thread ended
2025-06-20 11:39:41.043 [ERROR   ] [viseron.components.ffmpeg.stream.camera_3] - [h264 @ 0x55acf2087fc0] Overread VUI by 8 bits
2025-06-20 11:39:43.194 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - Closing LogPipe
2025-06-20 11:39:43.194 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - Stream information from FFprobe: Width: 768 Height: 432 FPS: 10 Video Codec: h264 Audio Codec: aac
2025-06-20 11:39:43.194 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - LogPipe thread ended

[roflcoopter]

There should be a line that says FFmpeg decoder command: ....

But there should be a viseron.log file on yoru config folder, you can attach that instead.

[ph123uk]

2025-06-27 13:42:31.878 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - FFmpeg decoder command: ffmpeg_camera_1 -hide_banner -loglevel error -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -timeout 5000000 -c:v h264_cuvid -rtsp_transport tcp -i rtsp://*****:*****@192.168.1.9:554/Streaming/Channels/102/ -vf fps=1.0 -f rawvideo -pix_fmt nv12 pipe:1
2025-06-27 13:42:31.878 [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - FFmpeg segments command: ffmpeg_camera_1_seg -hide_banner -loglevel error -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -timeout 5000000 -c:v h264_cuvid -rtsp_transport tcp -i rtsp://*****:*****@192.168.1.9:554/H.264 -f hls -hls_time 5 -hls_segment_type fmp4 -hls_list_size 10 -hls_flags program_date_time+delete_segments -strftime 1 -hls_segment_filename /tmp/viseron/segments/camera_1/%s.m4s -c:v copy -c:a copy /tmp/viseron/segments/camera_1/index.m3u8
2025-06-27 13:42:31.882 [INFO    ] [viseron.components.nvr.nvr.camera_1] - NVR for camera Back Door Camera initialized
2025-06-27 13:42:31.883 [INFO    ] [viseron.components] - Setup of domain nvr for component nvr with identifier camera_1 took 0.0 seconds

[roflcoopter]

Can you try to set this as the raw_command for the main stream?
Command is untested but it should work as long as you use a substream as well
It will override the generated command.

Remember to add in you user/pass

ffmpeg -hide_banner -loglevel error -rtsp_transport tcp -i rtsp://*****:*****@192.168.1.9:554/H.264 -f hls -hls_time 5 -hls_segment_type fmp4 -hls_list_size 10 -hls_flags program_date_time+delete_segments -strftime 1 -hls_segment_filename /tmp/viseron/segments/camera_1/%s.m4s -c:v copy -c:a copy /tmp/viseron/segments/camera_1/index

[ph123uk]

Can you try to set this as the raw_command for the main stream? Command is untested but it should work as long as you use a substream as well It will override the generated command.

Remember to add in you user/pass

ffmpeg -hide_banner -loglevel error -rtsp_transport tcp -i rtsp://*****:*****@192.168.1.9:554/H.264 -f hls -hls_time 5 -hls_segment_type fmp4 -hls_list_size 10 -hls_flags program_date_time+delete_segments -strftime 1 -hls_segment_filename /tmp/viseron/segments/camera_1/%s.m4s -c:v copy -c:a copy /tmp/viseron/segments/camera_1/index

Added this, got it to start, but cant live view anything - Don't worry about this further, I'm sure you have much more important things to do - Thankyou

[ph123uk]

To add on to this, just created a fresh, non-nvidia container, with one camera, default settings, and it exibits the exact same behavior. Rules one thing out i suppose :)

[matvey00z]

Regarding frame skipping, I suspect -use_wallclock_as_timestamps option is to blame. It, well, uses wallclock as timestamps... Which results in jitter, meaning where every frame has to be, say, 40ms long, one ends up being 5ms long and another being 75ms long.
On the other hand, input can have unpredictable / broken timestamps, which will break the recording completely, so this option is a saver.
There is another way though, if you know your framerate and it is constant (I can see you set fps: 22 in config). Then, you can override ffmpeg input args:

ffmpeg:
  camera:
    camera_1:  # This value has to be unique across all cameras
      name: Back Door Camera
      ...
      fps: 22
      input_args: ["-r", "22"]

Worked for me!