GP32 Jpeg and ram


NiN^_^NiN

YOUR AUSSIE GP32 GURU!!!!!!!!&#3
Joined
May 30, 2003
Messages
1,008
Age
40
Location
Melbourne, Australia
Website
ninja.doomportables.org
After using the gpviewer i relised it dosent read files over a certin pixels and i was wondering if this is cause of the ram? when it decodes is that the max you can get?

I had the idea of using my digicam then just poping the smc card from it intot he gp32 to see the images and when i did the program said to big :(

It's a 2.1mp camera so is it possible to view these images on the gp32?

:ph34r:
 
Thanks reeced but thats useless. This is what i want to do.

Take pictures with my 2.1mp camera
take the smc card out of the camera
insert the smc card into the gp32
launch the image viewer on the gp
select the image i just took
view image

Now i can take pictures and select the images i just took on the gp but the image viewer dosent support 2.1mp

2.1mp image size is 1600 x 1200 and it cant support this size

So i wanted to know if it was cause that size is to big to load into ram to view?

And if any1 is nice enough to make a image viewer for me ;)
 
I had that problem too, but I use GPFM (GamePark File Manager). It has a picture viewer and I have been able to view really big pictures. I love it!
 
I wanted to do the same thing with my Olympus camera. I couldn't find any programs that would view my pictures. GPFM would view the Olympus JPGs if I took them at a small size, but most of my pictures wouldn't work.

I tried to write a JPG viewer myself, but I ran into some problems because the Olympus pictures are somewhat odd. They actually have 2 JPGs inside of them: a thumbnail and the actual picture.

I passed my code on to a couple others, but so far I haven't heard of anyone creating a viewer that will view the larger JPGs.

One of the guys I gave the code to called himself Nitro. I don't know if he's a member here or not. I also talked to Pékélé about incorportating it into GPART. So, maybe one of those guys will come in here and add some insight.
 
i hope so how far did you get? did it view jpeg images? if so did it view images upto or more than 1600 x 1200?

I just formated my smc card n just dragged the files over again and nothing but i did see images that were like 320 x 240 etc it cant even see semi big files

the gp viewer will view bigger images than this :(

I really need a jpeg viewer that supports prob max 2000 x 2000 Mp that should be big enough for most digital cameras

a 3.1mp camera is 2160 x 1400 so if that was supported then at least it be helpful for other people.

:ph34r:
 
Digital cameras are not the only things that add extra header information to jpeg images. Photoshop actually adds its own thumbnail information to jpegs when they are saved, and since a lot of images on the web etc are saved in photoshop, the jpeg viewer I'm using won't read them properly.
Since the thumbnail picture comes before the real image, the jpeg reader picks up the thumbnail first and so that's what's processed. I've tried numerious ways of getting it to ignor this extra header information, but I've had no luck so far :(

As for the maximum size that can be viewed, I'd say it was around 1400 x 1400 which is about 5.6mb in memory. 2000 x 2000 would be 11.4mb which is well over the amount of ram the GP32 has. You need to remember that the program must be loaded into ram which takes about a meg, then the jpeg data must be loaded into ram and then what ever is left can be used to decode the picture.
 
You could easily view a picture of almost unlimited size, my amiga with its 1meg of ram could via any jpg no matter how big! It just scrolled the screen.

Its only a picture and you could decode on the fly as it was viewed, no big deal. Just no one has made a good viewer yet.

-Craig

www.gbax.com
 
I think there are 2 main issues here.

The code that I gave to Nitro was based on the TinyJPEG decoder source. That source code doesn't handle all JPEGs properly.

The other issue is that the people that do have source that handles all JPEGs properly haven't converted them to handle the RAM limitations of the GP32. I mean, there are some simple things that can be done to handle larger images. If an image is too large, just throw away every other row and every other column. The picture will be half-sized, but who really cares when you're viewing it on a GP32 screen? Do you really want to view a 1280x1024 image in 320x240 increments anyway?

Anyway, the people that do have good viewers haven't taken the time to accomodate the larger JPEGs, and the people that have taken the time to do so aren't working with good decoders.

;)
 
true there hasnt been much support of jpeg viewers semi big files there isnt many jpeg viewers either.

Do you really want to view a 1280x1024 image in 320x240 increments anyway?

i do ( but the size is bigger ) cause then i can scroll the image n see if there is anything bad like if its blured when i took a picture with my digicam.

:ph34r:
 
well, thank you all 8))

i can add any stuff into the COMI
(even viewers)
but it was made for ADIC2002 and i spent only a week or so for its coding...
that's why i wasn't able to make it better.
anyways the source is available 8) http://www.famesoft.ru (downloads)

and.. about a good.. manga viewer...
check www.devrs.com (gba section)
i think it's possible to port the recent viewer or so
 
Flavor posted on Jul 18 2003 said:
Do you really want to view a 1280x1024 image in 320x240 increments anyway?
Yes - my digital camera screen is smaller than the GP32 one. And I don't know a digital camera with a larger screen
 
Last edited by a moderator:
Nitro posted on Jul 18 2003 said:
Digital cameras are not the only things that add extra header information to jpeg images. Photoshop actually adds its own thumbnail information to jpegs when they are saved, and since a lot of images on the web etc are saved in photoshop, the jpeg viewer I'm using won't read them properly.
Since the thumbnail picture comes before the real image, the jpeg reader picks up the thumbnail first and so that's what's processed. I've tried numerious ways of getting it to ignor this extra header information, but I've had no luck so far :(
AFAIK this behavior is part of the EXIF standard that most digital cameras (and apparently Photoshop) support. I'd suggest looking through their docs, as there's probably a standard way of parsing through and dealing with that header data.

Hell, they probably have some small sample apps that'll do the parsing and seperation for you, assuming they aren't too hard to port.
 
Last edited by a moderator:
Back
Top