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/thread/434c60a275f3cc6f > >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 android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
