> On Dec 17, 2018, at 9:58 AM, Steven Liu wrote:
>
>
>
>>> On Dec 17, 2018, at 21:07, Ronak Patel
>>> wrote:
>>>
>>>
>>> On Dec 13, 2018, at 9:15 PM, Ronak Patel
>>> wrote:
>>>
>>>
>>>
>&
> On Dec 16, 2018, at 10:31 PM, Steven Liu wrote:
>
> Aleksey Skripka 于2018年12月14日周五 下午10:58写道:
>>
>>
>> From e85edcc4d8b0312c7871f78ed0859ec7436be460 Mon Sep 17 00:00:00 2001
>> From: Aleksey Skripka
>> Date: Fri, 14 Dec 2018 14:48:31 +
>> Subject: [PATCH] libavformat/hlsenc: fix broken
> On Dec 13, 2018, at 9:15 PM, Ronak Patel
> wrote:
>
>
>
>> On Dec 12, 2018, at 2:46 AM, Liu Steven wrote:
>>
>>
>>
>>>> 在 2018年12月12日,上午5:08,Ronak 写道:
>>>>
>>>>
>>>> On Dec 11, 2018, at 3:28 PM,
> On Dec 12, 2018, at 2:46 AM, Liu Steven wrote:
>
>
>
>>> 在 2018年12月12日,上午5:08,Ronak 写道:
>>>
>>>
>>> On Dec 11, 2018, at 3:28 PM, Gyan wrote:
>>>
>>>
On 12-12-2018 01:13 AM, Ronak wrote:
Looks like I found out why:
https://github.com/FFmpeg/FFmpeg/blob/master/liba
> On Oct 27, 2018, at 5:25 PM, Carl Eugen Hoyos wrote:
>
> 2018-10-27 20:50 GMT+02:00, Mark Thompson :
>> This reverts commit 6dbb64fdccafe846aaec75d3784f7ad49d8af5df.
>>
>> The additional braces cause build errors with Linux headers earlier
>> than 4.5 because the first element of the structur
> On Aug 17, 2018, at 10:40 AM, Steven Liu wrote:
>
>
>
>> On Aug 17, 2018, at 21:01, Ronak wrote:
>>
>> From 99e28c807a49cecf6ceb47ee44a85a3fdf78af64 Mon Sep 17 00:00:00 2001
>> From: "Ronak Patel"
>> Date: Thu, 2 Aug 2018 09:25:12 -040
> On Aug 15, 2018, at 8:21 PM, Steven Liu wrote:
>
>
>
>>> On Aug 16, 2018, at 07:41, Ronak Patel wrote:
>>>
>>>
>>> On Aug 15, 2018, at 11:08 AM, Steven Liu wrote:
>>>
>>>
>>>
>>>> On Aug 15,
> On Aug 15, 2018, at 8:39 PM, Ronak Patel wrote:
>
>
>> On Aug 15, 2018, at 8:21 PM, Steven Liu wrote:
>>
>>
>>
>>>> On Aug 16, 2018, at 07:41, Ronak Patel wrote:
>>>>
>>>>
>>>> On Aug 15, 2018, at 11:0
> On Aug 15, 2018, at 11:08 AM, Steven Liu wrote:
>
>
>
>> On Aug 15, 2018, at 09:31, Ronak wrote:
>>
>> From: "Ronak Patel" mailto:ron...@audible.com>yahoo.com>
>>
>> This fixes the creation of the hls manifest in hlsenc.c by wr
> On Aug 15, 2018, at 6:46 AM, Liu Steven wrote:
>
>
>
>>> 在 2018年8月15日,下午6:37,Ronak Patel 写道:
>>>
>>>
>>> On Aug 14, 2018, at 10:57 PM, Liu Steven wrote:
>>>
>>>
>>>
>>>> 在 2018年8月15
> On Aug 14, 2018, at 10:57 PM, Liu Steven wrote:
>
>
>
>> 在 2018年8月15日,上午9:31,Ronak 写道:
>>
>> From: "Ronak Patel" mailto:ronak2...@yahoo.com>yahoo.com>
>>
>> This fixes the creation of the hls manifest in hlsenc.c by writing
On Aug 10, 2018, at 7:30 AM, Liu Steven wrote:
>>>
>>> Hi Steven,
>>>
>>> Please see my new patch taking your feedback into account.
>>>
>>> Ronak
>>
>> Hi Steven,
>>
>> Did you have a chance to review? I’m going to send you a new patch for
>> dashenc.c shortly.
> Don’t worry, i will
> On Aug 8, 2018, at 5:37 PM, Ronak wrote:
>
>
>
>> On Aug 8, 2018, at 3:52 PM, Ronak wrote:
>>
>>
>>
>>> On Aug 6, 2018, at 10:20 AM, Steven Liu wrote:
>>>
>>>
>>>
>>>>> On Aug 6, 2018, at 19:29
> On Aug 6, 2018, at 7:19 AM, Liu Steven wrote:
>
>
>
>>> 在 2018年8月6日,下午7:12,Ronak Patel 写道:
>>>
>>>
>>> On Aug 5, 2018, at 10:54 PM, Liu Steven wrote:
>>>
>>>
>>>
>>>> 在 2018年8月4
nk about all of the player or parser, because ffmpeg is not
>>>>>> used only by myself.
>>>>>>
>>>>>> Or what about get the #EXT-X-VERSION position, to update it? looks like
>>>>>> flvenc.c or movenc.c date shift
>>&g
> I'm attaching a new patch that resolves all of these issues, while still
> resolving this bug for VOD playlists.
>
> Can you please review?
>
> <0001-libavformat-hlsenc-Fix-HLS-Manifest-Generation-from-.patch>
Hi Steven,
Can you please have a look at the updated patch and tell me what you t
> On Aug 1, 2018, at 9:30 PM, Ronak Patel
> wrote:
>
>
>> On Aug 1, 2018, at 7:30 PM, Steven Liu wrote:
>>
>>
>>
>>> On Aug 2, 2018, at 07:22, Steven Liu wrote:
>>>
>>>
>>>
>>>>> On Aug 2, 2018, at
M, Steven Liu wrote:
>>>>
>>>>
>>>>
>>>>> On Aug 2, 2018, at 03:50, Ronak wrote:
>>>>>
>>>>> <0001-libavformat-hlsenc-Fix-HLS-Manifest-Generation-from-.patch>
>>>> From e7ff03ed52c709d647a112833427b44
> On Jul 25, 2018, at 11:25 PM, Ronak Patel
> wrote:
>
>
>
>> On Jul 25, 2018, at 11:12 PM, Liu Steven wrote:
>>
>>
>>
>>> 在 2018年7月26日,上午7:04,Ronak Patel 写道:
>>>
>>> Hi,
>>>
>>> We’d like to
> On Jul 25, 2018, at 11:12 PM, Liu Steven wrote:
>
>
>
>> 在 2018年7月26日,上午7:04,Ronak Patel 写道:
>>
>> Hi,
>>
>> We’d like to start working on this real soon and want to make sure we
>> properly fix this. We understand this code is used
our fixes?
We’re afraid that the number of use cases here are unknown and we’ll be stuck
fixing this for an unknown time.
Can anyone please shed some light on this?
Thanks
Ronak
> On Jul 13, 2018, at 8:05 AM, Ronak Patel
> wrote:
>
> I was wondering if anyone on the developm
I was wondering if anyone on the development list was familiar with this code
and could provide pointers on how to fix up the code due to the below problem.
> On Jul 12, 2018, at 7:27 PM, Ronak Patel
> wrote:
>
>
>
>> On Jul 12, 2018, at 6:21 PM, Ronak Patel
>
Hi,
I was wondering if anyone more in the know about this can help fix this issue.
https://trac.ffmpeg.org/ticket/7282#comment:11
It’s preventing us from supporting adaptive Streaming between LCAAC and HEAAC.
Thanks
Ronak
Sent from my iPhone
___
ffm
We did consider rubberband, but the audio quality is too poor. The audio has
echo artifacts in it that makes it sound robotic.
Sent from my iPhone
> On Jun 4, 2018, at 8:32 PM, Lou Logan wrote:
>
>> On Mon, Jun 4, 2018, at 10:09 AM, Ronak wrote:
>>
>> We are looking to use the atempo filter f
Thanks. Is it okay if I push a patch for this? How high of a limit does the
algorithm support today?
Sent from my iPhone
> On Jun 4, 2018, at 8:00 PM, Pavel Koshevoy wrote:
>
>> On 06/04/2018 12:09 PM, Ronak wrote:
>> Hello,
>>
>> How are you all?
>>
>> We are looking to use the atempo filte
No I’ll give it a try and let you know.
Since this is just audio (no keyframes) I wouldn’t have thought this would have
mattered.
Sent from my iPhone
> On May 7, 2018, at 3:52 PM, Aman Gupta wrote:
>
> On Wed, May 2, 2018 at 7:59 AM, Ronak Patel <
> ronak2121-at-yahoo@ff
Hi all,
So I’ve noticed that ffmpeg does not always properly follow the number we
specify for hls_time when generating hls content.
For example, if we have an MP4/AAC file at 44.1kHz sampling rate, we would
expect that specifying 9.75238095238095 (420 frames) would return a manifest
with the s
Awesome guys thanks for the fix! That was fast!
Sent from my iPhone
> On Apr 19, 2018, at 11:41 PM, Jeyapal, Karthick wrote:
>
>
>
>> On 4/20/18 9:02 AM, Steven Liu wrote:
>> reference hls support fmp4 file from draft-pantos-http-live-streaming-20
>> the spec describes version 7 of hls proto
Hey guys,
So I think this may be my own lack of knowledge in the encoder.
Because we were specifying -b:a 32k in our encoding step, I thought the byte
ranges should align properly, but I’ve since learned that is incorrect.
The compression is still variable in terms of bytes.
Therefore this is
29 matches
Mail list logo