You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Meekohi, as it is right now, web-browsers only need to support H264, VP8 and VP9. While some browsers have been trying to adopt H265 for WebRTC (Safari, for example), no browser showed interest in allowing raw formats like MJPG and YUYV.
For your use, you'll have to either encode your video to H264, or change your device to some device that offers a H264-encoded video stream out of the box.
To encode your video, you'll have to write a script to get the video from your camera, process it, and let it available via an RTSP server. Then, in mavlink camera manager, you can add it as a redirect stream.
I believe the easiest way to accomplish that is to start from this. If you build this project and run the test-launch application (the source is at examples/test-launch.c), you can pass your gstreamer pipeline to do just what you need.
Oh, also, be aware that stream encoding requires some CPU or GPU process power. Feel free to try different encoders than the x264enc that I used in the example there.
The only options I see for my video source Encode are MJPG and YUVV. In contrast for the fake source I see h264, h265, MJPG, and YUVV.
Is there a way to either make h264 available for my video stream, or advice on how to figure out what is wrong with the mjpg/yuvv options?
The text was updated successfully, but these errors were encountered: