On 12/03/15 1:14 PM, Luca Barbato wrote: > On 12/03/15 13:54, Derek Buitenhuis wrote: >> On 3/11/2015 7:07 PM, Luca Barbato wrote: >>> On top of it, I wasn't aware it exists >> >> The feature has been complete and in FFmpeg master for 1.5+ years... >> >> I do not think "pretend FFmpeg doesn't exist and never look at it >> at all LALALAL I CAN'T HEAR YOU" is a valid stance to take as a >> competitive library. The only ones who suffer are users. > > Sure would be nice to add more features that are present in FFmpeg, but looks > like you and Hendrik missed the purpose of this patch. > > I want to write a walk through in the form of blogposts, so I need to write > something quite simple and possibly improve it incrementally. > > I did already for the demuxer (that maybe could enjoy a second post with the > feedback martin gave) that I know better. > > Since I do not know so well avfilter, I wanted to see if even this minimal > audio source is right before blogging (for the demuxer I blogged and then > sent the code to the ml). > > lu
Either write it, blog about it and do not apply the end result to the tree, or write a different simple filter instead. There are surely many filters ideas not yet written in any of the two projects one could write from scratch. "I'm doing it because i want to write a blog about how to write a filter" is not a good reason to create and apply a second implementation that inconveniences the end user. Or alternatively you could, after finishing writing this filter and the blog post, port aevalsrc and cherry pick code from your filter to improve the former. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
