From: Anssi Hannula
As per issue2629, most 23.976fps matroska H.264 files are incorrectly
detected as 24fps, as the matroska timestamps usually have only
millisecond precision.
Fix that by doubling the amount of timestamps inspected for frame rate
for streams that have coarse time base. This als
From: Anssi Hannula
As per issue2629, most 23.976fps matroska H.264 files are incorrectly
detected as 24fps, as the matroska timestamps usually have only
millisecond precision.
Fix that by doubling the amount of timestamps inspected for frame rate
for streams that have coarse time base. This als
Anton Khirnov writes:
> From: Anssi Hannula
>
> As per issue2629, most 23.976fps matroska H.264 files are incorrectly
> detected as 24fps, as the matroska timestamps usually have only
> millisecond precision.
>
> Fix that by doubling the amount of timestamps inspected for frame rate
> for stream
2011/3/28 Måns Rullgård :
> Anton Khirnov writes:
>
>> From: Anssi Hannula
>>
>> As per issue2629, most 23.976fps matroska H.264 files are incorrectly
>> detected as 24fps, as the matroska timestamps usually have only
>> millisecond precision.
>>
>> Fix that by doubling the amount of timestamps i
Alexander Strange writes:
> 2011/3/28 Måns Rullgård :
>> Anton Khirnov writes:
>>
>>> From: Anssi Hannula
>>>
>>> As per issue2629, most 23.976fps matroska H.264 files are incorrectly
>>> detected as 24fps, as the matroska timestamps usually have only
>>> millisecond precision.
>>>
>>> Fix that
On 02.04.2011 03:24, Måns Rullgård wrote:
> Alexander Strange writes:
>
>> 2011/3/28 Måns Rullgård :
>>> Anton Khirnov writes:
>>>
From: Anssi Hannula
As per issue2629, most 23.976fps matroska H.264 files are incorrectly
detected as 24fps, as the matroska timestamps usually
On 4/28/11 10:20 AM, Reinhard Tartler wrote:
From: Anssi Hannula
As per issue2629, most 23.976fps matroska H.264 files are incorrectly
detected as 24fps, as the matroska timestamps usually have only
millisecond precision.
Fix that by doubling the amount of timestamps inspected for frame rate
fo
On 4/28/11 10:20 AM, Reinhard Tartler wrote:
From: Anssi Hannula
As per issue2629, most 23.976fps matroska H.264 files are incorrectly
detected as 24fps, as the matroska timestamps usually have only
millisecond precision.
Fix that by doubling the amount of timestamps inspected for frame rate
fo
Luca Barbato writes:
> On 4/28/11 10:20 AM, Reinhard Tartler wrote:
>> From: Anssi Hannula
>>
>> As per issue2629, most 23.976fps matroska H.264 files are incorrectly
>> detected as 24fps, as the matroska timestamps usually have only
>> millisecond precision.
>>
>> Fix that by doubling the amount
On 04/28/2011 02:00 PM, Måns Rullgård wrote:
> And meanwhile startup overhead will be twice the already insane amount.
I'm afraid fixing the issue could require few weekends with at least 3-4
people banging their heads on the code to understand what the code tries
to do, write a clean replacement
On Fri, Apr 29, 2011 at 03:02:07AM +0200, Luca Barbato wrote:
> On 04/28/2011 02:00 PM, Måns Rullgård wrote:
> > And meanwhile startup overhead will be twice the already insane amount.
>
> I'm afraid fixing the issue could require few weekends with at least 3-4
> people banging their heads on the
11 matches
Mail list logo