@alfredfriedrich Thanks for posting your solution!
fhunleth
Co-author of Nerves
alfredfriedrich
I am glad, I can give something back.
My current command call is
rpicam-vid -t 0 --framerate -1.0 --width 1536 --height 864 --codec libav --profile Main --libav-video-codec libx264 --libav-format h264 --low-latency true --nopreview -o -
And I am trying use the membrane framework to stream that to a browser with HLS using hls.js in a LiveView, but I do get a delay of around 15s,
My final goal is to recreate the nx_hailo setup with membrane insterad of evision to have a custom plugin/filter that can be configured via an LiveView page somehow. Still work in progress 
2
Damirados
rpi5 doesn’t have hardware video encoders, software encoding (CPU) can be slow, nowhere near 15s though. If you setup webrtc stream with membrane or boombox to your liveview you should get much better latency.
0
alfredfriedrich
If I stream with –codec libav --libav-format mpegts from the command line and watch it with ffplay the delay is under 1s. Same setup with –codec libav --libav-format h264 gets a delay around 2-3s.
I guess the delay is not due to my membrane setup but per se, but the combination of target_windw_size and buffer in the hls.js player.
I tried WebRTC with membrane but was not able to get an connection between Player and Sink iirc without an ICE Server (passed an empty list in the JS and Pipeline). But I need an offline capable solution.
0
lawik
Nerves Core Team
HLS (HTTP Live Streaming for those following along at home) has a lot of inherent latency. I see reports of between 6 and 30s.
Like Damir said. WebRTC, WHIP and so on are much lower latency.
0