On 11/17/16, Andreas Cadhalpun <andreas.cadhal...@googlemail.com> wrote: > On 17.11.2016 17:27, Nicolas George wrote: >> Le quartidi 24 brumaire, an CCXXV, Andreas Cadhalpun a ecrit : >>> API changes in libavfilter are less of a problem, since not that many >>> programs use it. For example, the codecpar change has orders of magnitude >>> more impact. >> >> I mostly agree. If people are ok with a sudden API change in lavfi, then >> I can rework my patch for that. But I want confirmation beforehand. > > I don't think a sudden API change would be good. > >> A scheduled API change would be better, but I do not want to wait for it >> to apply the patch, so you would have to accept a temporary solution. > > I understand that and think a temporary solution would be OK if it's clear > that it will be removed in say 2 years. > >>> However, ideally any incompatible API change should be coordinated with >>> Libav. >> >> I have been spurned in the past in my attempts to coordinate lavfi >> evolution with libav, I will not make efforts again for that. > > That's sad. Maybe someone who uses the libavfilter API from both forks can > help and mediate in this matter?
Don't hold your breath, Libav interest in lavfi is very limited imho. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
