-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[HW Accel Support]: Rockchip 3588 on a Turing RK1 board #10192
Replies: 1 comment · 7 replies
-
looks like network issue, the service is refuising the rtsp connection |
Beta Was this translation helpful? Give feedback.
All reactions
-
ok, what does live view work on then? Is it an internal connection within the container itself then? |
Beta Was this translation helpful? Give feedback.
All reactions
-
yes, it is an internal connection, which is why I'd expect you would want to use 127.0.0.1 not the kub address |
Beta Was this translation helpful? Give feedback.
All reactions
-
ok so switch back to 127.0.0.1:8554 and it is working better (could have sworn i tested this and it failed). The old foscam one is showing Debug and even getting object detection. Not sure why the reolink still throws errors:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Did a bit more testing, by doing a kubernetes deployment to an x86 machine. Exact same frigate config and kubernetes manifests. However the machine i used was a Talos OS based machine vs the ubuntu based for the RK1. They both use flannel though. The image versions are of course different. The x86 Talos OS machine worked just fine no issues at all, both cameras show up right away with no errors. The RK1 ubuntu machine has issues, even though the Cellar camera does end up working it takes awhile before it does so it is not perfect, it throws initial errors. So based on that I feel like the most likely issue is a network issue. But where? Both systems connect back to the same switch and live on the same subnet. The RK1 though has to go through the TuringPi board which adds a switch layer, so that could be a source of issue. Talos and Ubuntu network layers are probably different. So not sure i will be able to solve this, and honestly i wanted to run Frigate on a kube cluster but not did not think I would be able to run it on the RK1 boards for all my cameras anyhow just curious if i could run it for a few. |
Beta Was this translation helpful? Give feedback.
All reactions
-
After letting this sit for a week I noticed I never tested the standard arm64 image on this rockchip. I had been using the custom -rk image that I believe builds in a custom ffmpeg to use hwaccel on the chip. After switching to the standard image an using ffmpeg:#video=copy it works great. So not a network issue, this seems to point to an issue with ffmpeg and maybe my specific cameras or something off in my config. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
So just testing out what these RK1 boards can do, not sure i will use them for Frigate or not but since there is a frigate iamge with rockchip support thought i would give it ago. Note this is a Helm install and I found to reference the "local" rtsp from go2rtc I needed to reference the kube service. However one thing I am never clear on is if I am getting connection refused because ffmpeg is failing or because my kube network is failing. I suspect it is due to the ffmpeg failures since I do get successful connections on the live view.
The issue I run into is I get a ton of ffmpeg crashes and such. Note that both cameras do stream on the live, but do not show anything in the debug view.
cellar is a old foscam
office is a reolink 522a
Version
0.13.2-RK
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
FFprobe output from your camera
Operating system
Debian
Install method
Docker Compose
Network connection
Wired
Camera make and model
reolink 522a. foscam
Any other information that may be helpful
NOT a Docker Compose install, Helm was not an option.
Beta Was this translation helpful? Give feedback.
All reactions