Re: Photo software authors
- From: Eric Grange <egrangeNO@xxxxxxxxxxxxxxx>
- Date: Wed, 20 Dec 2006 08:21:48 +0100
Photoprocessing software misses out because RAW files are 12-bit and
JPEG files are 8-bit. Loads of data simply tossed away there.
I think what we need are programs that will batch process [...]
Existing software can already do that, even the cheap PaintShopPro supports 16bit editing nowadays :)
You can then use scripts (recorded or edited) for the batch processing.
Allow the file to be saved as TIFF (both varieties), JPEG (both
varieties), Bitmap and Microsoft's new picture format.
Personally I would rather they ditch TIFF entirely (what a waste of time of a format IMO), the only places I've seen it "used" was in the editing world, and there usually by people that had no understanding of what resolution or dpi of a picture really are, when they didn't blindly equate filesize with picture resolution. It's kinda weird, given that's supposed to be their job, but it explains a lot of the low quality images that still end up printed.
Finally release it on all platforms - Windows, OSX, Linux.
Lightroom? or with a less cute UI The Gimp can cover quite a bit of what you listed.
I don't see cutting and pasting parts of the image as being good. Many
pros - particularly newpaper pros don't want to "edit" the image -
There was a website I bumped sometime ago that made the round of the well publicized press images, hunting for discrepancies, misuses and and blatant editing. Should have bookmarked it.
There were lots of pictures in there that you must have seen, that were reused all around the world that yet beared traces of manipulations, faint or obvious, some only visible by comparing the "same" image in different medias.
> merely bring up the good points and minimise the bad.
That's the definition of "editing" in my book :)
- Prev by Date: Re: Use a C++ library within Delphi
- Next by Date: Re: About VS C++
- Previous by thread: Re: Photo software authors
- Next by thread: Python & Delphi Mthology