FFmpeg and a thousand fixes

Re:FFmpeg and a thousand fixes by IceyEC on Friday January 10, 2014 @01:38PM (#7038435)

I get a kick out of the fact that they recommend not using FFMPEG but they say that Chrome uses it.

[ Parent | on HN ]

Re:FFmpeg and a thousand fixes by jcampbell1 on Friday January 10, 2014 @02:30PM (#7038784)

Chrome is probably using a subset that represents 2% of FFMpeg. I'd guess they have thoroughly audited the code paths that are actually used to decode about 10 media different that chrome supports.

For instance, one fix mentioned was a fix the demuxer for .4xm files. 4xm is a proprietary container format for a now defunct company. Chrome would never have to worry about this bug, because it doesn't need to support playback of .4xm files.

[ Parent | on HN ]

Re:FFmpeg and a thousand fixes by fletchowns on Friday January 10, 2014 @01:45PM (#7038494)

They aren't just flat out not recommending using FFmpeg, just that you need to take appropriate measures when dealing with untrusted media sources.

[ Parent | on HN ]

Re:FFmpeg and a thousand fixes by abraham on Friday January 10, 2014 @01:44PM (#7038482)

> I get a kick out of the fact that they recommend not using FFMPEG

More specifically Google is recommending you don't use it to "process untrusted media files"

[ Parent | on HN ]

Re:FFmpeg and a thousand fixes by ID_HOME on Friday January 10, 2014 @03:05PM (#7039010)

I don't trust any media files... Especially ones from Google who are doing most of the research... seriously though, media zero-days are unheard of, probably because they would be extremely valuable.

[ Parent | on HN ]