How to efficiently replace vaapih265enc with omxh265enc?

[Junyan He]

Yeah, I am saying that.
If I understand right, your problem is that if you replace the
vaapih265enc in the encoder side with `omxh265enc`, you must add a
parser beforce the vaapih265dec at decoder size, or, the decoder will
report error.

I suspect that the frame alignment cause this problem. vaapih265enc
output just one frame in one gstbuffer, and so, one gstbuffer is
already frame aligned(appsrc/appsink seems direct forward data in unit
of gstbuffer?). I am not famaliar with omxh265enc's hehavior, it may
mix data from several frames together, with AU as delimiter. So one
gstbuffer may not be frame aligned. At decoder side, if you need to
detect the frame edge, a parser is always needed before vaapih265dec.



On 一, 2019-11-18 at 06:20 -0600, jeyp4 wrote:
> Thanks for replying.
> 
> <http://gstreamer-devel.966125.n4.nabble.com/file/t379085/vaapih265en
> c.jpg> 
> 
> Actually, above pipeline works fine, even without 'h265parse'. I am
> sending
> buffer data in ROS msg. What I am doing at receiver side is,
> modifying pts,
> dts with current receiver pipeline running time. And also I have to
> start
> receiver before transmitter. In this way I observe almost no delay in
> decoding ~ 2ms. I am happy with this pipeline.
> 
> Just for info: If I add h265parse in above receiver pipeline, it
> works then
> also. But now decoding time is ~40ms. Decoding time: Difference
> between when
> receiver received buffer and when vaapidecode dropped its output. I
> confirmed this latency presence by measuring glass to glass latency
> also.
> 
> As I said, I am happy with above pipeline without h265parse because
> it is
> working fine.
> 
> I am trying to replace vaapih265enc with omxh265enc !
> 
> 
> 
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel