On 11/22/18 7:33 PM, Jeyapal, Karthick wrote:
>
> On 11/22/18 6:35 PM, Carl Eugen Hoyos wrote:
>> 2018-11-22 7:43 GMT+01:00, Jeyapal, Karthick :
>>>
>>> On 11/20/18 11:03 PM, Andrey Semashev wrote:
When stream time bases are very fine grained (e.g. nanoseconds), 32-bit
segment duration
On 11/22/18 6:35 PM, Carl Eugen Hoyos wrote:
> 2018-11-22 7:43 GMT+01:00, Jeyapal, Karthick :
>>
>> On 11/20/18 11:03 PM, Andrey Semashev wrote:
>>> When stream time bases are very fine grained (e.g. nanoseconds), 32-bit
>>> segment duration may overflow for even for rather small segment duration
2018-11-22 7:43 GMT+01:00, Jeyapal, Karthick :
>
> On 11/20/18 11:03 PM, Andrey Semashev wrote:
>> When stream time bases are very fine grained (e.g. nanoseconds), 32-bit
>> segment duration may overflow for even for rather small segment duration
>> (about 4 seconds long). Therefore we use 64-bit
On 11/20/18 11:03 PM, Andrey Semashev wrote:
> When stream time bases are very fine grained (e.g. nanoseconds), 32-bit
> segment duration may overflow for even for rather small segment duration
> (about 4 seconds long). Therefore we use 64-bit values for segment duration.
> ---
>
When stream time bases are very fine grained (e.g. nanoseconds), 32-bit
segment duration may overflow for even for rather small segment duration
(about 4 seconds long). Therefore we use 64-bit values for segment duration.
---
libavformat/dashenc.c | 6 +++---
1 file changed, 3 insertions(+), 3
