Roger Hardiman

The ffmpeg issue you see is just a trick (a hack) to get a JPEG image for the ONVIF GetSnapshotURI command. I needed an image from the camera to make...

What you need to do us get the h264 stream into a RTSP server. Rpos has 3 different RTSP servers you can use. Two use Live555. One uses gstreamer. Some...

In the case of gstreamer you can make gstreamer read from StdIn. There is a Gstreamer module for it but I cannot remember what it is called. (@Schwaneberg wrote the...

Were you just trying raspivid as a quick test, before moving over to the Python Camera Library?

Hi. In the gstreamer example from @Schwaneberg I noticed the trick of passing the H264 bitstream back through a H264 decoder (via OMX) to get raw video. I'd used a...

ffmpeg -fflags nobuffer -probesize 256 -rtsp_transport tcp -i rtsp://127.0.0.1:${this.config.RTSPPort}/${this.config.RTSPName} -vframes 1 -r 1 -s 640x360 -y /dev/shm/snapshot.jpg

in the services/media files in RPOS is code to launch ffmpeg, make ffmpeg connect to the local RTSP server and to extract 1 jpeg

There is no support for audio in RPOS in the ONVIF messages. So at the ONVIF level RPOS just reports the video capability. At the RTSP stream level you can...

It needs a volunteer to write the software. The we can review it, test it and add it to RPOS.

You are doing the right sort of things - RTSP type (in the config) is 3 for Gstreamer. You are right about the size. RPOS calls a python script which...