Originally posted by graphicgr8s Anytime you save a jpeg you lose. JPGS are considered a "lossy" file format because of the way it compresses an image. How much it looses depends on the photo.
Professionally, in my work environment I never save a jpeg back to itself. It will always get saved as a tif with no compression if I feel I may need to work on it later. If I give it to a client I will keep the tif and save as a new jpeg.
You are right. It is so. However, the question is, if you'd only change the exif data of a picture and then save it, would the program regenerate the JPG data (and degenerate the picture some more) or would it not touch the picture data?
Marc Sabatella is absolutely right that any proper programmer would avoid the regen. And I believe that Marc very well understands technology in a wide range of aspects, reading his posts....
However, my argument is that many object oriented code these days is written as such that the guys using these objects go for convenience instead of efficiency.
No offence Marc, but where I live, they do not teach students proper programming anymore. Most of them have no clue what their compiler actually is doing....
The best support for my argument comes from our todays Windows, Office etc etc.
10 years ago my computers were 20 times as slow, but my todays superduper hardware boots and reacts slower and slower than the stuff we worked with then.
It's all about structural programming and supportability, not about code or program efficiency.
Try it and be sure.
- Bert