Hi Dave, I was able to display the YUV frame onto the ISurface. But as you had mentioned, the emulator is considering only the Y-data and displaying a gray-scale video. I just have few clarifications from my above exercise :
1. In most of the posts and also in the source code, whenever we talk to posting to the display, all talk of Surface Flinger whereas the Camera and the Media Player uses ISurface to render the display images onto the screen. I also see the implementation of the Surface Flinger to be more of a wrapper to the ISurface. Which of these objects would you recommend to be used for real-time rendering of YUV data? 2. I seem to not to understand the difference between ashmemory and pmem memory. Can you point out some overall differences between the same? 3. In my requirement, I would have a native library A render the YUV frames and map it to a Memory Heap. If another library say B wants to have access to this memory heap , as per my understanding, I will have to wrap the memory heap into IMemory and pass the same via a callback from A to B right? If so, should my memory heap type be ashmem or pmem? Please correct me if my understandings are wrong anywhere. Regards, Syed Ibrahim M -------------------------- On Jan 22, 12:33 am, Dave Sparks <[email protected]> wrote: > Yes, you need to make your class a friend of SurfaceHolder. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
