Replies: 3 comments
-
Ok, so my issue with it defaulting to MSE is because of the AAC audio coming from some of my cameras. I can't change it in the cameras, but go2rtc can make quick work of transcoding to opus for me, so that should be solved once I update my config. And, for the timeline view, it apparently just didn't handle those exact camera resolutions as a group. Once I added the rest of the cameras, everything shows on the page as expected. 11 cameras doing continuous recording with motion detection using MOG2 and my raspberry pi 5 only sits at about 20% cpu usage. I have a coral, so I may throw that in the mix next. Great work on this project, thank you :) |
Beta Was this translation helpful? Give feedback.
-
Glad you got it sorted! WebRTC can be a bit tricky to get working. The support in Viseron is still very new so documentation is not great yet, will try to get write down some troubleshooting steps so other people dont have the same problem as you do. The view should show all cameras, regardless of number or resolution, but its a complex implementation so there might be some bug hidden in there |
Beta Was this translation helpful? Give feedback.
-
Yeah, it worked out. Most of my cameras only do AAC, which is fine for recordings, but not WebRTC. Changed the go2rtc to copy the existing audio and video, but also add an opus audio track and now WebRTC works fine.
Up next on my list is setting up the Coral and trying out notifications. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I searched before posting and didn't see anything but I may have missed it, so posting a discussion here for now.
First issue, I've set up the go2rtc component with the webrtc section:
But, live view always uses MSE in any browser I've tried (Chrome on Win11, Safari on mac, etc).
I noticed that the WebRTC port wasn't mapped in the default compose example, so I added those for testing as well as the other go2rtc ports:
But, I still can't get anything to actually use WebRTC. If I go directly to the now exposed go2rtc through :1984 I can click the WebRTC links and they work fine.
Second, the only other thing I've run into is that the timeline view doesn't seem to arrange cameras correctly if I select too many. So far, I only have 6 cameras set up, but will eventually have 11.
In the screenshot, the cameras on the bottom row are cut off and there doesn't seem to be a way to scroll down. I'd rather have them all resize to fit on one screen, but the ability to scroll would work as well.
If I use the fullscreen button, then I can view them all but can't use the timeline controls at the same time.
Beta Was this translation helpful? Give feedback.
All reactions