On Thu, Dec 14, 2017 at 12:39 AM, Josh de Kock <j...@itanimul.li> wrote: > On Thu, 7 Dec 2017 11:08:47 +0000 > Matteo Naccari <matteo.nacc...@bbc.co.uk> wrote: > >> - This patch contains the changes required to interface the Turing codec >> [...] > > I still have an issue with this patch, while it would be nice to have another > HEVC encoder available in FFmpeg for comparisons and whatnot, I feel that > turingcodec isn't a mature enough encoder compared to what is already in the > project. > > Not to mention that development seems to have stalled (with only very minor > fixes for several months). In FFmpeg it is very difficult to remove > 'features', so if this patch were to be merged and then turingcodec to > actually go stale we'd be left with dead code for longer than is ideal > (forever). > > My opinion is that you should just maintain this separately as an out-of-tree > patch as it doesn't benefit us. >
Hi, After taking a look at the commit history of the last year+ or so, issue tracker and pull request list over at https://github.com/bbc/turingcodec I must say I find it somewhat hard to disagree on a general level. Creating an encoder is great work and I applaud people for that, but unfortunately it - at the current point of time - looks like neither from the licensing, performance or project activity point of view merging a wrapper for this library is a good idea. Best regards, Jan _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
