5 ms·

My only direct interaction with ffmpeg and libavcodec/libavformat has been from a user and developer stand point. Most of it has been very poor, the code works

My only direct interaction with ffmpeg and libavcodec/libavformat has been from a user and developer stand point. Most of it has been very poor, the code works well, but their API both the C interface and the CLI could be a lot better.

jlarocco 14y ago
Couldn't agree more on the C API. The time I had to use it was a nightmare. There's almost no documentation, and the interface changes so often it's nearly impossible to find working sample code.
- ux 14y ago
  We did some work to improve this a little, see for example: http://git.videolan.org/?p=ffmpeg.git;a=tree;f=doc/examples;hb=HEAD http://git.videolan.org/?p=ffmpeg.git;a=tree;f=doc/examples;... This should be deployed with any new fresh ffmpeg install. The filtering code is still unstable due to what's explained in the blog post...
  - revelation 14y ago
    Its a start, but missing the point nonetheless. The grand idea is to have all the codecs and formats unified into one API, but the reality is that said API has become a gigantic dump yard. Redundant options and variables with one codec using one set and a different codec another. Not to mention to have stuff fail because a particular codec does not like a specific configuration.
  - jlarocco 14y ago
    It's good to see things improving. To be honest, the biggest problem I had was that searches would return too many out of date code snippets and sample code on other sites that didn't match the exact version I was using, so it wouldn't work for me. Other than that, once I got it working, it was awesome.
- gravitronic 14y ago
  I agree. I bet that 99% of "movie players" are direct clones of ffplay.