On Mon, Sep 10, 2018 at 8:00 PM, Marton Balint wrote:
> Yes, just put the same value to both line 12 (or whichever line the user
> selects) and its pair line in the other field.
Ok, will take care of this today.
Thanks for reviewing.
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kern
On Sun, 9 Sep 2018, Devin Heitmueller wrote:
On Sun, Sep 9, 2018 at 4:59 PM, Marton Balint wrote:
Thanks, I applied patches 1-4.
decklink: Add support for output of Active Format Description (AFD)
Regarding this one, I noticed you always set the AFD in line 12. Are you
sure that it is
Hi James,
> Shouldn't this new packet side data be handled in libavcodec/decode.c
> ff_decode_frame_props() as well?
I have a patch which does this as part of a patch series which adds
AFD parsing to decklink capture, ensures it gets preserved in
ff_decode_frame_props, and encodes the resulting A
On Sun, Sep 9, 2018 at 4:59 PM, Marton Balint wrote:
> Thanks, I applied patches 1-4.
>
>> decklink: Add support for output of Active Format Description (AFD)
>
>
> Regarding this one, I noticed you always set the AFD in line 12. Are you
> sure that it is OK to use line 12 for all resolutions?
On 9/9/2018 5:59 PM, Marton Balint wrote:
>
>
> On Fri, 7 Sep 2018, Devin Heitmueller wrote:
>
>> The following patches add support for output of 708 and AFD over
>> the Decklink SDI interface. This series is a subset of a series
>> submitted in early January, with the hope of getting the less
On Fri, 7 Sep 2018, Devin Heitmueller wrote:
The following patches add support for output of 708 and AFD over
the Decklink SDI interface. This series is a subset of a series
submitted in early January, with the hope of getting the less
controversial parts merged upstream.
Note compared to th