LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Mobile (https://www.linuxquestions.org/questions/linux-mobile-81/)
-   -   Picture formats? (https://www.linuxquestions.org/questions/linux-mobile-81/picture-formats-4175473744/)

business_kid 08-17-2013 03:01 PM

Picture formats?
 
Samsung Galaxy Note on Android-4.1.2, a.k.a "Jelly bean" What an unattractive title.

What picture formats will it take? I copied on a .tif and a .png and it doesn't see one and won't open the other. .tif was pushing it, but png should surely be ok.

Doc CPU 08-17-2013 03:53 PM

Hi there,

Quote:

Originally Posted by business_kid (Post 5011048)
Samsung Galaxy Note on Android-4.1.2, a.k.a "Jelly bean" What an unattractive title.

yea, alright ... I agree that Jelly Bean sounds a bit awkward, has the connotation of "slick toad".

Quote:

Originally Posted by business_kid (Post 5011048)
What picture formats will it take?

That question was a bit ambiguous. On first reading, I thought you were thinking about what image format the integrated camera would produce, but then I realized you probably tried to copy some image files to the device to see which it would display properly.

Quote:

Originally Posted by business_kid (Post 5011048)
I copied on a .tif and a .png and it doesn't see one and won't open the other. .tif was pushing it, but png should surely be ok.

Indeed, TIFF is a bit exotic. Even with desktop software that claims to "work with TIFF", it is a lucky game whether it will really work, because there are so many TIFF variants around. On the other hand, PNG is a very widespread standard, and I would expect any halfway recent appliance or software to display PNG images properly. If the Galaxy doesn't, did you face it with an exceptionally difficult task, like PNG with alpha-transparency or PNG in CMYK color space?

[X] Doc CPU

business_kid 08-18-2013 08:09 AM

Here, Jelly beans are cheap nasty sweets(candy in American) that are sold to children. They are loaded with sugar, and highly poisoned with poisonous colours (Azo dyes) to make kids hyperactive.

Dunno about the images. They are someone else's images with their own rgb built in.. The reason to use tiff is that you can get dot for dot whereas when you use a compressed format, dots are grouped. Looks like I'll have to go jpeg. But this is some sort of compressed tiff :-/.

Doc CPU 08-18-2013 09:03 AM

Hi there,

Quote:

Originally Posted by business_kid (Post 5011352)
Here, Jelly beans are cheap nasty sweets(candy in American) that are sold to children. They are loaded with sugar, and highly poisoned with poisonous colours (Azo dyes) to make kids hyperactive.

oh, I see. Like gum bears, but in different shapes?

Quote:

Originally Posted by business_kid (Post 5011352)
The reason to use tiff is that you can get dot for dot whereas when you use a compressed format, dots are grouped.

Erm, yes ... why would that be a problem? I mean, image compression is okay for me as long as it still looks good.

After all, there are two different classes of image compression:

Lossless compression reduces the amount of data to be stored or transferred, but the original image data can be reconstructed precisely to the last bit from the compressed data, that is, the image data before and after compression is exactly identical. Both TIFF and PNG fall into this category. PNG achieves a compression factor of about 3..5 for photographs.

Lossy compression deliberately drops fine details to further improve the compression ratio: The more you choose to compress the data, the more quality you lose. JPEG is a typical example for that (or MPEG in video/audio). If you save an image as JPEG and then open it again, you can see that it has become blurred and/or frizzy around sharp edges, and smooth color gradients may get slightly terraced. At a decent quality, JPEG achieves a compression ratio of 10..30.

Quote:

Originally Posted by business_kid (Post 5011352)
Looks like I'll have to go jpeg. But this is some sort of compressed tiff :-/.

Well, JPEG is a lossy compression (not a lousy one), TIFF uses a lossless one. Usually, photographs still look good as JPEG, if you don't push the compression ratio sky high.
If possible, I'd go for PNG.

[X] Doc CPU

John VV 08-18-2013 10:08 AM

png's should not be a problem .However .tiff or .tif might
png's are what i use most often if it is NOT raw data or data that NEEDS to be in 16 bit or 32 bit
BUT some software might have a problem if the png is 16 bit/layer and not 8 bit/layer


A tif image can be a single layer 8 bit image or a 16 bit Unsigned lsb/msb or a 32 bit floating point single layer
or
a 3 layer 96 bit ( 3 32 bit layers)

mostly the tiff format is used for 32bit imaging data ( black and white images )

business_kid 08-18-2013 01:07 PM

Quote:

:
Originally Posted by business_kid View Post
The reason to use tiff is that you can get dot for dot whereas when you use a compressed format, dots are grouped.
Erm, yes ... why would that be a problem? I mean, image compression is okay for me as long as it still looks good.
THIS tiff definitely seems to have been subjected to lossy compression at some stage. Maybe the resolution is just poor. I spent a while in Digital Archiving, handling 500G discs full of 400-900MB images of ancient documents. I am suspicious of a tiff that should be 100MB+ but is only about 8MB. Even it's uncompressed size of 22MB is not inspiring. All this doesn't get me going.

PNG should work (usually) - Thanks for that. Mine does not.
Tiff - no.
I'll try a .gif, then mark this thread solved.

John VV 08-18-2013 02:16 PM

seeing as you "copied" it
Are the file permissions correct ?

is it owned by you and in the users group ?

or


is it the newer "bigtiff" format ?
or a "GEOTiff" -- used by GIS software

or compressed using LZW , zip ,deflate, jpg, ccitffax4
stripped or tiled
single or pyramid

it might be the size of the image
slightly large images , say 25 meg + might not have thumbnails made
mind you my tiff images tend to be 4 GIG+

can you see a jpg or a windows bmp ( or the better ppm / pgm )

have you tried deleting the file extension and let the os figure out the image format

Doc CPU 08-18-2013 02:21 PM

Hi there,

Quote:

Originally Posted by business_kid (Post 5011461)
I am suspicious of a tiff that should be 100MB+ but is only about 8MB. Even it's uncompressed size of 22MB is not inspiring.

then you must have huge images - huge in terms of resolution. 22MB sounds like roughly 7MPix, 24bit uncompressed; 100MB would be more than 30MPix. Okay, 15MPix at 48bit. What camera produces images like that?

Quote:

Originally Posted by business_kid (Post 5011461)
I'll try a .gif, then mark this thread solved.

GIF won't satisfy you. It allows for only 256 colors or gray shades, and not more than 4096px of height and width.

[X] Doc CPU

business_kid 08-19-2013 04:15 AM

@JohnVV:
I copied it to the sdcard because bluetooth was acting up (too many suspends & no reboot) but it's cleared out now, so I can't check. I never had issues before with similar files.

I can get very little image data. Opening it in Gimp reveals basically nothing (Image/properties). No thumbnail. It has it's own rgb pallette. No specs at all. Ditto the png. File returns nothing. The best I get is with ImageMagick's 'identify' which tells me they're both 8 bit.

@Doc CPU: Modern Electronic archiving equipment uses sunlight bulbs and the most exotic camera sensors in existence. These
http://1641.tcd.ie (You can see a section of an old page in the opening screen) were imaged with older stuff, giving the 400-900MB images I mentioned. That was the project I was involved with. What you get to see on the site is jpegs. Tiffs are supplied as well as the jpegs. The tiffs are the archival copy, and jpegs are made & remade if needed from the tiffs. If the software was better, pngs would have been used. Some of the top cameras are up to (as of 5 years ago) 40k pixels on the sensor = 8000x5000, or something like that. Larger ones were coming. The pages were typically 45-60cm x 25-50cm. No such thing as A4 in 1641!

Thanks for the reminder on .gifs. that allows me to mark this solved.

Doc CPU 08-19-2013 04:47 AM

Hi there,

Quote:

Originally Posted by business_kid (Post 5011754)
Modern Electronic archiving equipment uses sunlight bulbs and the most exotic camera sensors in existence. These http://1641.tcd.ie (You can see a section of an old page in the opening screen) were imaged with older stuff, ...

oh, I see, that's a very specialized thing. I was under the impression that we were talking about regular digital cameras, the kind that "everyone" has nowadays. Then I have to withdraw all I said about "huge" images, because I can't assess it due to lack of expert knowledge.

However, you could've given a hint on the kind of imaging you're dealing with in your opening post.

Quote:

Originally Posted by business_kid (Post 5011754)
Some of the top cameras are up to (as of 5 years ago) 40k pixels on the sensor = 8000x5000, or something like that.

That's off by a factor of 1000. You obviously mean 40M pixels, and that's ... wow! :-)
Considering these image sizes, I second JohnVV's suggestion that it could be the sheer size (whether it's file size or number of pixels) which stops the Samsung device from displaying these images.

[X] Doc CPU

business_kid 08-19-2013 06:13 AM

I saw the sensor they use and it was bigger than a 35mm negative. Some crazy dpi. There's no point in me playing with a tif if it has been jpeg'ed at some stage. I can't get any real info on the pictures, which is annoying. Even ImageMagick's identify is very tight lipped. I have a jpg on the phone which serves my purpose, and I'll make another and put that beside it. I have a 16G external sdcard, so I can do that.

Thanks for all your help guys. I've marked this one solved. End of inquiries.

EDIT: BTW, I don't have that stuff on the phone, it's another source entirely, which it is outside forum rules to elaborate on. Not porn, either!

business_kid 08-19-2013 10:06 AM

I created a superior png from the tif. ImageMagick even barfed on the conversion "Tags and labels are rubbish: ignoring them" but it made me something that displays, which is all that I need.


All times are GMT -5. The time now is 02:25 AM.