Wile E
Power User
- Joined
- Oct 1, 2006
- Messages
- 24,318 (3.79/day)
System Name | The ClusterF**k |
---|---|
Processor | 980X @ 4Ghz |
Motherboard | Gigabyte GA-EX58-UD5 BIOS F12 |
Cooling | MCR-320, DDC-1 pump w/Bitspower res top (1/2" fittings), Koolance CPU-360 |
Memory | 3x2GB Mushkin Redlines 1600Mhz 6-8-6-24 1T |
Video Card(s) | Evga GTX 580 |
Storage | Corsair Neutron GTX 240GB, 2xSeagate 320GB RAID0; 2xSeagate 3TB; 2xSamsung 2TB; Samsung 1.5TB |
Display(s) | HP LP2475w 24" 1920x1200 IPS |
Case | Technofront Bench Station |
Audio Device(s) | Auzentech X-Fi Forte into Onkyo SR606 and Polk TSi200's + RM6750 |
Power Supply | ENERMAX Galaxy EVO EGX1250EWT 1250W |
Software | Win7 Ultimate N x64, OSX 10.8.4 |
I completely disagree with your assessment what png and jpeg are best for. I think png is the best format for comparisons. Jpeg is great for just showing stuff without the need for absolute accuracy.To add to that...
GIF = best for images with 256 colors or less.
JPEG = best for images with lots of variations (virtually all digital camera pictures and game screenshots).
PNG = best for images with large areas of a solid color (like a screenshot of this website).
You should always be able to get a 1920x1200 picture under the 2 MiB limit with the right format. I've only encountered problems with size when dealing with 5+ megapixel pictures from digital cameras. In which event, I either crop or scale the image down and save as JPG (PNG generally won't work well for something photographed) and then they usually come in under 1 MiB.
Yes, it's more work to treat images right but it's also easier on everyone else (bandwidth, hosting server, users viewing it, etc.) to do so.
As such, I think the 2 MiB limit is fine for the time being. Yes, it can be a bit annoying but it is for the better.
That said, there have been some great suggestions in this thread on how to maintain accuracy while achieving good compression.
EDIT: And I forgot to ask Newtekie a question: What software do you use to compare the photos?