Replies: 2 comments
|
Hey, sorry for the late reply. Actually, MJPEG isn't supported via WebRTC/MSE. I've made a note of it and will see if it can be easily added (possibly as another streaming method in the UI) The real issue arises with HomeKit and other clients that expect H.264/H.265. In that case, we’d need to implement an auto-transcoding layer (with GPU support) |
0 replies
|
Thanks for your answer. I was just about to develop an auto-transcoder based on a Raspi Pi Zero ... just catching MJPEG Streams, transcoding them and sending RTSP out ... quick an dirty. But I can also wait two more days for the internal solution 😇 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I noticed that my DIY ESP32 CameraWebServer (MJPEG only) works perfectly in the integrated go2rtc UI, but not in the camera.ui live view.
Before opening a bug report, I just wanted to ask:
Does camera.ui 2.x still support live MJPEG playback in the web interface, or is the web UI now intended for RTSP/H.264/H.265 only?
I can see in the browser console that camera.ui tries WebRTC and then MSE, both failing because the source is MJPEG, but I never see a fallback to an MJPEG player.
All reactions