On Tue, Mar 21, 2017 at 9:40 AM, Mark Reid wrote:
>
>
> On Mon, Mar 20, 2017 at 12:48 PM, Paul B Mahol wrote:
>
>> On 7/12/16, Mark Reid wrote:
>> > Hi,
>> > The following patch adds support for detecting more dnxhr header
>> prefixes.
>> >
>> > After generating many random resolution dnxhr fil
On Mon, Mar 20, 2017 at 12:48 PM, Paul B Mahol wrote:
> On 7/12/16, Mark Reid wrote:
> > Hi,
> > The following patch adds support for detecting more dnxhr header
> prefixes.
> >
> > After generating many random resolution dnxhr files via quicktime,
> > I have deduced that second 4 bytes in prefi
On 7/12/16, Mark Reid wrote:
> Hi,
> The following patch adds support for detecting more dnxhr header prefixes.
>
> After generating many random resolution dnxhr files via quicktime,
> I have deduced that second 4 bytes in prefix is the header size or
> data offset to the end of the scan table. On
On Sat, Jul 16, 2016 at 7:16 AM, Michael Niedermayer
wrote:
> On Mon, Jul 11, 2016 at 07:07:21PM -0700, Mark Reid wrote:
>> ---
>> libavcodec/dnxhddata.h | 15 +++
>> libavcodec/dnxhddec.c | 2 +-
>> 2 files changed, 12 insertions(+), 5 deletions(-)
>
> applied
>
> can you add a fat
On Mon, Jul 11, 2016 at 07:07:21PM -0700, Mark Reid wrote:
> ---
> libavcodec/dnxhddata.h | 15 +++
> libavcodec/dnxhddec.c | 2 +-
> 2 files changed, 12 insertions(+), 5 deletions(-)
applied
can you add a fate test for this ?
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF
---
libavcodec/dnxhddata.h | 15 +++
libavcodec/dnxhddec.c | 2 +-
2 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/libavcodec/dnxhddata.h b/libavcodec/dnxhddata.h
index 3ae4683..2394e04 100644
--- a/libavcodec/dnxhddata.h
+++ b/libavcodec/dnxhddata.h
@@ -34,8 +34,6 @@
Hi,
The following patch adds support for detecting more dnxhr header prefixes.
After generating many random resolution dnxhr files via quicktime,
I have deduced that second 4 bytes in prefix is the header size or
data offset to the end of the scan table. On heights smaller then 1080 the
header siz
