Re: [FFmpeg-devel] [PATCH 1/3] decklink: Don't take for granted that first frame to decklink output will be PTS 0

2023-03-01 Thread Devin Heitmueller
On Tue, Feb 28, 2023 at 3:46 PM Marton Balint wrote: > And what if first packet pts is 0? Then the second packet pts will be > assigned to first pts? Maybe you should use AV_NOPTS_VALUE for the default > first_pts value and check for that instead. That's a good point. I never noticed that, but

Re: [FFmpeg-devel] [PATCH 1/3] decklink: Don't take for granted that first frame to decklink output will be PTS 0

2023-02-28 Thread Marton Balint
On Thu, 23 Feb 2023, Devin Heitmueller wrote: The existing code assumed that the first frame received by the decklink output would always be PTS zero. However if running in other timing modes than the default of CBR, items such as frame dropping at the beginning may result in starting at a

[FFmpeg-devel] [PATCH 1/3] decklink: Don't take for granted that first frame to decklink output will be PTS 0

2023-02-23 Thread Devin Heitmueller
The existing code assumed that the first frame received by the decklink output would always be PTS zero. However if running in other timing modes than the default of CBR, items such as frame dropping at the beginning may result in starting at a non-zero PTS. For example, in our setup because we