Timestamp H.264 frame ramp up?

[pisymbol .]

On Fri, Jul 5, 2019 at 7:36 PM pisymbol . <pisymbol at gmail.com> wrote:

>
>
> On Thu, Jul 4, 2019 at 11:44 PM Vinod Kesti <vinodkesti at yahoo.com> wrote:
>
>> pisymbol
>>
>> It may be source giving wrong delta.
>>
>> What is a source in your pipeline
>> Do similar analysis immediately after the source. That would give you some
>> Idea.
>>
>
> Vinod that is a great question. I am going to exactly that. Will report
> back.
>
>
[
    {
        "delta": 0,
        "frame": 0,
        "timestamp": 710794680
    },
    {
        "delta": 31127306,
        "frame": 1,
        "timestamp": 741921986
    },
    {
        "delta": 8828365,
        "frame": 2,
        "timestamp": 750750351
    },
    {
        "delta": 21636578,
        "frame": 3,
        "timestamp": 772386929
    },
    {
        "delta": 32609730,
        "frame": 4,
        "timestamp": 804996659
    },
    {
        "delta": 33260030,
        "frame": 5,
        "timestamp": 838256689
    },
    {
        "delta": 32897792,
        "frame": 6,
        "timestamp": 871154481
    },
...

So it's slightly better. But notice frame 2 and 3 have some kinda weird
buf.pts timestamps before it starts to level out to about 30fps. The source
is nvcamerasrc (i.e. nvcamerasrc (bunch of options) ! identity ..).

Is this just some kind of pipeline jitter?

-aps
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20190706/242285e8/attachment-0001.html>