Replies: 2 comments 3 replies
-
The live view uses the substream, the live streams are pretty bad right now. Essentially they are what Viseron "sees". But the recordings should definitely be high res. Could you enable debug logging and restart Viseron? logger:
default_level: debug Seeing your full config wrapped in triple backticks would help as well |
Beta Was this translation helpful? Give feedback.
3 replies
-
Hi @roflcoopter this is my configuration.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi I am very new to viseron so please excuse me if I am doing something wrong.
After my NVR died last week I was looking for alternatives and I came across the viseron software that I find very interesting and promising.
I have configure into viseron 7 outdoor cameras but I was looking to reduce the cpu load so after reading the documentation I created for each camera the corresponding substream. I run the substream of each camera from within vlc to make sure the path was correct and then set it up into the configuration of the viseron and restart it.
For one camera the configuration is the following:
But after I notice that the live video and record that happened was of the substream and not of the main stream. The resolution of both the live view and recording is lower (640x480) and even the frames of the video are very low, ~1-2.
According to what I read in the documentation (https://viseron.netlify.app/components-explorer/components/ffmpeg#substream) I was under the impression that the main stream will be used for live view and recording and the substream for motion detection.
Am I doing something wrong or is this a bug?
Thanks
mpc
Beta Was this translation helpful? Give feedback.
All reactions