As soon as I add a second camera, nothing works

[JPMakesStuff]

Describe the problem you are having

Added one Axis IP (POE) camera using go2rtc for both streams = works fine
Used that same camera with a go2rtc stream for detect, and a direct to camera RTSP stream for record = works fine

Added a second Axis IP (POE) camera using go2rtc = nothing works, both cameras
using direct camera streams = nothing works, both cameras
using go2rtc and direct = nothing works, both cameras
... both cameras, the original working one, and the new one show "no frames have been received check error logs" and the logs say things like "frontdoor_frame0 not found" or "unable to read frames from the ffmpeg process"
funny thing is if I click on a camera, in the main view, it does show me that camera, however motion detection doesn't seem to be working

using...
environment:

• NVIDIA_VISIBLE_DEVICES=all
• NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
  runtime: nvidia

confirmed...
docker exec -it frigate nvidia-smi
...shows the RTX 3050 is available to docker

tried...
services:
frigate:
# ...
shm_size: "1g"
...same problem

tried...
ffmpeg:
path: "5.0"
...same problem

Version

0.16.1-e664cb2

Frigate config file

mqtt:
  enabled: false

detectors:
  coral:
    type: edgetpu
    device: usb

record:
  enabled: true
  retain:
    days: 7
    mode: motion

go2rtc:
  streams:
    frontdoor:
      - rtsp://192.168.x.x/axis-media/media.amp?camera=3&audio=1

cameras:
  frontdoor:
    ffmpeg:
      hwaccel_args: preset-nvidia
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://192.168.x.x/axis-media/media.amp?camera=3&audio=0
          input_args: preset-rtsp-generic
          roles: [detect]
        - path: rtsp://127.0.0.1:8554/frontdoor
          input_args: preset-rtsp-restream
          roles: [record]
    detect:
      enabled: true
      fps: 10

detect:
  enabled: true
version: 0.16-0

Relevant Frigate log output

Too many unprocessed recording segments in cache for sidefront. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...

the file sidefront_frame0 not found

sidefront: Unable to read frames from ffmpeg process.

Relevant go2rtc log output

Starting go2rtc healthcheck service...

...that is the last entry

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    image: ghcr.io/blakeblackshear/frigate:stable
    restart: unless-stopped
    stop_grace_period: 30s
    shm_size: "512mb"
    volumes:
      - ./config:/config
      - /mnt/frigate:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs: { size: 1000000000 }
    ports:
      - "8971:8971"       # Frigate UI (HTTPS)
      - "8554:8554"       # RTSP relay (optional)
    devices:
      - /dev/bus/usb:/dev/bus/usb
    environment:
      - NVIDIA_VISIBLE_DEVICES=all
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
    runtime: nvidia

Object Detector

Coral

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

The second camera I'm adding is not a normal 1080p rectangle resolution, rather it's a dewarped 360 view that is flattened by the camera to Panorama 2276 x 640 ... could this have something to do with the problem?

[inkeep-ai-assistant[bot]]

Your issue where adding a second camera causes both cameras to fail, with errors like “frame0 not found” and “unable to read frames from the ffmpeg process,” could be related to several configuration and compatibility factors:

1. Non-Standard Resolution: Cameras with non-standard or unusual resolutions (like 2276x640) may cause issues for ffmpeg or Frigate. The documentation recommends adjusting the camera’s detect width and height to a standard aspect ratio (e.g., 640x360, 1280x720) if you encounter display or processing problems. Try setting the detect resolution for the problematic camera to a standard value and see if this resolves the errors(1).

2. Hardware Acceleration and Resources: You’re using NVIDIA hardware acceleration with preset-nvidia. The documentation notes that hardware acceleration should be properly configured and compatible with your system. Ensure that your container has access to the GPU device and that there are no conflicts when multiple streams are decoded simultaneously. Check the output of nvidia-smi and ensure all ffmpeg processes are running as expected inside the container(2).

3. shm_size: Frigate requires sufficient shared memory (shm_size) for decoding multiple camera streams. If you have two high-resolution or high-frame-rate feeds, you may need to increase shm_size further (e.g., “2g”) to avoid memory exhaustion(3).

4. Input Args Presets: When mixing restreamed (go2rtc) and direct camera streams, ensure that the correct input_args presets are used for each input. If you use a restream (like rtsp://127.0.0.1:8554/frontdoor), you must use preset-rtsp-restream as the input_args. Using the wrong preset can cause ffmpeg to fail to read frames(4).

5. go2rtc Stream Naming and Matching: The name of the go2rtc stream should exactly match the name used in your camera configuration. Double-check for typos or mismatches(5).

6. Logs and Debugging: Use the /api/go2rtc/streams endpoint to verify that both streams are available and healthy in go2rtc(6). Also, check the Frigate and go2rtc logs for any additional errors or warnings.

Action Steps:

• Set the detect width and height for the problematic camera to a standard value (e.g., 1280x720) in your config.
• Increase your container’s shm_size (e.g., to “2g”) to ensure enough shared memory for multiple streams.
• Ensure that input_args for each ffmpeg input match the stream type (preset-rtsp-restream for restreams, preset-rtsp-generic for direct).
• Confirm that your go2rtc stream names are consistent and correct.
• Visit /api/go2rtc/streams to confirm stream status and check logs for further ffmpeg errors.

If the camera’s non-standard resolution is the cause, adjusting it to a standard resolution is the recommended first step(1).

📚 Sources:

1. Live View
2. Video Decoding
3. Full Reference Config
4. FFmpeg presets
5. Configuring go2rtc
6. Restream

---

Have another question? Just tag @inkeep.

[NickM-27]

we will need to see your config with the second camera, along with a full copy of logs