rtpgstpay: Header packets have bogus RTP timestamps
rtpgstpay
is outputting its first packets before any input packet is received and as such before the input timestamps are known. This causes basepayload to output them with the RTP timestamp that corresponds to running time 0.
If the stream does not start at running time 0 this would cause a completely bogus RTP timestamp to be sent.
The only solution I can think of would be to delay the headers until the first input buffer arrived, but that would potentially delay them for a considerable amount of time and could break existing applications that assume that the headers arrive immediately in the beginning.