On Thu, Apr 19, 2012 at 02:19:54AM +0400, Kostya Vasilyev wrote:
> I'm not saying you dreamed those up, sorry, no offence meant.
>
> But since we seem to be discussing memory usage, not disk usage, the
> compressed size is irrelevant.
Thank you. My point exactly.
> And 5 megapixels at RGB_8888 is 32 bits per pixel or 20 megabytes in
> RAM, if stored as an uncompressed pixel array.
Again, my point exactly.
A couple of posts got this thread severely side-tracked, which is getting
really annoying, as I'm seriously asking for help on the issue I
originally posted about[1] in this thread, not stupid jpeg sizes.
Later,
--jim
[1] trying to find out if there's a way to process photo and filter
bitmaps in chunks, and possibly save them in chunks, as well, or
perhaps use some other method, to allow users to keep their maximum
resolution, at 24-bit color, not lousy 16-bit color, and *DEFINITELY*
not, as I saw suggested in one of the many old posts I read, reducing
the resolution to work with it, and then raising it back up to full
resolution, presumably thinking that the lost resolution would just
magically restore itself. :-)
--
THE SCORE: ME: 2 CANCER: 0
73 DE N5IAL (/4) | "My spell checker eloped with a wiccan
spooky1...@gmail.com | and I've not seen it since!"
< Running FreeBSD 7.0 > |
ICBM / Hurricane: | (from news.admin.net-abuse.email)
30.44406N 86.59909W |
Android Apps Listing at http://www.jstrack.org/barcodes.html
--
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
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
