Good morning,
As already stated, the idea is that libcodec will be something more like
libstagefright, where libmedia2 will be like libmedia (I mean the android
versons OFC).
I think it is rather *obvious* why I choose this path in the end. But I
understand my work may be obvious sometimes so let's clarify a few things.
Okay, calling all comas, let's reply to the same questions again.
The media kit is, well, the base API for media processing. Media file I/O
is part of that, so to me it seems they should be in the same kit.
take care of formats and conversions, where the media2 will not have to
care about that except respecting the constraints of the codec kit.
Huh? That's the job of individual plugins, and then the media kit
respects those constraints already. Isn't that what we have now? Why do we
need a media2 here?
Sorry you don't understand the current issues with the media_kit. I am not
willing to repeat again and again.
The API design of BMediaTrack might need to be rethought, but the plug-in
API itself seemed mostly sound.
No. The problem is not BMediaTrack itself that works like similar classes
in other systems, the problem is what you plug into it.
Should I read "splitting them in a separate kit"? If not, I already
stated in a previous post that I may in the end use the same library for
the codec and media2 kit.
This doesn't make much sense. If you are trying to reuse code between the
Media Kit and Media2 Kit, then just move the functionality to the Media2
Kit and reimplement the Media 1 Kit classes using the new APIs. Which seems
to be what you are doing away, only fragmenting APIs in a way that makes
little sense.
Again, it seems you don't understand what I am doing.