[Camera Support]: no playback when veiwing recording from one camera

[Chris87871]

Describe the problem you are having

No playback from one video camera recordings tried in firgate phone app and web browser. Other camera plays fine.

Steps to reproduce

Opened and played video files

Version

14.0

Frigate config file

mqtt:
  enabled: false

detectors:
  deepstack:
    type: deepstack
    api_url: http://192.168.2.4:32168/v1/vision/detection
    api_timeout: 3   # seconds
  cpu1:
    type: cpu
    num_threads: 4
    #cpu2:
      #type: cpu
      #num_threads: 4
#Global Object Settings
objects:
  track:
    - person
  filters:
    person:
      min_area: 100
      max_area: 100000
      threshold: 0.7

birdseye:
  # Optional: Enable birdseye view (default: shown below)
  enabled: true
  # Optional: Restream birdseye via RTSP (default: shown below)
  # NOTE: Enabling this will set birdseye to run 24/7 which may increase CPU usage somewhat.
  restream: false
  # Optional: Width of the output resolution (default: shown below)
  width: 3840
  # Optional: Height of the output resolution (default: shown below)
  height: 2160
  # Optional: Encoding quality of the mpeg1 feed (default: shown below)
  # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
  quality: 1
  # Optional: Mode of the view. Available options are: objects, motion, and continuous
  #   objects - cameras are included if they have had a tracked object within the last 30 seconds
  #   motion - cameras are included if motion was detected in the last 30 seconds
  #   continuous - all cameras are included always
  mode: continuous

go2rtc:
  streams:
    BackYard:
      - ffmpeg:rtsp://admin:@192.168.2.100:554/stream0

    BackYard_Sub:
      - ffmpeg:rtsp://admin:@192.168.2.100:554/stream1

    Window:
      - ffmpeg:rtsp://admin:@192.168.2.102:554/live/main

    Window_Sub:
      - ffmpeg:rtsp://admin:@192.168.2.102:554/live/sub

    webrtc:
    candidates:
      - 192.168.2.4:8555
      - stun:8555

cameras:
  BackYard:
    birdseye:
      order: 1
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/BackYard?video&audio
          input_args: preset-rtsp-restream
          roles:
            - record
            - audio
        - path: rtsp://127.0.0.1:8554/BackYard_Sub?video&audio
          input_args: preset-rtsp-restream
          roles:
            - detect

    motion:
      threshold: 40
      contour_area: 10
      improve_contrast: 'true'
  Window:
    birdseye:
      order: 2
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/Window?video&audio
          input_args: preset-rtsp-restream
          roles:
            - record
            - audio
        - path: rtsp://127.0.0.1:8554/Window_Sub?video&audio
          input_args: preset-rtsp-restream
          roles:
            - detect
detect:
  width: 640
  height: 480
  fps: 5
  max_disappeared: 25

record:
  enabled: true
  retain:
    days: 7
    mode: motion
  events:
    retain:
      default: 14
      mode: active_objects

snapshots:
  enabled: true
  retain:
    default: 30


version: 0.14

Relevant log output

2024-08-09 08:52:56.784480873  [INFO] Preparing Frigate...
2024-08-09 08:52:56.797956015  [INFO] Starting Frigate...
2024-08-09 08:52:58.691806055  [2024-08-09 08:52:58] frigate.app                    INFO    : Starting Frigate (0.14.0-da913d8)
2024-08-09 08:52:58.691888430  [2024-08-09 08:52:58] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-08-09 08:52:58.727701063  [2024-08-09 08:52:58] frigate.util.config            INFO    : frigate config does not need migration...
2024-08-09 08:52:58.780542028  [2024-08-09 08:52:58] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2024-08-09 08:52:58.823789236  [2024-08-09 08:52:58] peewee_migrate.logs            INFO    : Starting migrations
2024-08-09 08:52:58.824784972  [2024-08-09 08:52:58] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-08-09 08:52:58.843713610  [2024-08-09 08:52:58] frigate.app                    INFO    : Recording process started: 382
2024-08-09 08:52:58.849186804  [2024-08-09 08:52:58] frigate.app                    INFO    : Recording process started: 383
2024-08-09 08:52:58.854334865  [2024-08-09 08:52:58] frigate.app                    INFO    : go2rtc process pid: 98
2024-08-09 08:52:58.889737604  [2024-08-09 08:52:58] detector.deepstack             INFO    : Starting detection process: 410
2024-08-09 08:52:58.895743802  [2024-08-09 08:52:58] detector.cpu1                  INFO    : Starting detection process: 412
2024-08-09 08:52:58.896093016  [2024-08-09 08:52:58] frigate.app                    INFO    : Output process started: 414
2024-08-09 08:52:58.900842102  [2024-08-09 08:52:58] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2024-08-09 08:52:58.918062132  [2024-08-09 08:52:58] frigate.app                    INFO    : Camera processor started for BackYard: 428
2024-08-09 08:52:58.924277258  [2024-08-09 08:52:58] frigate.app                    INFO    : Camera processor started for Window: 429
2024-08-09 08:52:58.930217794  [2024-08-09 08:52:58] frigate.app                    INFO    : Capture process started for BackYard: 435
2024-08-09 08:52:58.937126218  [2024-08-09 08:52:58] frigate.app                    INFO    : Capture process started for Window: 445

Operating system

Debian

Install method

Docker Compose

Network connection

Wireless

Camera make and model

Ctv-vision

Any other information that may be helpful

No response

[hawkeye217]

This is often caused by using a codec (h265/+) that's incompatible with your browser.

[Chris87871]

Camera say it's running h.264

[hawkeye217]

It would be helpful to see a screenshot of your browser dev tools network pane when you try to play the recordings, then.

[Chris87871]

[Chris87871]

So far the newer recording are working just not the one now, odd may be got corrupted.

[hawkeye217]

Great, will close this then. Feel free to reopen if you're still having problems.

[Chris87871]

So some still are not playing but have audio during play back