I'm not sure the audio is the issue, AAC is a standard codec. You can try disabling it by setting audio_codec: null under the recorder block for the camera

4 minutes ago, roflcoopter said:

I'm not sure the audio is the issue, AAC is a standard codec. You can try disabling it by setting audio_codec: null under the recorder block for the camera

So what's causing these errors?

My posts from last year with the same errors:

https://forums.unraid.net/topic/96774-support-viseron-v3-self-hosted-local-only-nvr-and-ai-computer-vision-software/page/2/#findComment-1481711

https://forums.unraid.net/topic/96774-support-viseron-v3-self-hosted-local-only-nvr-and-ai-computer-vision-software/page/2/#findComment-1484508

Edited December 8, 2025Dec 8 by itlists

Its sadly impossible for me to say without access to the same hardware.

Did you try disabling audio?

My only recommendation is that you fiddle with the FFmpeg command until you find something that works, and then we can adapt it to meet the needs of Viseron.

On 12/9/2025 at 4:26 AM, roflcoopter said:

Its sadly impossible for me to say without access to the same hardware.

Did you try disabling audio?

My only recommendation is that you fiddle with the FFmpeg command until you find something that works, and then we can adapt it to meet the needs of Viseron.

Appreciate the reply, thanks. I'm not going to bother with the time to fiddle with various settings and configuration parameters.

I tried AgentDVR which simply works out of the box! Its not as slick and intuitive to use or setup as Viseron but the time savings is huge. One huge downside is its freemium model which allows only 1 local user account in the free version. I'm not comfortable with using the tool with admin priv all the time.

On 12/9/2025 at 4:26 AM, roflcoopter said:

Its sadly impossible for me to say without access to the same hardware.

Did you try disabling audio?

My only recommendation is that you fiddle with the FFmpeg command until you find something that works, and then we can adapt it to meet the needs of Viseron.

is there a way to disable SEI for ffmpeg in the config file?

Hello @roflcoopter

Live view is finally working, along with recording. The config file is just the template with cam login info and stream url added.

Between Main and Substream - which stream does Viseron record and which stream does it show in live view?

There are recording for some motion events but when trying to view any recording, this error is shown: "Playback cannot continue. No available working or supported playlists."

Screenshots attached.

For transparency if anyone has similar issues, the solution to the problem above was transcoding to supported formats:
https://github.com/roflcoopter/viseron/discussions/1180

I love this software. I've been playing around with it for a few days now, and it's really great. But there's one issue I can't seem to figure out...

With just one camera—a Tapo—it's using up 25% of my CPU. That seems like a lot to me; it's an Intel J4105, which isn't exactly powerful, but it seems excessive for an integrated iGPU. And I can't figure out why.

Any ideas?

 

go2rtc:
  streams:
    entrada:
      - rtsp://****@192.168.1.102:554/stream1
    entradaLow:
      - rtsp://****@192.168.1.102:554/stream2

ffmpeg:
  camera:
    entrada:
      name: Entrada
      host: localhost
      port: 8554
      path: /entrada
      fps: 10
      audio_codec: aac
      recorder:
        audio_codec: aac 
      substream:
        port: 8554
        path: /entradaLow

mog2:
  motion_detector:
    cameras:
      entrada:
        fps: 1

darknet:
  object_detector:
    half_precision: true
    cameras:
      entrada:
        fps: 1
        scan_on_motion_only: true
        labels:
        - label: person
          confidence: 0.8
          trigger_event_recording: true
        zones:
        - name: Puerta
          labels:
          - label: person
            confidence: 0.8
            trigger_event_recording: true
          coordinates:
          - x: 20
            y: 77
          - x: 1219
            y: 82
          - x: 1091
            y: 718
          - x: 95
            y: 714

nvr:
  entrada:

@roflcoopter said me to add the LIBVA_DRIVER_NAME variable with i965 value, so I could use the previous driver, which does support my iGPU, and power consumption dropped to 5%.

Problem solved!