How to debug/fix running error when use rtph264pay?

Nicolas Dufresne nicolas at ndufresne.ca
Fri Jul 31 17:37:51 UTC 2020


Le vendredi 31 juillet 2020 à 16:39 +0800, Psychesnet Hsieh a écrit :
> Hi Gotsring,
> 
> I still have a question on rtph264pay after checking the sink's capability.
> For rtph264pay,
> Pad Templates:
>   SINK template: 'sink'
>     Availability: Always
>     Capabilities:
>       video/x-h264
>           stream-format: avc
>               alignment: au
>       video/x-h264
>           stream-format: byte-stream
>               alignment: { (string)nal, (string)au }
> 
> The input of rtph264pay could be avc:au or byte-stream:nal/au.
> Since my H264 frame is coming from ISP, each h264 frame has complete NAL header.
> And at each callback, I will put a complete H264 frame to pipeline.
> So, I try to set appsrc's capability with byte-stream:au without h264parse, I can see h264 frame can be display on server side.
> But, the appsrc program keep showing
> (process:1113): GStreamer-CRITICAL **: 08:21:56.048: gst_segment_to_running_time: assertion 'segment->format == format' failed

You like forgot to set the property "format" on appsrc
to GST_FORMAT_TIME. The RTP elements only works well with time format.
Make sure to setup some decent timestamp if you want smoother network
streaming.

> 
> Questions are
> 1. set appsrc's capability with byte-stream:au without h264parse, is it make sense?
> 2. if 1 is yes, how can I fix critical issue?
> 
> Thanks.
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel



More information about the gstreamer-devel mailing list