On Sunday, July 1, 2012 1:55:55 PM UTC+3, Jonathan Hartley wrote: > > I was interested to read this background on ffmpeg & libav. > > http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html > > I don't know whether this is an unbiased or authoritative account, but > it was still interesting to me just to find out about the split & its > contentiousness. >
There should be a conflict point somewhere, a conflict of interest. Let me turn on a paranoid bit. If I am not mistaken ffmpeg and libav are both C/C++. C/C++ is exploitable. I somebody is looking into a way to exploit many systems to add them to botnet or steal private keys secretly (which is more interesting nowadays) - attacking ffmpeg is a valid choice IMHO. Now avbin == Debian/Ubuntu, ffmpeg == everything else. What I am trying to say? Somebody should start writing non-GPL audio/video decompressors in pure Python and companies should invest in PyPy to make it beat those ancient technologies. Then the Earth will be safe again. =) Of course looking how codec processes one frame in n seconds could be boring, but what if the whole decoding process can be visualized with pyglet? I'd be interesting to see how video structure look like from inside and play with it instead of drilling through specifications and headers.. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/SzVLIR57J5QJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
