On Thu, Oct 6, 2016 at 4:08 PM, Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 4:44 PM, James Almer wrote:
>> On 10/4/2016 11:35 AM, Hendrik Leppkes wrote:
>>> On Tue, Oct 4, 2016 at 4:32 PM, wm4 wrote:
On Tue, 4 Oct 2016 14:15:03 +0200
Michael Niedermayer wrote:
> On Tue, O
On Tue, Oct 4, 2016 at 4:44 PM, James Almer wrote:
> On 10/4/2016 11:35 AM, Hendrik Leppkes wrote:
>> On Tue, Oct 4, 2016 at 4:32 PM, wm4 wrote:
>>> On Tue, 4 Oct 2016 14:15:03 +0200
>>> Michael Niedermayer wrote:
>>>
On Tue, Oct 04, 2016 at 01:52:02PM +0200, Hendrik Leppkes wrote:
> On
On 10/4/2016 11:35 AM, Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 4:32 PM, wm4 wrote:
>> On Tue, 4 Oct 2016 14:15:03 +0200
>> Michael Niedermayer wrote:
>>
>>> On Tue, Oct 04, 2016 at 01:52:02PM +0200, Hendrik Leppkes wrote:
On Tue, Oct 4, 2016 at 1:44 PM, Hendrik Leppkes
wrote:
On Tue, 4 Oct 2016 16:35:02 +0200
Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 4:32 PM, wm4 wrote:
> > On Tue, 4 Oct 2016 14:15:03 +0200
> > Michael Niedermayer wrote:
> >
> >> On Tue, Oct 04, 2016 at 01:52:02PM +0200, Hendrik Leppkes wrote:
> >> > On Tue, Oct 4, 2016 at 1:44 PM, Hendrik
On Tue, Oct 4, 2016 at 4:32 PM, wm4 wrote:
> On Tue, 4 Oct 2016 14:15:03 +0200
> Michael Niedermayer wrote:
>
>> On Tue, Oct 04, 2016 at 01:52:02PM +0200, Hendrik Leppkes wrote:
>> > On Tue, Oct 4, 2016 at 1:44 PM, Hendrik Leppkes
>> > wrote:
>> > > On Tue, Oct 4, 2016 at 1:23 PM, Michael Niede
On Tue, 4 Oct 2016 14:15:03 +0200
Michael Niedermayer wrote:
> On Tue, Oct 04, 2016 at 01:52:02PM +0200, Hendrik Leppkes wrote:
> > On Tue, Oct 4, 2016 at 1:44 PM, Hendrik Leppkes
> > wrote:
> > > On Tue, Oct 4, 2016 at 1:23 PM, Michael Niedermayer
> > > wrote:
> > >> On Tue, Oct 04, 2016
On Tue, Oct 04, 2016 at 01:52:02PM +0200, Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 1:44 PM, Hendrik Leppkes wrote:
> > On Tue, Oct 4, 2016 at 1:23 PM, Michael Niedermayer
> > wrote:
> >> On Tue, Oct 04, 2016 at 08:41:42AM +0200, Hendrik Leppkes wrote:
> >>> On Tue, Oct 4, 2016 at 4:05 AM,
On Tue, Oct 4, 2016 at 1:55 PM, Michael Niedermayer
wrote:
> On Tue, Oct 04, 2016 at 10:30:24AM +0200, Hendrik Leppkes wrote:
>> On Tue, Oct 4, 2016 at 8:41 AM, Hendrik Leppkes wrote:
>> > On Tue, Oct 4, 2016 at 4:05 AM, Michael Niedermayer
>> > wrote:
>> >> On Sat, Oct 01, 2016 at 04:15:45PM +0
On Tue, Oct 04, 2016 at 10:30:24AM +0200, Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 8:41 AM, Hendrik Leppkes wrote:
> > On Tue, Oct 4, 2016 at 4:05 AM, Michael Niedermayer
> > wrote:
> >> On Sat, Oct 01, 2016 at 04:15:45PM +0200, Hendrik Leppkes wrote:
> >>> Decoders have previously not use
On Tue, Oct 4, 2016 at 1:44 PM, Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 1:23 PM, Michael Niedermayer
> wrote:
>> On Tue, Oct 04, 2016 at 08:41:42AM +0200, Hendrik Leppkes wrote:
>>> On Tue, Oct 4, 2016 at 4:05 AM, Michael Niedermayer
>>> wrote:
>>> > On Sat, Oct 01, 2016 at 04:15:45PM +0
On Tue, Oct 4, 2016 at 1:23 PM, Michael Niedermayer
wrote:
> On Tue, Oct 04, 2016 at 08:41:42AM +0200, Hendrik Leppkes wrote:
>> On Tue, Oct 4, 2016 at 4:05 AM, Michael Niedermayer
>> wrote:
>> > On Sat, Oct 01, 2016 at 04:15:45PM +0200, Hendrik Leppkes wrote:
>> >> Decoders have previously not u
On Tue, Oct 04, 2016 at 08:41:42AM +0200, Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 4:05 AM, Michael Niedermayer
> wrote:
> > On Sat, Oct 01, 2016 at 04:15:45PM +0200, Hendrik Leppkes wrote:
> >> Decoders have previously not used AVFrame.pts, and with the upcoming
> >> deprecation of pkt_pts
On Tue, Oct 4, 2016 at 8:41 AM, Hendrik Leppkes wrote:
> On Tue, Oct 4, 2016 at 4:05 AM, Michael Niedermayer
> wrote:
>> On Sat, Oct 01, 2016 at 04:15:45PM +0200, Hendrik Leppkes wrote:
>>> Decoders have previously not used AVFrame.pts, and with the upcoming
>>> deprecation of pkt_pts (in favor o
On Tue, Oct 4, 2016 at 4:05 AM, Michael Niedermayer
wrote:
> On Sat, Oct 01, 2016 at 04:15:45PM +0200, Hendrik Leppkes wrote:
>> Decoders have previously not used AVFrame.pts, and with the upcoming
>> deprecation of pkt_pts (in favor of pts), this would lead to an errorneous
>> interpration of tim
On Sat, Oct 01, 2016 at 04:15:45PM +0200, Hendrik Leppkes wrote:
> Decoders have previously not used AVFrame.pts, and with the upcoming
> deprecation of pkt_pts (in favor of pts), this would lead to an errorneous
> interpration of timestamps.
I probably misunderstand the commit message but
If code
On Sun, Oct 2, 2016 at 6:22 PM, Hendrik Leppkes wrote:
> On Sat, Oct 1, 2016 at 4:15 PM, Hendrik Leppkes wrote:
>> Decoders have previously not used AVFrame.pts, and with the upcoming
>> deprecation of pkt_pts (in favor of pts), this would lead to an errorneous
>> interpration of timestamps.
>> -
On Sat, 1 Oct 2016 16:15:45 +0200
Hendrik Leppkes wrote:
> Decoders have previously not used AVFrame.pts, and with the upcoming
> deprecation of pkt_pts (in favor of pts), this would lead to an errorneous
> interpration of timestamps.
> ---
> ffmpeg.c | 7 +--
> 1 file changed, 1 insertion(
On Sat, Oct 1, 2016 at 4:15 PM, Hendrik Leppkes wrote:
> Decoders have previously not used AVFrame.pts, and with the upcoming
> deprecation of pkt_pts (in favor of pts), this would lead to an errorneous
> interpration of timestamps.
> ---
> ffmpeg.c | 7 +--
> 1 file changed, 1 insertion(+),
Decoders have previously not used AVFrame.pts, and with the upcoming
deprecation of pkt_pts (in favor of pts), this would lead to an errorneous
interpration of timestamps.
---
ffmpeg.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/ffmpeg.c b/ffmpeg.c
index 9a8e65a..cdbf
19 matches
Mail list logo