Re: [libav-devel] [PATCH 2/2] vc1: always read the bfraction element for interlaced fields

2012-01-26 Thread Kostya Shishkov
On Mon, Jan 23, 2012 at 03:19:21PM +0100, Hendrik Leppkes wrote: > On 1/23/12, Mashiat Sarker Shakkhar wrote: > > > > > > Doesn't mach my copy of spec or the ref-code. BFRACTION is only present > > in B-pictures, not P. My copy of ref-code says: > > > > if(vc1_InterlacedField == pPosition->ePi

Re: [libav-devel] [PATCH 2/2] vc1: always read the bfraction element for interlaced fields

2012-01-23 Thread Hendrik Leppkes
On 1/23/12, Mashiat Sarker Shakkhar wrote: > > > Doesn't mach my copy of spec or the ref-code. BFRACTION is only present > in B-pictures, not P. My copy of ref-code says: > > if(vc1_InterlacedField == pPosition->ePictureFormat) > { > if(TRUE == pSeqParams->RefDistFlag) > {

Re: [libav-devel] [PATCH 2/2] vc1: always read the bfraction element for interlaced fields

2012-01-23 Thread Mashiat Sarker Shakkhar
- Original Message - > From: Hendrik Leppkes > To: libav development > Cc: > Sent: Sunday, January 22, 2012 1:22 AM > Subject: [libav-devel] [PATCH 2/2] vc1: always read the bfraction element for > interlaced fields > > Hi, > > attached patch fixe

[libav-devel] [PATCH 2/2] vc1: always read the bfraction element for interlaced fields

2012-01-21 Thread Hendrik Leppkes
Hi, attached patch fixes an inconsistency in the VC-1 interlaced fields header parsing. I validated the changes against the spec and the reference decoder, and this does seem more correct. I don't know if this actually affected any files, i couldn't find one, but with the state of the VC-1 interl