Re: [FFmpeg-devel] [PATCH] avcodec/aac_ac3_parser: account for data already in the parsing buffer

2018-04-15 Thread Hendrik Leppkes
On Fri, Apr 13, 2018 at 11:54 AM, Paul B Mahol wrote: > On 4/13/18, Hendrik Leppkes wrote: >> On Wed, Apr 11, 2018 at 1:40 PM, Hendrik Leppkes >> wrote: >>> If a frame starts very close to a packet boundary, the start code may >>>

Re: [FFmpeg-devel] [PATCH] avcodec/aac_ac3_parser: account for data already in the parsing buffer

2018-04-13 Thread Paul B Mahol
On 4/13/18, Hendrik Leppkes wrote: > On Wed, Apr 11, 2018 at 1:40 PM, Hendrik Leppkes > wrote: >> If a frame starts very close to a packet boundary, the start code may >> already have been added to the parsing buffer, indicated by a small >> negative

Re: [FFmpeg-devel] [PATCH] avcodec/aac_ac3_parser: account for data already in the parsing buffer

2018-04-13 Thread Hendrik Leppkes
On Wed, Apr 11, 2018 at 1:40 PM, Hendrik Leppkes wrote: > If a frame starts very close to a packet boundary, the start code may > already have been added to the parsing buffer, indicated by a small > negative value of "i", while the header is still being tracked in the >

Re: [FFmpeg-devel] [PATCH] avcodec/aac_ac3_parser: account for data already in the parsing buffer

2018-04-11 Thread Hendrik Leppkes
On Wed, Apr 11, 2018 at 8:07 PM, Carl Eugen Hoyos wrote: > 2018-04-11 13:40 GMT+02:00, Hendrik Leppkes : >> If a frame starts very close to a packet boundary, the start code may >> already have been added to the parsing buffer, indicated by a small >>

Re: [FFmpeg-devel] [PATCH] avcodec/aac_ac3_parser: account for data already in the parsing buffer

2018-04-11 Thread Carl Eugen Hoyos
2018-04-11 13:40 GMT+02:00, Hendrik Leppkes : > If a frame starts very close to a packet boundary, the start code may > already have been added to the parsing buffer, indicated by a small > negative value of "i", while the header is still being tracked in the > "state"

[FFmpeg-devel] [PATCH] avcodec/aac_ac3_parser: account for data already in the parsing buffer

2018-04-11 Thread Hendrik Leppkes
If a frame starts very close to a packet boundary, the start code may already have been added to the parsing buffer, indicated by a small negative value of "i", while the header is still being tracked in the "state" variable. Reduce the remaining size accordingly, otherwise trying to find the