Hi,
2016-04-27 23:58 GMT+02:00 Carl Eugen Hoyos :
> Mark Thompson jkqxz.net> writes:
>
>> Unless someone can show what created this file and that
>> it might make more, I suggest that the hack workaround
>> should be removed.
>
> Is there a valid file affected by the applied patch?
> It is very i
Am 28.04.2016 um 17:27 schrieb Carl Eugen Hoyos:
> Please review, Carl Eugen
Is there a ticket number?
Matthias
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, 28 Apr 2016 16:46:49 +0200
Michael Niedermayer wrote:
> On Thu, Apr 28, 2016 at 03:34:34PM +0200, wm4 wrote:
> > The deprecated avcodec_decode_video2() and avcodec_decode_audio4()
> > functions called av_packet_split_side_data() on the input packets. This
> > is required for packets produ
On 4/18/16, Christophe Gisquet wrote:
> I think only the 2 first patches are needed, but I prefer the code
> from the 3rd+4th patches. Overall, it's still not the nicest code, and
> valgrind-proofing the patchset is needed (not possible atm for me).
>
> The SSE4 implementation is not worthwhile in
On 27.04.2016 16:08, Michael Niedermayer wrote:
On Tue, Apr 26, 2016 at 08:10:25PM +0200, Thomas Volkert wrote:
Hi,
,
On 21.03.2016 21:49, Thilo Borgmann wrote:
Am 21.03.16 um 20:42 schrieb Michael Niedermayer:
On Mon, Mar 21, 2016 at 12:14:40PM +0100, Thilo Borgmann wrote:
Hi,
last weekend
Hi,
On Thu, Apr 28, 2016 at 3:42 AM, Carl Eugen Hoyos wrote:
> Kieran Kunhya obe.tv> writes:
>
> > > It is very important that FFmpeg also decodes invalid
> > > files as long as no valid files are affected.
> >
> > Nonsense,
>
> > should FFmpeg be able to decode any file created by using netcat
Hi Ronald!
> So, since you're stating this as fact, I would like to point out that this
> was never formally agreed by any group of FFmpeg developers, and this is
> certainly not the official position.
Your message surprises me: The mpegts demuxer (before this discussed patch)
accepts all kind
Hi,
On Fri, Apr 29, 2016 at 7:52 AM, Carl Eugen Hoyos wrote:
> I was under the impression that the only reason that demuxers and decoders
> are written like that is that we all want FFmpeg to support invalid streams
> as long as this doesn't affect valid streams.
It's too broad. I want to know
On Wed, 27 Apr 2016 20:39:34 +0200
Piotr Bandurski wrote:
> Subject: [PATCH] avformat/riff: assign g721 and g723 codec tags to
> g726 decoder
> +{ AV_CODEC_ID_ADPCM_G726, 0x0014 },
> +{ AV_CODEC_ID_ADPCM_G726, 0x0040 },
i wonder if we should make a comment that these are diffe
On Tue, 26 Apr 2016 17:11:26 +0300
Александр Слободенюк wrote:
> { AV_CODEC_ID_MPEG2VIDEO, MKTAG('M', '7', '0', '1') },
> +{ AV_CODEC_ID_MPEG2VIDEO, MKTAG('M', '7', '0', '3') },
> { AV_CODEC_ID_MPEG2VIDEO, MKTAG('M', '7', '0', '5') },
i wonder if we can add m702 + m704 as wel
On Fri, Apr 29, 2016 at 08:09:34AM -0400, Ronald S. Bultje wrote:
> Hi,
>
> On Fri, Apr 29, 2016 at 7:52 AM, Carl Eugen Hoyos wrote:
>
> > I was under the impression that the only reason that demuxers and decoders
> > are written like that is that we all want FFmpeg to support invalid streams
>
Resolves https://trac.ffmpeg.org/ticket/4209
---
libavformat/movenc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavformat/movenc.c b/libavformat/movenc.c
index b9c0f7a..c237736 100644
--- a/libavformat/movenc.c
+++ b/libavformat/movenc.c
@@ -3084,6 +3084,7 @@ static int mov_write_udt
> I found another bug, this time in lossy mode - the file encoded as "joint
> stereo" decodes after a few seconds into noise:
>
> https://www.datafilehost.com/d/c2e8b332
There seems to be infinite loop while decoding fuzzed file:
https://www.datafilehost.com/d/eab97154
Please fix it as well in
On 4/27/16, Paul B Mahol wrote:
> On 4/18/14, Peter Ross wrote:
>> Signed-off-by: Peter Ross
>> ---
>> samples: www.acoust.rise.waseda.ac.jp/1bitcons/data.html
>>
>> Changelog| 1 +
>> doc/general.texi | 1 +
>> libavformat/Makefile | 1 +
>> libavformat/allfor
This is for the developers:
Building ffmpeg-20160428.tar.bz2
.
.
.
.
yasm -f elf -m amd64 -DPIC -I.
-I"/sdb3/home/jd/rpmbuild/BUILD/ffmpeg-20160428" -Pconfig.asm -I
libavcodec/x86/ -o libavcodec/x86/vp3dsp.o libavcodec/x86/vp3dsp.asm
libavcodec/x86/h264_qpel_mmx.c: Assembler messages:
libavcode
On Fri, Apr 29, 2016 at 05:08:39PM -0600, jd1008 wrote:
> This is for the developers:
> Building ffmpeg-20160428.tar.bz2
> .
> .
> .
> .
> yasm -f elf -m amd64 -DPIC -I.
> -I"/sdb3/home/jd/rpmbuild/BUILD/ffmpeg-20160428" -Pconfig.asm -I
> libavcodec/x86/ -o libavcodec/x86/vp3dsp.o libavcodec/x86/vp
On 04/29/2016 05:25 PM, Michael Niedermayer wrote:
On Fri, Apr 29, 2016 at 05:08:39PM -0600, jd1008 wrote:
This is for the developers:
Building ffmpeg-20160428.tar.bz2
.
.
.
.
yasm -f elf -m amd64 -DPIC -I.
-I"/sdb3/home/jd/rpmbuild/BUILD/ffmpeg-20160428" -Pconfig.asm -I
libavcodec/x86/ -o lib
On 4/29/2016 8:25 PM, Michael Niedermayer wrote:
> On Fri, Apr 29, 2016 at 05:08:39PM -0600, jd1008 wrote:
>> This is for the developers:
>> Building ffmpeg-20160428.tar.bz2
>> .
>> .
>> .
>> .
>> yasm -f elf -m amd64 -DPIC -I.
>> -I"/sdb3/home/jd/rpmbuild/BUILD/ffmpeg-20160428" -Pconfig.asm -I
>>
Please ignore.
Problem was in system.
On 04/29/2016 05:56 PM, jd1008 wrote:
On 04/29/2016 05:25 PM, Michael Niedermayer wrote:
On Fri, Apr 29, 2016 at 05:08:39PM -0600, jd1008 wrote:
This is for the developers:
Building ffmpeg-20160428.tar.bz2
.
.
.
.
yasm -f elf -m amd64 -DPIC -I.
-I"/sdb3
Hi all
@mentors, you all probably received the mail from Google about
community bonding. Please encourange your students to participate
in FFmpeg in some form
@students, google asked us to report any student that shows no activity
by the 16th may. Thus be active and participate in FFmpeg in some
20 matches
Mail list logo
