3.2.0 - Proper live streaming #1057
Replies: 3 comments 4 replies
-
First of all — thanks for the continued work on Viseron and the v3.2.0 release! I noticed when updating to v3.2.0 that the Docker image size has increased significantly compared to v3.1.2 — it went from about 4,4 GB to about 13,1 GB (roughly 3× larger). Is the new go2rtc component cause of the growth? |
Beta Was this translation helpful? Give feedback.
-
On the go2rtc, I have added it and the streaming is suburb, but I was thinking, should I be running the go2rtc stream back into the ffmpeg instead of reading from the cameras twice, at the same time? The feed used a uuid it seems to I am not sure what the source would be? Thanks in advance, and thanks for fixing the 3.2 for me.
|
Beta Was this translation helpful? Give feedback.
-
thanks, so i have reolink cameras, with the substream, this is is my working config:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Proper live streaming is now available in Viseron, utilizing the great go2rtc application.
Previously Viseron resorted to using the MJPEG stream for live streaming, which results in low quality and high latency.
With the new
go2rtc
component, Viseron can now stream using WebRTC or MSE, which gives a much better experience.The new Live page is available at
/live
and can be accessed from the sidebar.The Live page is very similar to the Events page, using the same responsiveness so that you can view multiple cameras at once.
In order to use it, you will need to update your configuration to include the new
go2rtc
component.Breaking changes
port
inwebserver
is now deprecated. In order to support the newgo2rtc
streaming server, an NGINX reverse proxy is now included in the container, which listens to the old default port8888
New features
/live
and can be accessed from the main menu. It utilizes the newgo2rtc
component to support WebRTC/MSE streaming.go2rtc
streaming server is now included in the container. This allows for better live streaming and support for more protocols.go2rtc
.YOLO
component which uses Ultralytics YOLOv8 for object detection is now available.Does not work in iOS, because Apple.
The new implementation uses numpy instead of pure SQL queries, which should improve performance at the cost of slightly (temporary) increased memory usage.
You can limit the CPU usage of this calculation by setting the new
tier_check_cpu_limit
config option.You can further tune the workload using the config options
tier_check_batch_size
,tier_check_sleep_between_batches
andtier_check_workers
.Changes
Fixes
coco.names
file in the RPI3 build, which is required for the Darknet object detection model.Developer experience
When cloning using the instructions in the Developer docs, the config folder was not present on the host since
cloneInVolume
was used.The config folder is now dynamically set to the correct path in the Devcontainer using the env variable
VISERON_CONFIG_PATH
.Docker images will be on Docker Hub shortly
All Changes
New Contributors
Full Changelog: v3.1.2...v3.2.0
This discussion was created from the release 3.2.0 - Proper live streaming.
Beta Was this translation helpful? Give feedback.
All reactions