OpenCore

[fala70]

Anybody know if is possible use directly OpenCore from java or
native
with NDK ?
thanks

[David Turner]

OpenCore is intentionally not exposed through the NDK.

[Dan Marlin]

David,

Can you explain further on why its not accessible from the NDK? We
had high hopes to port a lot of the work we have done in CorePlayer
for Android into the native space as much as we can because of the
third party hardware accelerations schemes (among other things).

Also... can you comment on the status of the:

- Alsa Audio input
- The availability of natively accessing the video renderer

Thank You.

Dan Marlin
CEO/CoreCodec, Inc.

[David Turner]

It's really simple, we only expose native ABIs we think we can support entirely for the next 10 years,
and the media stuff is not ready yet for this. Now let me explain the details:

The media framework within Android is changing all the time, so is the graphics subsystem, the browser
and a lot of other things, and we can't freeze their APIs and ABIs for application developers without adding
lots of bloat in the system; because supporting old versions of system libraries generally requires more space
taken from the system partition, and often some creative hacking that takes lots of developer times and
introduces "interesting" issues later in the process.

There is an interesting spectrum between the things a company like Microsoft would do to ensure backwards
compatibility (and we now it's damn horrible, given that it involves perpetuating bad design decisions for
several decades), and those done by Linux distributions (where everything gets recompiled in the new distro
hotness, which is only possible if you have the source of all packages). Android tries to be in the middle and
must ensure a stable foundation for applications, most of them proprietary, available to users.

Native code stability is by definition extremely brittle compared to VM languages like Java and we're serious
about supporting existing applications as much as we can. I'm constantly in touch with other engineers responsible
with other parts of the system. There is a general willingness to open as much stuff as possible to native code,
as long as we have a very clear path regarding API and ABI stability.

I can't give you specifics or ETAs, but I know that we want to expose native ABIs for sound and media in
the future though. And we definitely prefer to use standard APIs instead of inventing our own whenever
possible.

Hope this helps

[Tim Hutt]

2009/9/28 David Turner <di...@android.com>:

> I can't give you specifics or ETAs, but I know that we want to expose native
> ABIs for sound and media in
> the future though.

Not even a tentitative too-the-nearest-year estimate? :-)

[David Turner]

Not even sorry, I hate over-promising, especially when the real work is done by someone else :-)
 

[fala70]

My problem is that I need to work directly with decodes and encoders
functions using single frames. On java level I can only work with
files recorder and player.
The only solution then is make a porting of a codec library C or CPP
on NDK layer. Right David ? Be can a right solution ?

[Kevin]

I am pushing for better audio support in the NDK, see Android Bug
3434.
http://code.google.com/p/android/issues/detail?id=3434

Kevin

[Dianne Hackborn]

Do you really have to post this to every list in the world?  All you are doing is annoying people.

--
Dianne Hackborn
Android framework engineer
hac...@android.com

Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails.  All such questions should be posted on public forums, where I and others can see and answer them.