On Nov 14, 8:49 am, Dave Sparks <[EMAIL PROTECTED]> wrote: > 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.
It appears that not passing a surface into the camera object does cause a crash. > 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. I was finally able to give the camera a surface that is 0x0 pixels, and then use the preview callback image. The lag isn't a serious problem for my application, although it is unfortunate for those like Blindfold doing augmented reality apps. Dave, I just found a post you made on Issue 1271. Very helpful for when I try to crack open the actual data - thanks!: ( http://code.google.com/p/android/issues/detail?id=1271 ): > The actual format is YCbCr420 semi-planar. The Y-plane is followed by > an interleaved CbCr plane. This is a native format used by the G1 camera, > hardware > video codecs, and display processor. It enables hardware color conversion in > the > display processor which is a significant savings over software CC. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
