I'm not even sure whether Android's yuv422sp preview format represents any decent standard format, because with a previous SDK M5 RC15 we got a color preview on the emulator screen, whereas nowadays with SDK 1.0 r1 it shows as greyscale only. Moreover, although the preview array for me shows a size corresponding to 176 x 144 at 16 bpp (namely 50688 bytes), I get a nice clean greyscale image if I just save the preview image as a raw binary file and next import it into for instance IrfanView as a 176 x 144 8 bpp (1 byte per pixel greyscale) headerless raw image file, thus brutally discarding the second half of the byte array! By loading the file as 16 bpp I can see that there is color info in the second half of the file, but as far as reproducing the greyscale emulator preview is concerned, simply treating the (first half of the) byte array as 176 x 144 8 bpp pure greyscale encoding seems to suffice.
I wonder what byte array the physical G1 generates as preview image... I still haven't had any answers from the Android Team on my various camera questions lately, while camera based image processing in Android currently has some serious unresolved issues. Regards On Oct 22, 5:52 pm, Jason Proctor <[EMAIL PROTECTED]> wrote: > yes, but the issue is whether the encoding is chunky or planar, and > whether the chrominence values are signed. the "SP" on the end of the > format implies both, but my decoder isn't having much luck either way. > > ffmpeg is a command line program. i'm trucking through the source, > but some of it reads a little like Martian :-) > > thanks for the response. it's no big deal, i can keep trucking. i > hoped someone on the 'droid team could provide a quick authoritative > answer. > > >I noticed that data.length in the callback gave twice the number of > >pixels, implying a 16 bits per pixel encoding as was discussed at > > >http://groups.google.com/group/android-developers/browse_thread/threa... > > >Does ffmpeg not have some properties dialog or something such that > >more information can be gleaned about the YUV422SP encoding details? > > >On Oct 22, 5:12 pm, Jason Proctor <[EMAIL PROTECTED]> wrote: > >> well, ffmpeg can decode it, so it *is* a real format. but i'm trying > >> to decode a little of it myself for nefarious purposes, and ffmpeg is > >> a touch difficult to read ;-) so i was hoping someone here knew the > >> skinny. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
