just ordered the VIM4 with the target to turn it into a mobile (bandwidth efficient) streaming solution with datalogger capabilities for a motorbike 24h race stream.
Vim4 does offer everything needed. HDMI IN (GoPro Input), H.265 encode, LTE module.
Can anybody point me towards ressources on how to use the h.265 encoder with ffmpeg or gstreamer?
The ressources in the docs do ‘only’ encode a singular file, and not a stream. (Target is to HLS stream H.265 to youtube)
At this moment, you can only use the library to perform hardware encoding. For encoding with ffmpeg and gstreamer are not supported yet. But we have a plan to support gstramer first.
I would also like to voice a need for this functionality. Using the HDMI input with ffmpeg is the reason I purchased the boards. I can’t seem to use the input with /anything/. Seeing the video input working in Android is encouraging, but I’m disappointed that there seems to be no way to use the video input for anything useful at the time of release. Will be following this thread very closely and posting any updates I might find.
I was unfamiliar with gstreamer, but it looks as though that will suit my needs as well.
Basically if the board is on I want it to be broadcasting a stream of whatever is coming into the input at any given time with no need for human interaction if the input is removed or swapped. So ideally it would continue to stream even if there is no input and maybe have an OSD that reflects as much. But I digress.
TLDR: HDMI to Stream with as little latency as possible. Trying to go webrtc unless I have no other option.
I will add my hopes here. Similar to what others have said, I want to stream the HDMI In via gstreamer via RTSP. I do this right on other SBC using usb capture devices, but this seems like one less thing to worry about. So having v4l2 input, and preferably also hardware encoding in gstreamer would be ideal.
In my opinion a product which is advertised to have a certain feature (HDMI, H.264/H.265 HW encode) should support this through a standard interface on the supported OS(s).
So for hdmi in v4l2 backend so that it appears as a video input device and for the encoders a lib for ffmpeg/gstreamer.
Hi @numbqq ,
As others have mentioned building a driver to support v4l2 would be good enough. From there multiple applications would be able to pull frames and audio from it (not limited to gst or ffmpeg only).
Wonder if you have any timeline for gstreamer implementation? Do you need beta testers? Do reach out if you do.
Cool thanks so much for working hard on this (= Probably have to build GStreamer from scratch through meson and ninja rather than use the packages from ubuntu if you need additional Wayland support. Minimally the core libraries though you’d probably want a clean install of gst cos the plugins might interfere if you just rebuild the core.
Hi Nick thanks for this. This is for hw decoding, wonder if you happen to know which V4L2 device HDMI IN is? I see a bunch of them when trying to tap the various devices. The board enumerates devices up to video70