How are these two omxh264enc caps different?

[gmilan]

*setup 1 *
gst-launch-1.0 -v v4l2src device=/dev/video0 \
! video/x-raw, width=320,height=240,framerate=5/1 \
! queue \
*! omxh264enc target-bitrate=40000 control-rate=variable \
! "video/x-h264, profile=high" \*
! h264parse \
! queue \
! tcpserversink host=192.168.10.1 port=5000 sync-method=2
recover-policy=keyframe

*setup 2*
 gst-launch-1.0 -v v4l2src device=/dev/video0 \
! video/x-raw, width=320,height=240,framerate=5/1 \
! queue \
*! omxh264enc \
! "video/x-h264, profile=high, target-bitrate=40000, control-rate=variable"
\*
! h264parse \
! queue \
! tcpserversink host=192.168.10.1 port=5000 sync-method=2
recover-policy=keyframe

As you may see, two different caps implementation in omxh264enc above. I
found the results obtained by above two are quite different.

First setup has artifacts, but it is more real time comparing source and
sink.
Second setup is more clear, but it has more latency.

Am I making mistake providing caps for omxh264enc, I need to change the
bitrate of omxh264enc.(The bitrate i targetted by assigning target-bitrate
=40000 is not reflected in tcp bandwidth, it get very much variable as
well).

Please somebody help.



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/How-are-these-two-omxh264enc-caps-different-tp4674676.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.