omxmjpegdec problem

oguime oguime at gmail.com
Sat Jul 18 20:46:36 PDT 2015


Hi,

I wanted to add a clockoverlay to the AVI created by GStreamer when reading
a MJPEG from a D-Link IP Camera, but decoding and encoding increased CPU
usage to 89% when recording on a Raspberry PI.

I tried to use omx instead to take advantage of hardware acceleration but
there seems to be a problem with omxmjpegdec. When I try to use it,
GStreamer won't stop when receiving an EOS.

This works using jpegdec (67% CPU):

gst-launch-1.0 souphttpsrc location=http://user:pass@IP/mjpeg.cgi
num-buffers=3000 ! image/jpeg,framerate=12/1 ! *jpegdec* ! clockoverlay
time-format="%Y/%m/%d %H:%M:%S" ! omxh264enc target-bitrate=2000000
control-rate=3 ! video/x-h264 ! h264parse ! mp4mux ! filesink
location=output.mp4

This worked once or twice using omxmjpegdec (34% CPU):

gst-launch-1.0 souphttpsrc location=http://user:pass@IP/mjpeg.cgi
num-buffers=3000 ! image/jpeg,framerate=12/1 ! jpegparse ! *omxmjpegdec* !
clockoverlay time-format="%Y/%m/%d %H:%M:%S" ! omxh264enc
target-bitrate=2000000 control-rate=3 ! video/x-h264 ! h264parse ! mp4mux !
filesink location=output.mp4

There is a bug report here:
https://bugzilla.gnome.org/show_bug.cgi?id=742172

Is there any alternative besides using mjpegdec ?

THanks



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/omxmjpegdec-problem-tp4672718.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list