[Camera Support]: one of the cameras is not recording

[geo903]

Describe the problem you are having

Hello! My system is fully operational, but one of the cameras isn't recording motion. There are recognized events, screenshots, and preview videos. There are no errors in the logs when motion is detected.

Version

0.16.3-9034454

What browser(s) are you using?

No response

Frigate config file

detectors:
  rknn:
    type: rknn
    soc: rk3588
detect:
  enabled: true
  stationary:
    interval: 1
    threshold: 50
motion:
  threshold: 40
  contour_area: 20
  delta_alpha: 0.7
record:
  enabled: True
  retain:
    days: 7
    mode: motion
  alerts:
    retain:
      days: 30
  detections:
    retain:
      days: 30
birdseye:
  enabled: true
  mode: objects
  quality: 1
  restream: true
snapshots:
  enabled: true
  bounding_box: true
  timestamp: true
  crop: false
  retain:
    default: 30
auth:
  enabled: True
  reset_admin_password: false

go2rtc:
  streams:
    gluhovo2:
      - rtsp://admin:xxx@192.168.8.253:8554/profile0
    gluhovo2_detect:
      - rtsp://admin:xxx@192.168.8.253:8554/profile1

  gluhovo2:
    enabled: true
    ffmpeg:
      input_args: preset-rtsp-restream
      hwaccel_args: preset-rk-h264
      inputs:
        - path: rtsp://localhost:8554/gluhovo2
          roles:
            - record
            - detect            
    detect:
      enabled: true
      width: 720
      height: 480
      fps: 5
    objects:
      track:
        - person

Relevant Frigate log output

no

Relevant go2rtc log output

no

FFprobe output from your camera

Input #0, rtsp, from 'rtsp://localhost:8554/gluhovo2':
  Metadata:
    title           : go2rtc/1.9.9
  Duration: N/A, start: 0.040000, bitrate: N/A
  Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1920x1080, 25 fps, 25 tbr, 90k tbn
  Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Object Detector

RKNN

Network connection

Wired

Camera make and model

china cam

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

Looking at your configuration, I can see a few potential issues:

1. Missing record role assignment

Your camera config shows:

inputs:
  - path: rtsp://localhost:8554/gluhovo2
    roles:
      - record
      - detect

However, you have global recording enabled with record: enabled: True and retention set to mode: motion(1). When mode is set to motion, any time audio volume is > min_volume that recording segment for that camera will be kept(2).

2. Verify motion detection is working

Since recording retention is set to mode: motion(1), recordings will only be kept when motion is detected. You mentioned there are recognized events and screenshots, which suggests detection is working, but verify that motion is actually being triggered by checking:

• The motion threshold and contour_area settings are appropriate for your camera
• Motion masks aren't blocking the areas where activity occurs

3. Check storage and retention

With retain: days: 7 under the record section(1), recordings older than 7 days will be automatically deleted. Verify you're looking at recent recordings within this retention window.

4. Recording stream quality

Your detect stream is 720x480 at 5fps, but your record stream from rtsp://localhost:8554/gluhovo2 is 1920x1080 at 25fps. This should work fine, but ensure the recording stream is stable and not experiencing connection issues.

Recommendation:

Check the Frigate logs specifically during times when motion should be detected to see if there are any recording-related errors. Also verify that the /media/frigate/recordings directory has sufficient space and proper permissions.

📚 Sources:

1. Full Reference Config
2. Audio Detectors

---

Have another question? Just tag @inkeep.

[geo903]

1. I tried different streams, but the recording doesn't work.
2. The global camera is set to motion-detection recording mode, and the other 7 cameras are working and recording normally.
3. The storage has been checked and is in order, there are recordings from other cameras
4. I also tried 5 frames, but the recording didn't work.

[hawkeye217]

Recordings require the aac audio codec since they are packaged in an mp4 container. According to the ffprobe output, your camera is providing pcm_mulaw audio.

You should use an output preset to transcode the audio to AAC, eg:

output_args: preset-record-generic-audio-aac

[geo903]

  gluhovo2:
    enabled: true
    ffmpeg:
      input_args: preset-rtsp-restream
      hwaccel_args: preset-rk-h264
      output_args:
        record: preset-record-generic-audio-aac
        detect: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://localhost:8554/gluhovo2 
          roles:
            - record
        - path: rtsp://localhost:8554/gluhovo2_detect
          roles:
            - detect                       
    detect:
      enabled: true
      width: 720
      height: 480
      fps: 5
    objects:
      track:
        - person

It seems it doesn't accept this preset.

      | 2026-01-27 22:52:43 | ffmpeg.gluhovo2.detect | [out#0 @ 0xaaaaedc2f980] Error initializing the muxer for preset-record-generic-audio-aac: Invalid argument
error | 2026-01-27 22:52:43 | ffmpeg.gluhovo2.detect | Error opening output file preset-record-generic-audio-aac.
error | 2026-01-27 22:52:43 | ffmpeg.gluhovo2.detect | Error opening output files: Invalid argument

[hawkeye217]

You should not use an output arg for the detect stream. You only want it for record.

[geo903]

Editing the camera source (add parameter ?video=h264) and enabling audio in the camera's web interface helped. Unfortunately, the option preset-record-generic-audio-aac didn't work, even leaving it in the record section.

go2rtc:
  streams:
    gluhovo2:
      - rtsp://192.168.8.253:8554/profile0?video=h264
    gluhovo2_detect:
      - rtsp://192.168.8.253:8554/profile1?video=h264

Now the recording is going well, you can close the topic