3 ms·
Is this related to the libav/ffmpeg dustup from a few months ago? (see here: http://lwn.net/Articles/433347/ http://lwn.net/Articles/433347/ ) Seems to be a lo
by zdw 16y ago
Is this related to the libav/ffmpeg dustup from a few months ago? (see here: http://lwn.net/Articles/433347/ http://lwn.net/Articles/433347/ )
Seems to be a lot of drama in the open source codec space, and I'm really not sure who is on what side or what the issues at stake are.
Anyone care to explain what's going on?
- wmf 16y agoYes, it looks like the admin of mplayerhq.hu sided with libav in the fork and someone on the other side got pissed.
- pontifier 16y agoThere was an article linked from ffmpeg.org that seems to have a lot of information, especially in the comments there. http://lwn.net/Articles/423702/ http://lwn.net/Articles/423702/
- jallmann 16y agoThis announcement has its roots in the FFmpeg/libav fork. For a long time, FFmpeg resources were hosted on the MPlayer server. (Not sure if they still are; its git has been migrated to videolan at least.) Like a number of OSS devs, people on both sides of the fork share traits of being a) brilliant hackers, b) stubborn and c) prone to mannerisms that people may interpret as rude or inflammatory, whether intentional or not. I for one am sad to see this whole fork happen. If it were driven by interests pursuing divergent goals, then that's understandable, but this fork is purely politics. Codec development is already an arcane art, and there are dozens of RE'd (or poorly documented) codecs in the FFmpeg codebase. Splitting up development and maintenance effort is not going to help anybody in this case.