motiejus/jakstys.lt
1
Fork 0
Code Releases Activity

some pics and changes

Browse Source
This commit is contained in:
Motiejus Jakštys
2025-03-19 15:39:49 +00:00
parent 94adf999c3
commit aa7b215eb8
3 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
assets/_/2025/construction-site-surveillance/frigate-config.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 56 KiB

BIN
assets/_/2025/construction-site-surveillance/grafana-traffic.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 42 KiB

9
content/log/2025/construction-site-surveillance.md
View File

@@ -142,9 +142,12 @@ a yet another tailscale+headscale recommendation.
## Bandwidth and codec considerations ## Bandwidth and codec considerations
I am pushing two camera streams, encoded in h.265 (resolutions TBD) using a Two camera streams (`2688x752` and `1920x1080`), encoded in h.265 consume
constant 4.1Mb/s. Both streams are transcoded to h.264 via go2rtc and then sent around 1.8Mb/s 24/7. Both streams are transcoded to h.264 via go2rtc and then
over to Frigate and live view. sent over to Frigate and live view. and
Every 5 minutes a separate process captures a full-resolution picture of both
cameras: `5376x1520` and `2560x1440`.
Using exactly the same parameters (resolution, fps), but with h.264, the Using exactly the same parameters (resolution, fps), but with h.264, the
bandwidth grows to 11 Mb/s. Which may not sound like a lot with today's fiber bandwidth grows to 11 Mb/s. Which may not sound like a lot with today's fiber