Suggestion required for h265 codec appsink-appsrc pipeline

jeyp4 jaiforfriend at gmail.com
Thu Aug 27 16:40:50 UTC 2020


Hi

In my C++ applications, I am trying to obtain below pipelines.
 v4l2src ( I420, fps=25) ! omxh265enc ( iframeinterval=25) ! appsink
(video/x-h265, stream-format=byte-stream, alignment=au)

appsrc (video/x-h265, stream-format=byte-stream, alignment=au, fps=25,
do-timestamp=TRUE, is-live=TRUE) ! nvh265dec ! autovideosink

Finally, autovideosink shows the stream, but I see ghosting effect in
presence of movements.


I suspect it is because of non-uniformly placed in time h265
packets.(referring below figure). The network carrier is ROS+VPN+4G.
<http://gstreamer-devel.966125.n4.nabble.com/file/t379085/nabbleAsk.jpg> 

I find big latency in RTPH server pipelines, that's why I choose ROS method.
Also, I am thinking to avoid using any queue in receiver pipeline so that I
can achieve minimum latency target.

Can someone provide any suggestion to improve my results? Note: With every
packet from transmitter, I also carry extra info. E.g. fps, dts, pts,
duration, height and width. (Just in case if it can be used to improve
results)



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/


More information about the gstreamer-devel mailing list