Dear experts,
In Android 4.2 release, I observe that in ACodec::LoadedState::onConfigureComponent, there is a call to initNativeWindow for all cases. In case of an encoder being employed as a ACodec, then initNativeWindow invokes enableGraphicBuffers on the encoder's output port with flag set to OMX_FALSE.
For an encoder, this is mandating to support an additional setParameter on the output port of the component. From a code perspective, I felt it is not intuitive to invoke a enableGraphicBuffers on output port.
Could someone please point to any potential reasons for the same?
Thanks,
Ganesh
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment