On 15/01/13 05:34, "Paweł Hajdan, Jr." wrote: > I'm trying to make Chromium be more compatible with more versions of > ffmpeg: > <https://groups.google.com/a/chromium.org/d/topic/chromium-dev/fm5Oe_AC3Sc/discussion> > (although not stated there, that includes libav). > > Now the initial response there is not enthusiastic (which doesn't > surprise me), but do you think there are some points useful for the > discussion I'm not aware of? > > What are the main challenges of keeping up-to-date with latest ffmpeg > API changes? How do other projects deal with that?
I guess it had been stated there, but is worth noting again that chromium has a specific fork of ffmpeg and they merge and adapt/fix as they need. As Libav we try to see what they are doing and when possible either import their fix or redo it in a more general way if it doesn't fit normal consumption (see our review process policy for more details). Their API usage is quite normal nowadays (after we convinced them to use AVIO instead of the deprecate URLProtocol, for our and their respective pleasure since it resulted in slashing a good chunk of cruft) Feel free to nag me if something breaks with a system libav. lu
