Closed salabur closed 1 year ago
as you can see in the uploaded clip I lied and the error is at 4 seconds in... and also present in this viewer ;(
docker file
version: "3.9"
# volumes:
# env_files:
# driver_opts:
# type: "nfs"
# o: "addr=192.168.1.222,nolock,soft,rw"
# device: ":/docker/docker-compose_files/env/"
# frigate_config:
# driver_opts:
# type: "nfs"
# o: "addr=192.168.1.222,nolock,soft,ro"
# device: ":/docker/frigate/config/" #config.yml"
networks:
frigate_network:
# external: false
# driver: bridge
services:
frigate:
image: ghcr.io/blakeblackshear/frigate:0.12.0-beta7
container_name: frigate
environment:
- TZ=Europe/Berlin
privileged: true # this may not be necessary for all setups
shm_size: "512mb"
#environment:
# FRIGATE_RTSP_PASSWORD: "frigate"
# devices:
# - /dev/bus/usb:/dev/bus/usb
# - /dev/dri:/dev/dri # for intel hwaccel, needs to be updated for your hardware
# - /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions
# - /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
# - /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- /media/nvr/config/config.yml:/config/config.yml #:ro
- /media/nvr/media:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
# - /media/nvr/config/frigate/frigate-go2rtc.yaml:/config/frigate-go2rtc.yaml
# - type: volume
# source: frigate_config
# target: /config/config.yml
# volume:
# nocopy: true
# - .:/lab/frigate:cached
- /dev/bus/usb:/dev/bus/usb
- /dev/video10:/dev/video10
- /dev/video11:/dev/video11
- /dev/video12:/dev/video12
- /dev/video18:/dev/video18
- /dev/video19:/dev/video19
- /dev/video31:/dev/video31
- /dev/media0:/dev/media0
- /dev/media2:/dev/media2
ports:
- "5000:5000"
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
restart: unless-stopped
networks:
- frigate_network
What browser are you using? We already tell the viewer to skip and try playing again. However, we have to rely on the browser to playback and if it can't handle the corrupt section then it can't. The errors could definitely be the issue. I've seen this happen with bad data from a cheap camera and chrome couldn't play it back but safari could no problem.
I´m using mainly the ha app on android (iframe) All pcs use chrome as default. These two options do not work same as edge browse. Firefox and Safari on ios work fine. I try to reduce the bitrate from the cameras.
Yes in that case it could very well be a device issue.
Hi, I have same issue with one Hikvision camera. In my case it's definetely Frigate or Go2RTC issue, as with Frigate 0.11 it can play recorded media, with 0.12 recorded data can't be played. Audio is definetely AAC.
this is go2rtc info:
{
"producers": [
{
"type": "RTSP source",
"url": "rtsp://192.168.51.12:554/cam/realmonitor?channel=1\u0026subtype=0/",
"remote_addr": "192.168.51.12:554",
"user_agent": "go2rtc/1.1.1",
"medias": [
"video, sendonly, 96 H264/90000",
"audio, sendonly, 97 MPEG4-GENERIC/8000",
"audio, recvonly, 8 PCMA/8000"
],
"tracks": [
"96 H264/90000, sinks=1",
"97 MPEG4-GENERIC/8000, sinks=1"
],
"recv": 1078882189
}
],
"consumers": [
{
"type": "RTSP client",
"url": "rtsp://localhost:8554/go_garaz",
"remote_addr": "127.0.0.1:38568",
"user_agent": "FFmpeg Frigate/0.12.0-66881eb",
"medias": [
"video, recvonly, 96 H264/90000",
"audio, recvonly, 97 MPEG4-GENERIC/8000"
],
"tracks": [
"96 H264/90000, sinks=1",
"97 MPEG4-GENERIC/8000, sinks=1"
],
"send": 1075756813
}
]
}
As you can see receive is higher than send.
@pszafer looks like you are running an older beta, I'd suggest updating.
Changing the bitrate has not made any difference.
Also tried changing
rtsp://user:pass@192.168.1.70:554/h264Preview_01_main
to
ffmpeg:http://192.168.1.70/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=user&password=pass#video=copy#audio=copy
and different variants of video=copy#audio=copy
/ video=copy#audio=aac
/ video=copy
None of this seemed to have any effect.
Re-encoding of the stream would be not very effective.
Anybody has any idea or direction I could try? Also to other users of the Reolink RLC-520A, everything fine for you? Changing the browser is not good for the WAF and everything is integrated into home assistant and consequently viewed embedded within the app.
Please also comment if I should close this issue as this is in my understanding not an direct frigate problem.
I'd suggest asking reolink for better firmware
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi. I see there has been no activity on this thread for a while now, Has anyone found something to fix this problem? I have the same problem on one of my cameras (reolink doorbell POE). The rest of the cameras (different Reolkink and TAPO models) work perfectly. The problem with the camera is always playing back recordings. The real time video does not give any problem.
Similar problem, same error message. Happens in the Home Assistant app (using the Frigate Proxy add-in and Home Assistant OS) whereas the recordings stream just fine from the latest stable Opera mobile browserbon android.
Same issue here, running Reolink doorbell camera, stream works fine. Also downloading the clip works.
Running Chrome on windows browser
Describe the problem you are having
"The media playback was aborted due to a corruption problem or because the media used features your browser did not support."
Error is shown when viewing some (like 5%) of the recorded events in the WebUI. The event will start to play and at some (100% reproducible) time will interrupt and show the error. The file(s) containing the event can be viewed with vnc on win 10 64bit without any error shown. Even if the recorded files are corrupt in some mater (I cant say for sure), maybe the process used for playing the clips can be set to ignore errors if possible and continue from the next keyframe or something like that?
I have attached one of the relevant files, the playback is interrupted at about 2 seconds into the clip.
There are some errors in the logs, but none correspond to the time of the recording or playback.
Version
0.12.0-66881EB (0.12.0-beta7)
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
3x Reolink RLC-520A / Firmware with Interframe Space Setting (1) and fixed framerate
Any other information that may be helpful
Raspi 4B @1.9Ghz 512GB SSD for sys and media (powered USB-Hub together with coral) DietPi 64bit Docker