4 ms·

I was thinking libav has replaces FFmpeg? Anyway, this project is very cool. I could see web workers working a mini video grid kind of system perhaps.

• aaronm67 13y ago
  We did get libav working, but it was much less stable than FFmpeg, and we couldn't get swscaler working (which meant a lot of videos would not work)
  • astrange 13y ago
    There shouldn't be that much difference between the two forks. Which parts were failing? For swscale, was it compile problems or something later? Also, if you have a way to run libav's "make fate" (regression tests), do you know which ones fail?
    • aaronm67 13y ago
      I'm not sure if we can private message on here, but if you would email me at aaronm67@gmail.com, or contact us on the github project, I can let you know our progress and where we got caught up.
• neeee 13y ago
  No, check out http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html. While Libav left with the server, bug tracker, etc., the FFmpeg project was restoring itself, with the help of some VideoLAN people (the FFmpeg sources are now hosted on git.videolan.org). Michael also started to merge the Libav changes back into FFmpeg every 1-2 day, with a lot of forgotten, previously rejected, sometimes controversial features, or in stand-by such as ffmpeg-mt. The main point here is that the fork stimulated the competition, and FFmpeg became a way better (IMHO) and more complete project. Also, I must say the leader's attitude completely changed, in a very good way. This is certainly one of the most positive thing that came out of that war.
  • 0x09 13y ago
    The mpv developers have written a really very good rundown of the current situation: https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav