Signed-off-by: James Almer
---
libavcodec/x86/utvideodsp.asm| 20 ++--
libavcodec/x86/utvideodsp_init.c | 2 +-
2 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/libavcodec/x86/utvideodsp.asm b/libavcodec/x86/utvideodsp.asm
index
Hi,
I noticed (using Wireshark) that FFMPEG (3.1.8) would sometimes close
an RTSP control connection (TCP FIN) before it tries to get a response
to the TEARDOWN request.
There is an open bug (https://trac.ffmpeg.org/ticket/4929) about not
sending TEARDOWN, it's probably still not solving this
On 6/29/2017 10:14 PM, Henrik Gramner wrote:
> On Fri, Jun 30, 2017 at 1:58 AM, Michael Niedermayer
> wrote:
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00684919 in ff_sbr_hf_gen_sse ()
>
>>0x00684909 : sub
On Fri, Jun 30, 2017 at 1:58 AM, Michael Niedermayer
wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00684919 in ff_sbr_hf_gen_sse ()
>0x00684909 : sub%r9,%r8
> => 0x00684919
I am posting this question in development community because the feature
that I am looking for is not supported as per my understanding. I would
like to know what ffmpeg developers think about implementing this. I hope
this is the right place for such question.
So this is how it goes:
Quoting
On Wed, Jun 28, 2017 at 03:02:42PM +0300, ffm...@a.legko.ru wrote:
>
> subject: when input sample stops, input thread stops too (withous
> restart), thus, breaking the streaming and loop mode does not affect
> this. touches only multistream (multiprog) mode, when threads are
> used.
>
>
On Wed, Jun 28, 2017 at 02:48:55PM +0200, Matthieu Bouron wrote:
> On Fri, Jun 23, 2017 at 05:01:35PM +0200, Matthieu Bouron wrote:
> > On Thu, Jun 22, 2017 at 12:53:52PM -0300, James Almer wrote:
> > > On 6/22/2017 9:56 AM, Matthieu Bouron wrote:
> > > > ---
> > > >
> > > > The following
On Wed, Jun 28, 2017 at 07:22:01PM +0530, Paras Chadha wrote:
> Added code to export metadata as frame metadata
>
> Signed-off-by: Paras Chadha
> -
[...]
> +/**
> + * function reads the fits header and stores the values in FITSDecContext
> pointed by header
> + * @param
Am 29.06.2017 21:45 schrieb "Derek Buitenhuis" :
On 6/29/2017 3:06 PM, Saverio Blasi wrote:
> ---
> LICENSE.md | 1 +
> configure | 6 +
> libavcodec/Makefile| 1 +
> libavcodec/allcodecs.c | 1 +
> libavcodec/libturing.c | 313
On 6/29/2017 6:17 PM, James Almer wrote:
> On 6/29/2017 5:51 PM, Michael Niedermayer wrote:
>> On Thu, Jun 29, 2017 at 03:52:05PM +0100, Derek Buitenhuis wrote:
>>> From: John Stebbins
>>>
>>> ff_mp4_obj_type contains the wrong type of tags for
>>>
On 6/29/2017 5:51 PM, Michael Niedermayer wrote:
> On Thu, Jun 29, 2017 at 03:52:05PM +0100, Derek Buitenhuis wrote:
>> From: John Stebbins
>>
>> ff_mp4_obj_type contains the wrong type of tags for
>> AVOutputFormat.codec_tag. AVOutputFormat.codec_tag is used to
>>
On Thu, Jun 29, 2017 at 03:52:05PM +0100, Derek Buitenhuis wrote:
> From: John Stebbins
>
> ff_mp4_obj_type contains the wrong type of tags for
> AVOutputFormat.codec_tag. AVOutputFormat.codec_tag is used to
> validate AVCodecParameters.codec_tag so needs to be the same
On Thu, 29 Jun 2017 21:26:47 +0100
Derek Buitenhuis wrote:
> On 6/29/2017 9:09 PM, wm4 wrote:
> > On Thu, 29 Jun 2017 20:45:10 +0100
> > Derek Buitenhuis wrote:
> >
> >> Keep in mind that C99 bool and C++
> >> bool are not compatible.
On 6/29/2017 9:09 PM, wm4 wrote:
> On Thu, 29 Jun 2017 20:45:10 +0100
> Derek Buitenhuis wrote:
>
>> Keep in mind that C99 bool and C++
>> bool are not compatible.
>>
>
> (Actually they are.)
Source?
On Thu, 29 Jun 2017 20:45:10 +0100
Derek Buitenhuis wrote:
> Keep in mind that C99 bool and C++
> bool are not compatible.
>
(Actually they are.)
___
On 6/27/2017 10:59 AM, foo86 wrote:
> +static int s337m_get_offset_and_codec(AVFormatContext *s,
> + uint64_t state,
> + int data_type, int data_size,
> + int *offset, int *codec)
NIT:
On 6/29/2017 3:06 PM, Saverio Blasi wrote:
> ---
> LICENSE.md | 1 +
> configure | 6 +
> libavcodec/Makefile| 1 +
> libavcodec/allcodecs.c | 1 +
> libavcodec/libturing.c | 313
> +
> 5 files changed, 322
On 6/27/17, foo86 wrote:
> ---
> Changelog| 1 +
> doc/general.texi | 1 +
> libavformat/Makefile | 1 +
> libavformat/allformats.c | 1 +
> libavformat/s337m.c | 205
> +++
>
On Thu, Jun 29, 2017 at 12:47:58PM -0300, James Almer wrote:
> On 6/28/2017 10:21 AM, Clément Bœsch wrote:
> > We have AV_CPU_FLAG_ARMV8 == AV_CPU_FLAG_SSE3 which causes a trigger of
> > this MMX warning on AArch64.
> > ---
> > libavutil/cpu.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1
On 6/28/2017 10:21 AM, Clément Bœsch wrote:
> We have AV_CPU_FLAG_ARMV8 == AV_CPU_FLAG_SSE3 which causes a trigger of
> this MMX warning on AArch64.
> ---
> libavutil/cpu.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libavutil/cpu.c b/libavutil/cpu.c
> index
From: John Stebbins
ff_mp4_obj_type contains the wrong type of tags for
AVOutputFormat.codec_tag. AVOutputFormat.codec_tag is used to
validate AVCodecParameters.codec_tag so needs to be the same
type of tag.
Creates new tag lists for mp4 and ismv. New tag lists support
On 6/29/2017 7:51 AM, Paul B Mahol wrote:
> EVRC is audio codec. Shouldn't be mp4a.
Yes.
- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, 29 Jun 2017 14:06:21 +
Saverio Blasi wrote:
> - This patch contains the changes to interface the Turing codec
> (http://turingcodec.org/) with ffmpeg. The patch was modified to address the
> comments in the review as follows:
> - Added a pkg-config file
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) with ffmpeg. The patch was modified to address the
comments in the review as follows:
- Added a pkg-config file to list all dependencies required by libturing.
This should address the issue pointed out
On Thu, 29 Jun 2017 13:54:51 +
Saverio Blasi wrote:
> - This patch contains the changes to interface the Turing codec
> (http://turingcodec.org/) with ffmpeg. The patch was modified to address the
> comments in the review as follows:
> - Added a pkg-config file
- This patch contains the changes to interface the Turing codec
(http://turingcodec.org/) with ffmpeg. The patch was modified to address the
comments in the review as follows:
- Added a pkg-config file to list all dependencies required by libturing.
This should address the issue pointed out
I noticed this with mastering display data. If frame threading is
enabled, this side data is exported only for some frames. It turns out
it's not properly propagated to the worker threads.
I didn't touch A53 captions, because that involves memory allocation and
freeing the data as side data is
On Tue, 16 May 2017 07:45:14 +
Saverio Blasi wrote:
> Dear all,
>
> We would appreciate if you could let us know the procedure and expected
> timeline for integration of our patch related with the Turing codec within
> the ffmpeg project.
FFmpeg is a project by
Hi there,
This problem is exactly the same as that reported in
https://github.com/soimort/you-get/issues/1270
When I try to download HLS with FFMPEG, FFMPEG automatically skip those
segments with the same #EXTINF value. However, it makes the downloaded
video stutter, suggesting that these
On 6/29/17, Derek Buitenhuis wrote:
> From: John Stebbins
>
> ff_mp4_obj_type contains the wrong type of tags for
> AVOutputFormat.codec_tag. AVOutputFormat.codec_tag is used to
> validate AVCodecParameters.codec_tag so needs to be the same
>
30 matches
Mail list logo