How are these two omxh264enc caps different?

Nicolas Dufresne nicolas.dufresne at collabora.com
Fri Nov 27 07:11:17 PST 2015


Le vendredi 27 novembre 2015 à 06:44 -0800, gmilan a écrit :
> ! "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).

target-bitrate and control-rate are encoder properties specific to
omxh264enc, not caps field. The second case is not correct.

Nicolas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20151127/ff2ce71a/attachment-0001.sig>


More information about the gstreamer-devel mailing list