top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is the best C native library(framework) for video rendering for usage in Android?

0 votes
301 views

I'm looking for native library for video play with custom buffering for rendering of big video files (500MB+) in android application. What is the best options?

posted Mar 22, 2013 by Salil Agrawal

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

Do you need a library with a JNI wrapper or just a native one?

We are using FFMPEG (libav) for that purpose, but it doesn't have any ready to use JNI. You can search for a Java wrapper though.

It's quite heavy weight, but can do many various stuff. The cons are that there isn't much documentation in the internet. And almost all tutorials are now outdated because the API changes really fast.

That's a good tutorial to start. The best documentation is their doxygen at http://ffmpeg.org/doxygen/trunk/index.html or http://libav.org/doxygen/master/

We haven't found anything better yet..

answer Sep 20, 2013 by anonymous
Similar Questions
+3 votes

We know there are bootstrap themes for free to use but don't know if there is same for android layouts so that we can reduce the time while designing the app UI. If someone know, please share the link?

+1 vote

I'm using uri to read the contacts that are stored in mobile. Now I want display those names in autocomplete. Please explain me how to add uri in AutoCompleteTextView?

+4 votes

What is Unable to resolve target 'android-15' until the SDK is loaded? IN eclipse I am getting the error while am try to run my app. Please help me how to solve this issue.

+2 votes

Similar to HAL for enabling s/w apps development on variety of h/w platforms, can a generic OS abstraction Layer ( OAL) be developed such that the apps written on top be immediately supported on all underlying platform?

IOAL can expore two interfaces. The southbound will expose open APIs towards the underlying OS ( Android/IOS/WIndows/Blackberry) which can then invoke the native APIs on OS. More than APIs the other mechanism of dealing with underlying OS will be embedded in this interface.

The northbound interface will be the standard APIs towards the APPs. This will be uniform across platforms. The OAL will also manage abstracted resources inside as it may be required to manage the underlying OS.

There will be no h/w intelligence/awareness inside this layer. This may puncture the individual power of popular platforms which draw strength from number of apps on it.

...