Yes, one can hide the preview frame and do image processing on the data from the preview callback and only display the results of that. On Android/G1 this is painfully slow, but it is successfully used in my live image processing and sound synthesis app at
http://www.seeingwithsound.com/android.htm Another good thing is that this gets around the fact that the normal preview image cannot be freely positioned. ;-) Regards On Nov 14, 5:49 pm, Dave Sparks <[EMAIL PROTECTED]> wrote: > You cannot alter the preview frames as they are being displayed. > Camera preview uses a private shared interface between the camera and > SurfaceFlinger to display preview frames. It would be too costly to > pass this data across two process boundaries and a Java VM. > > You might be able to get away with not passing a surface into the > camera object. I don't think we've ever tested that. If it doesn't > work, let me know and we'll file a bug to get if fixed. In that case, > you would take the preview frame, do your filter operation on it, and > draw it directly to your own view. Expect the preview to be very laggy > though. > > If you just want to do an overlay, you can composite a window on top > of the preview frame. This will be much more efficient since the > native code is still doing the heavy lifting. On the G1, it's actually > a hardware display processor that takes care of color conversion, > rotation, and scaling, so it's really cheap. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
