[Config Support]: Artifacts and wrong colors on live stream after updating to 0.14 #13568

NickyM · 2024-09-05T10:30:48Z

NickyM
Sep 5, 2024

Checklist

I have updated to the latest available Frigate version.
I have cleared the cache of my browser.
I have tried a different browser to see if it is related to my browser.
I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.

Describe the problem you are having

After updating til 0.14 (and 0.14.1), my camera liveviews are a mesh. Recordings however is fine.
This happens both on root page which multiple streams and on single camera views.
Sometime it happens to all - sometimes to some - other times to none. Sometimes it takes a few seconds.
Tested on multiple computers and phones.
It doesnt seem to happen in Home Assistant with Frigate integration.

Steps to reproduce

Navigate to root page
Sometimes wait a few seconds
Osbserve how colors is messed up and stream have artifacts

Version

0.14.1-f4f3cfa

In which browser(s) are you experiencing the issue with?

Google Chrome 127.0.6533.120

Frigate config file

mqtt:
  host: 10.4.2.6
  user: frigate
  password: [redacted]

cameras:
  driveway:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[redacted]@10.4.3.11:80/cam/realmonitor?channel=1&subtype=0
          roles:
            - rtmp
            - record
            - detect
      hwaccel_args: preset-vaapi
    detect:
      width: 2688
      height: 1520
    objects:
      track:
        - car
        - person
        - cat
        - dog
      filters:
        person:
          mask:
            - 1342,253,1465,241,1453,114,1349,108
    zones:
      car_entry:
        coordinates: 49,690,680,389,665,82,383,175,386,335,0,516
        objects:
          - car
      yard:
        coordinates: 
          390,363,361,267,358,185,422,174,412,153,883,50,889,254,990,239,991,35,1264,28,1252,218,1356,211,1375,24,1946,66,2312,160,2666,0,2688,1520,0,1520,0,511
        objects:
          - person
          - cat
          - dog
      alert_area:
        coordinates: 
          444,160,853,64,875,261,1037,264,1022,49,1269,28,1248,219,1355,217,1358,21,1894,78,2401,173,2688,1520,0,1520,22,586,517,396,421,384
        objects:
          - car
          - person
    review:
      alerts:
        required_zones:
          - car_entry
          - yard
  frontyard:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[redacted]@10.4.3.10:80/cam/realmonitor?channel=1&subtype=0
          roles:
            - rtmp
            - record
            - detect
      hwaccel_args: preset-vaapi
    detect:
      width: 1920
      height: 1080
    record:
      retain:
        days: 14
        mode: motion
    objects:
      track:
        - car
        - person
        - cat
        - dog
    zones:
      entry_way:
        coordinates: 1127,0,1049,99,770,106,815,0
        objects:
          - car
      everything:
        coordinates: 
          1920,1080,1920,75,1697,0,1545,0,1540,144,1487,128,1492,0,1375,0,1369,90,1323,81,1328,0,295,0,0,64,0,1080
        objects:
          - person
          - cat
          - dog
      light_area:
        coordinates: 
          1315,1080,1920,237,1920,75,1697,0,1545,0,1540,144,1487,128,1492,0,1375,0,1369,90,1323,81,1328,0,295,0,0,64,0,1080
        objects:
          - person
      backdoor:
        coordinates: 0.003,0.118,0.017,0.361,0.183,0.349,0.15,0.055
        loitering_time: 0
        objects: person
      non-car-area:
        coordinates: 
          0.134,0.889,0.159,0.985,1,1,1,0,0.561,0.053,0.525,0.298,0.153,0.591,0.24,0.633,0.243,0.754,0.197,0.851
        inertia: 3
        loitering_time: 0
        objects: person
    motion:
      mask:
        - 0.108,0.854,0.19,0.865,0.244,0.771,0.229,0.638,0.145,0.577,0.062,0.615
        - 0.03,0.404,0.068,0.611,0.16,0.564,0.163,0.495,0.082,0.381
        - 1,0.082,1,0,0.876,0
        - 0.965,0.046,0.963,0.077,0.757,0.078,0.752,0.044
        - 0.711,0.071,0.693,0.06,0.695,0,0.716,0
        - 0.805,0,0.801,0.136,0.78,0.118,0.779,0
    review:
      alerts:
        required_zones:
          - backdoor
          - entry_way
          - non-car-area
  patio:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[redacted]@10.4.3.13:80/cam/realmonitor?channel=1&subtype=0
          roles:
            - rtmp
            - record
            - detect
      hwaccel_args: preset-vaapi
    detect:
      width: 2688
      height: 1520
#    record:
#      retain:
#        days: 14
#        mode: motion
    objects:
      track:
        - person
        - cat
        - dog
  workshop:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[redacted]@10.4.3.12:80/cam/realmonitor?channel=1&subtype=0
          roles:
            - rtmp
            - record
            - detect
      hwaccel_args: preset-vaapi
    detect:
      width: 2688
      height: 1520
#    record:
#      retain:
#        days: 14
#        mode: motion
    objects:
      track:
        - person
        - cat
        - dog
    zones:
      alert_area:
        coordinates: 0,1520,2688,1520,2666,852,1456,505,1420,367,607,275,73,328
    review:
      alerts:
        required_zones: alert_area
record:
  enabled: true
  events:
    retain:
      default: 14

birdseye:
  enabled: true
  mode: continuous
  width: 1920
  height: 1080

detectors:
  coral:
    type: edgetpu
    device: usb
version: 0.14

docker-compose file or Docker CLI command

version: "3.9"

volumes:
  config_share_pool:
    driver_opts:
      type: nfs
      o: addr=10.4.0.3,nfsvers=3 # ip address of synology
      device: :/mnt/Pool/Heimdall/Frigate # nfs mount path

  media_share:
    driver_opts:
      type: nfs
      o: addr=10.4.0.3,nfsvers=3 # ip address of synology
      device: :/mnt/Stripe/Frigate/frigate # nfs mount path

services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: always
    image: ghcr.io/blakeblackshear/frigate:0.14.1
    shm_size: "512mb" # update for your cameras based on calculation above
    devices:
      - /dev/bus/usb:/dev/bus/usb  # Passes the USB Coral, needs to be modified for other versions
      - /dev/dri/card0:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - config_share_pool:/config
      - media_share:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000

    ports:
      - "5000:5000"
      - "1935:1935" # RTMP
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      FRIGATE_RTSP_PASSWORD: "[redacted]"
    labels:
      autoheal-frigate: true
      
  autoheal:
    deploy:
      replicas: 1
    environment:
      AUTOHEAL_CONTAINER_LABEL: autoheal-frigate
    image: willfarrell/autoheal:latest
    network_mode: none
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock

Relevant Frigate log output

2024-09-03 21:49:54.247741912  [INFO] Preparing Frigate...
2024-09-03 21:49:54.264458188  [INFO] Starting Frigate...
2024-09-03 21:49:56.020543236  [2024-09-03 21:49:56] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-09-03 21:49:56.020946898  [2024-09-03 21:49:56] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-09-03 21:49:56.059690018  [2024-09-03 21:49:56] frigate.util.config            INFO    : frigate config does not need migration...
2024-09-03 21:49:56.373765179  [2024-09-03 21:49:56] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-09-03 21:50:57.934518529  [2024-09-03 21:50:57] peewee_migrate.logs            INFO    : Starting migrations
2024-09-03 21:50:57.937064387  [2024-09-03 21:50:57] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-09-03 21:50:57.962934189  [2024-09-03 21:50:57] frigate.app                    INFO    : Recording process started: 479
2024-09-03 21:50:57.967790252  [2024-09-03 21:50:57] frigate.app                    INFO    : Recording process started: 480
2024-09-03 21:50:57.972708689  [2024-09-03 21:50:57] frigate.app                    INFO    : go2rtc process pid: 110
2024-09-03 21:50:58.009807686  [2024-09-03 21:50:58] frigate.app                    INFO    : Output process started: 510
2024-09-03 21:50:59.789797048  [2024-09-03 21:50:59] frigate.app                    INFO    : Camera processor started for driveway: 563
2024-09-03 21:50:59.796639666  [2024-09-03 21:50:59] frigate.app                    INFO    : Camera processor started for frontyard: 564
2024-09-03 21:50:59.802877204  [2024-09-03 21:50:59] frigate.app                    INFO    : Camera processor started for patio: 565
2024-09-03 21:50:59.810223817  [2024-09-03 21:50:59] frigate.app                    INFO    : Camera processor started for workshop: 566
2024-09-03 21:50:59.819255206  [2024-09-03 21:50:59] frigate.app                    INFO    : Capture process started for driveway: 579
2024-09-03 21:50:59.830862010  [2024-09-03 21:50:59] frigate.app                    INFO    : Capture process started for frontyard: 589
2024-09-03 21:50:59.839547780  [2024-09-03 21:50:59] frigate.app                    INFO    : Capture process started for patio: 593
2024-09-03 21:50:59.844428577  [2024-09-03 21:50:59] frigate.app                    INFO    : Capture process started for workshop: 596
2024-09-03 21:51:00.835349080  [2024-09-03 21:50:58] detector.coral                 INFO    : Starting detection process: 508
2024-09-03 21:51:00.840664878  [2024-09-03 21:50:58] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-09-03 21:51:00.841158593  [2024-09-03 21:51:00] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-09-05 06:56:38.244854213  [2024-09-05 06:56:38] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-09-05 06:57:05.876646990  [2024-09-05 06:57:05] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-09-05 06:57:27.518808739  [2024-09-05 06:57:27] frigate.comms.dispatcher       INFO    : Setting motion threshold for frontyard: 30
2024-09-05 06:57:27.549562351  [2024-09-05 06:57:27] frigate.comms.dispatcher       INFO    : Setting motion contour area for frontyard: 10
2024-09-05 06:58:44.800604598  [2024-09-05 06:58:44] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-09-05 06:58:45.575157549  [2024-09-05 06:58:45] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-09-05 06:59:14.551251304  [2024-09-05 06:59:14] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-09-05 06:59:19.891293853  [2024-09-05 06:59:19] frigate.comms.dispatcher       INFO    : Setting motion threshold for workshop: 30
2024-09-05 06:59:19.911215860  [2024-09-05 06:59:19] frigate.comms.dispatcher       INFO    : Setting motion contour area for workshop: 10

Relevant go2rtc log output

2024-09-03 21:49:54.255778774  [INFO] Preparing new go2rtc config...
2024-09-03 21:49:54.618680089  [INFO] Starting go2rtc...
2024-09-03 21:49:54.733092960  21:49:54.732 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-03 21:49:54.733097026  21:49:54.732 INF config path=/dev/shm/go2rtc.yaml
2024-09-03 21:49:54.733098800  21:49:54.732 INF [rtsp] listen addr=:8554
2024-09-03 21:49:54.733100553  21:49:54.732 INF [webrtc] listen addr=:8555/tcp
2024-09-03 21:49:54.733339384  21:49:54.733 INF [api] listen addr=:1984
2024-09-03 21:50:04.246730753  [INFO] Starting go2rtc healthcheck service...

Operating system

Debian

Install method

Docker Compose

Network connection

Wired

Camera make and model

1 x Dahua IPC-HDW4221E, 1 x Dahua IPC-HDW4431EM-AS, 2 x Dahua IPC-HFW1431S-S4

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Frigate is running in docker, on a virtual Ubuntu hosted by Proxmox.

Answered by hawkeye217

Sep 5, 2024

Please see the FAQ, Usage question 15.

View full answer

hawkeye217 · 2024-09-05T10:37:56Z

hawkeye217
Sep 5, 2024
Collaborator

Please see the FAQ, Usage question 15.

4 replies

NickyM Sep 5, 2024
Author

Well, well, well - thank you.

Resolution was correct and both height and width could be divided by 4.
Added go2rtc to my config file and now streams has no artifacts and is better quality than in 0.13 - it takes 1-2 seconds for them to load now though.

hawkeye217 Sep 5, 2024
Collaborator

See the camera settings recommendations in the docs. You’ll want to adjust your I-frame interval. https://docs.frigate.video/configuration/live#camera-settings-recommendations

NickyM Sep 5, 2024
Author

Oh my. The interval was only alligned for the two oldest cameras. Thanks again.
That + restreaming instead of multiple stream fixed it.

hawkeye217 Sep 5, 2024
Collaborator

Great! Happy to help.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Config Support]: Artifacts and wrong colors on live stream after updating to 0.14 #13568

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Config Support]: Artifacts and wrong colors on live stream after updating to 0.14 #13568

NickyM Sep 5, 2024

Checklist

Describe the problem you are having

Steps to reproduce

Version

In which browser(s) are you experiencing the issue with?

Frigate config file

docker-compose file or Docker CLI command

Relevant Frigate log output

Relevant go2rtc log output

Operating system

Install method

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 1 comment · 4 replies

hawkeye217 Sep 5, 2024 Collaborator

NickyM Sep 5, 2024 Author

hawkeye217 Sep 5, 2024 Collaborator

NickyM Sep 5, 2024 Author

hawkeye217 Sep 5, 2024 Collaborator

NickyM
Sep 5, 2024

Replies: 1 comment 4 replies

hawkeye217
Sep 5, 2024
Collaborator

NickyM Sep 5, 2024
Author

hawkeye217 Sep 5, 2024
Collaborator

NickyM Sep 5, 2024
Author

hawkeye217 Sep 5, 2024
Collaborator