Trying to get a reasonable frame number and timestamp

[Thibault Saunier]

After h264 the stream is "parsed"  so 1 buffer == 1 frame, so yes that
would work in simple cases.

On Fri, Jun 14, 2019 at 7:55 PM pisymbol . <pisymbol at gmail.com> wrote:

>
>
> On Fri, Jun 14, 2019 at 7:46 PM pisymbol . <pisymbol at gmail.com> wrote:
>
>>
>>
>> On Fri, Jun 14, 2019 at 7:40 PM Thibault Saunier <tsaunier at gnome.org>
>> wrote:
>>
>>> It is not what I am saying, I am just saying that you do not have the
>>> frame number set on encoded buffers.
>>>
>>>
>>>
>> But if I try to dump offset before encoding, I get max(uint64) which
>> doesn't make sense to me given what you just said, i.e. add a "tap" right
>> after capturing from nvcamerasrc. And the other thread I referenced seemed
>> to decode out the raw frames to get them, no? I can do that (I fixed my tee
>> command) but the frame numbers still look funny to me (I expect 1,2,3,4
>> etc.).
>>
>>
> Actually, even simpler. The PTS timestamps look good. Can I just number
> each timestamp frame 1, 2, 3, etc.? They should correlate to the encoded
> stream, no?
>
> -aps
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20190614/0568792f/attachment.html>