On Fri, Jan 01, 2016 at 06:23:57PM +0100, Michael Niedermayer wrote:
> From: Michael Niedermayer
>
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/codec_desc.c |1 +
> 1 file changed, 1 insertion(+)
applied
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC7870
On Tue, Apr 21, 2015 at 03:12:36PM +0200, Michael Niedermayer wrote:
> memalign() is not guranteed to be compatible with free() or realloc()
> and for platforms in this category we have --enable-memalign-hack
> (which should be enabled automatically if such system is detected)
> Trying to somehow h
On 01/10/2016 04:04 AM, Mats Peterson wrote:
original private data, and finally sets track->codec->priv_data to the
Should be track->codec_priv.data of course.
Mats
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listi
How about this one, Michael? Rather than using the obviously dangerous
av_realloc() it uses av_malloc() to allocate new memory for the private
data, then copies the private data to it, frees the pointer to the
original private data, and finally sets track->codec->priv_data to the
newly allocate
On 01/10/2016 03:24 AM, Mats Peterson wrote:
I suppose that ebml_read_binary() in matroskadec.c is the function used
to read the private data, and it allocates memory using
av_fast_padded_malloc() for this. Is it safe to reallocate a pointer
from this function then? So far I've had no problems, b
On 01/10/2016 03:05 AM, Mats Peterson wrote:
I suppose that ebml_read_binary() in matroskadec.c is the function used
to read the private data, and it allocates memory using
av_fast_padded_malloc() for this. Is it safe to reallocate a pointer
from this function then? So far I've had no problems,
On 01/10/2016 02:20 AM, Michael Niedermayer wrote:
+if (!(track->codec_priv.data = av_realloc(track->codec_priv.data,
+track->codec_priv.size + 4)))
+return AVERROR(ENOMEM);
in case of this failing the memory is not freed and leaks
see av_reallocp() if you
On 1/9/2016 9:28 PM, Kieran Kunhya wrote:
> ---
> libavcodec/Makefile | 1 +
> libavcodec/allcodecs.c | 1 +
> libavcodec/avcodec.h| 1 +
> libavcodec/cfhd.c | 565
>
> libavcodec/cfhd.h | 99 +
> libavcodec/cfhd
On Sat, Jan 09, 2016 at 12:02:19PM +0100, Mats Peterson wrote:
> Minor simplification of get_qt_codec(). Description follows:
>
> This patch adds a new static function get_qt_codec() that takes care
> of the initial retrieval of the fourcc and codec ID for A_QUICKTIME
> and V_QUICKTIME. It also no
On 10 January 2016 at 00:17, Ricardo Constantino wrote:
> On 9 January 2016 at 23:32, Michael Niedermayer
> wrote:
>
>>
>> we should pass the version number we need i think
>> see
>>
>> https://quickgit.kde.org/?p=libktorrent.git&a=commit&h=a23bafe9191e0dcbd5ae75335fd5d8e49bfda9ed
>>
>>
> I woul
---
libavcodec/Makefile | 1 +
libavcodec/allcodecs.c | 1 +
libavcodec/avcodec.h| 1 +
libavcodec/cfhd.c | 565
libavcodec/cfhd.h | 99 +
libavcodec/cfhddata.c | 470
li
---
libavformat/riff.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavformat/riff.c b/libavformat/riff.c
index f297dd4..faf0f86 100644
--- a/libavformat/riff.c
+++ b/libavformat/riff.c
@@ -377,6 +377,7 @@ const AVCodecTag ff_codec_bmp_tags[] = {
{ AV_CODEC_ID_SCREENPRESSO, MKTAG('S'
On 9 January 2016 at 23:32, Michael Niedermayer
wrote:
>
> we should pass the version number we need i think
> see
>
> https://quickgit.kde.org/?p=libktorrent.git&a=commit&h=a23bafe9191e0dcbd5ae75335fd5d8e49bfda9ed
>
>
I wouldn't know the minimum version FFmpeg needs.
Wouldn't it be better to lea
On Sat, Jan 09, 2016 at 09:23:43PM +, Paul B Mahol wrote:
>
> I already set color range.
Fixed and pushed.
Timothy
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Mon, Jan 04, 2016 at 02:39:41AM +, Ricardo Constantino wrote:
> On 3 January 2016 at 23:13, Jan Ekstrom wrote:
>
> > Hi,
> >
> > In general looks good, although it might look a bit weird for someone
> > as usually libraries have initialization functions called like that.
> > That said, thi
On Sat, Jan 09, 2016 at 12:04:27PM +0100, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch fixes ticket #5142.
>
> Please comment, Carl Eugen
> libx264.c |2 ++
> 1 file changed, 2 insertions(+)
> 98178e28de0e96f9e4c9f1f1ddcc4d75055d48bd patchx264coder.diff
> diff --git a/libavcodec/libx26
From: Aman Gupta
---
libavcodec/ccaption_dec.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/libavcodec/ccaption_dec.c b/libavcodec/ccaption_dec.c
index fc6431b..8bef771 100644
--- a/libavcodec/ccaption_dec.c
+++ b/libavcodec/ccaption_dec.c
@@ -165,6 +165,24 @@ static
From: Aman Gupta
This new mode is useful for realtime decoding of closed captions so they
can be display along with mpeg2 frames.
Closed caption streams contain two major types of captions:
- POPON captions, which are buffered off-screen and displayed
only after EOC (end of caption, aka displ
On 1/9/16, Timothy Gu wrote:
> ---
> libavfilter/avf_showspectrum.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libavfilter/avf_showspectrum.c b/libavfilter/avf_showspectrum.c
> index 5b26be8..a967a41 100644
> --- a/libavfilter/avf_showspectrum.c
> +++ b/libavfilter
---
libavfilter/avf_showspectrum.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavfilter/avf_showspectrum.c b/libavfilter/avf_showspectrum.c
index 5b26be8..a967a41 100644
--- a/libavfilter/avf_showspectrum.c
+++ b/libavfilter/avf_showspectrum.c
@@ -240,7 +240,7 @@ stati
Le decadi 20 nivôse, an CCXXIV, kovacsr...@proci.hu a écrit :
> The windows shell can't comment inline, can't tagging with new line simply
> and the script file is not compatible with Linux.
> I use both operating system. This solution makes it possible to create
> UNIVERSAL control files.
You ca
Hi
The windows shell can't comment inline, can't tagging with new line simply
and the script file is not compatible with Linux.
I use both operating system. This solution makes it possible to create
UNIVERSAL control files.
Shell can't make dynamically generated script with etc.:
http://localhos
From: "ha...@mayartech.com"
This commit adds a hardware accelerated H.264 encoder which utilizes
libVA (open source implementation of VA-API). Information about libva
is available at: https://en.wikipedia.org/wiki/Video_Acceleration_API
This encoder is only availbale on linux and supported hardwa
On 1/9/2016 11:43 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Fri, Jan 8, 2016 at 10:12 PM, Sasi Inguva wrote:
>
>> Pass through color range to vp9 encoder. Parse color range in libvpxdec.c.
>>
>> Signed-off-by: Sasi Inguva
>> ---
>> libavcodec/libvpxdec.c | 6 ++
>> libavcodec/libvpxenc.c |
Ping
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hi,
On Fri, Jan 8, 2016 at 10:12 PM, Sasi Inguva wrote:
> Pass through color range to vp9 encoder. Parse color range in libvpxdec.c.
>
> Signed-off-by: Sasi Inguva
> ---
> libavcodec/libvpxdec.c | 6 ++
> libavcodec/libvpxenc.c | 26 ++
> 2 files changed, 32 insert
From: Clément Bœsch
---
TODO
- ass_split needs to be able to handle dialog event without "Dialogue:
..." so our encoding chain can handle the sane decoded subtitles
- zvbi needs testing
- option sub_text_format needs to be documented and default ready to be
changed
- doxy ff_ass_*
- minor or
---
libavcodec/Makefile | 4 ++--
libavcodec/assdec.c | 60 +++-
libavcodec/assenc.c | 14 ++--
libavformat/assenc.c | 14
libavformat/nut.c| 1 -
5 files changed, 24 insertions(+), 69 deletions(-)
diff --git a/libavcod
Hi!
Attached patch fixes ticket #5142.
Please comment, Carl Eugen
diff --git a/libavcodec/libx264.c b/libavcodec/libx264.c
index 4dc531a..88406a3 100644
--- a/libavcodec/libx264.c
+++ b/libavcodec/libx264.c
@@ -953,6 +953,8 @@ static const AVOption options[] = {
{ "default", NULL, 0
Minor simplification of get_qt_codec(). Description follows:
This patch adds a new static function get_qt_codec() that takes care of
the initial retrieval of the fourcc and codec ID for A_QUICKTIME and
V_QUICKTIME. It also normalizes noncompliant private data found in some
older files that inc
Hi!
A user has provided a "spdif" file that is incompatible with my hardware
receiver but used together with SDI and MXF as specified by SMPTE (iiuc).
See "Ingest of SMPTE-377M" on the FFmpeg user mailing list.
Attached patch allows to write such files, I cannot test.
Please review, Carl Eugen
James Zern google.com> writes:
> On Fri, Jan 8, 2016 at 1:58 AM, Carl Eugen Hoyos wrote:
> > Attached patch fixes ticket #5140 here
> lgtm. thanks.
Patch applied.
Thank you, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffm
32 matches
Mail list logo