On Tue, Mar 21, 2017 at 9:40 AM, Mark Reid <mindm...@gmail.com> wrote:
> > > On Mon, Mar 20, 2017 at 12:48 PM, Paul B Mahol <one...@gmail.com> wrote: > >> On 7/12/16, Mark Reid <mindm...@gmail.com> 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 heights smaller then 1080 >> the >> > header size is always 0x0280 >> > >> > here are some samples with prefixes that aren't currently supported. >> > https://dl.dropboxusercontent.com/u/170952/ffmpeg_samples/ne >> w_header_prefixs/lb_2k_2048x1536.mxf >> > https://dl.dropboxusercontent.com/u/170952/ffmpeg_samples/ne >> w_header_prefixs/lb_4k_Full_Aperture_4096x3112.mxf >> > https://dl.dropboxusercontent.com/u/170952/ffmpeg_samples/ne >> w_header_prefixs/lb_custom_2766x3234.mov >> > https://dl.dropboxusercontent.com/u/170952/ffmpeg_samples/ne >> w_header_prefixs/lb_custom_3462x2134.mov >> > >> > Mark Reid (1): >> > libavcodec/dnxhd: add support more dnxhr header prefixes >> > >> > libavcodec/dnxhddata.h | 15 +++++++++++---- >> > libavcodec/dnxhddec.c | 2 +- >> > 2 files changed, 12 insertions(+), 5 deletions(-) >> >> This one causes http://trac.ffmpeg.org/ticket/6214 > > > > I've identified the issue, working on a fix. > > nevermind, see your already working on a similar fix. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
