On Mon, Aug 15, 2016 at 7:47 PM, Rostislav Pehlivanov <atomnu...@gmail.com> wrote:
> On 15 August 2016 at 11:51, Robert Krüger <krueger@lesspain.software> > wrote: > > > On Sun, Aug 14, 2016 at 5:05 PM, Rostislav Pehlivanov < > atomnu...@gmail.com > > > > > wrote: > > > > > On 10 April 2016 at 16:38, Kieran Kunhya <kie...@kunhya.com> wrote: > > > > > > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > > > The git master is fast changing and <anything> can happen API or setting > wise every day. Deprecations, behavioral changes, etc. This is why users > who need stability use the stable releases. Hell, we've removed far bigger > external library support this year. > So no. They've had PLENTY of time to switch to the internal AAC encoder > (since December last year) and plenty of versions to try out since then. > It's getting removed and it's getting removed soon. Like ffserver. > > Your call but definitely not a nice thing with regard to users. I may have missed it but I haven't seen an announcement that this is going to happen and thought deprecation was the tool exactly for that as is used in other software/frameworks/projects especially for non-exotic features like in this case probably one of the most used encoders out there in ffmpeg-based systems. but I will shut up now. You seem to have a pretty strong opinion on this and I'm merely providing input as a downstream user not a dev. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
