On Sun, Jan 03, 2016 at 01:37:18PM -0500, Derek Buitenhuis wrote: > It serves absolutely no purpose other than to confuse potentional > Android developers about how to use hardware acceleration properly > on the the platform. Both stagefright itself, and MediaCodec, have > avcodec backends already, and this is the correct way to use it. > MediaCodec as a proper JNI API.
MediaCodec is the current way to go on Android either via JNI or using its C API that has been introduced in Android 5. I'm not sure if there is already an avcodec backend for it as I'm currently working on one based on the C API (h264 decoding is working, the flush command still need to be implemented; some patch can be expected at the end of the month). > > Furthermore, stagefright support in avcodec needs a series of > magic incantations and version-specific stuff, such that > using it actually provides downsides compared just using the actual > Android frameworks properly, in that it is a lot more work and confusion > to get it even running. It also leads to a lot of misinformation, like > these sorts of comments (in [1]) that are absolutely incorrect. +1 for removal (but I'm not an user of this backend). Matthieu [...] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
