Announcement

Collapse
No announcement yet.

The "Compression Artefacts" issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • seahawk
    replied
    You really do not need to shoot RAW to get acceptable pics for jp. If the camera is set to use the highest quality jpg setting, there is way enough room for editing. The EXIF shows no wrong camera setting, so I would say either noise filter used (which makes no sense at ISO160) or maybe saved more than once after opening the original file.

    Leave a comment:


  • brianw999
    replied
    Originally posted by akerosid View Post
    You didn't, but it was mentioned - here (Pamela's last point!) ... that's what I have been doing.

    Incidentally, I what is the ideal resolution (for a Nikon user) to select. I've always tried to select the finest resolution available (although I never use Raw).
    RAW without a doubt. It is totally lossless and gives you the maximum resolution whereas .jpg will always have a degree of lost detail compression. Combined with a photoshop saving at the maximum 12 and compression should not be a problem.

    Leave a comment:


  • seahawk
    replied
    Did you use noise reduction software?

    Leave a comment:


  • LX-A343
    replied
    Believe me, sharpening before or after resizing does have nil impact on JPG compression. It only results in more or less fine jagged lines, but compression is something different. Do an easy check: if your photos at the size you use to upload here are below 200kb, something is fishy.

    Leave a comment:


  • akerosid
    replied
    Originally posted by pdeboer View Post
    Agree with Gerardo.

    If you are already saving at the highest quality, there are some other possible causes:
    the original is a lower quality (low resolution) to begin with
    you cropped too much on long distance shots
    something in the postprocessing, like sharepening before resizing, check this thread: http://forums.jetphotos.net/showthre...ected-for-soft
    You didn't, but it was mentioned - here (Pamela's last point!) ... that's what I have been doing.

    Incidentally, I what is the ideal resolution (for a Nikon user) to select. I've always tried to select the finest resolution available (although I never use Raw).

    Leave a comment:


  • LX-A343
    replied
    Originally posted by akerosid View Post
    Thanks everyone ... I think the answer lies in sharpening before re-sizing. I will avoid this in future. I only ever save once, so I don't think that's an issue.

    Anyway, many thanks to you all for replying. Good lessons to learn!
    That doesn't have any impact at all on JPG compression!! That's why we dodn't mention it in our list of possible reasons.

    Leave a comment:


  • akerosid
    replied
    Thanks everyone ... I think the answer lies in sharpening before re-sizing. I will avoid this in future. I only ever save once, so I don't think that's an issue.

    Anyway, many thanks to you all for replying. Good lessons to learn!

    Leave a comment:


  • LX-A343
    replied
    Originally posted by pdeboer View Post
    Agree with Gerardo.

    If you are already saving at the highest quality, there are some other possible causes:
    the original is a lower quality (low resolution) to begin with
    you cropped too much on long distance shots
    something in the postprocessing, like sharepening before resizing, check this thread: http://forums.jetphotos.net/showthre...ected-for-soft
    ... or adding to that list:
    - You save at low Image quality in your camera
    - you save multiple times (always do your editing and save only once, at the very end of your post processing
    - in your software "high quality" does not mean "no compression", but just the best out of different settings to save for the internet, but does nevertheless have some compression.

    ... or a mix of some of the mentioned problems.

    Leave a comment:


  • pdeboer
    replied
    Originally posted by LX-A343 View Post
    I see fuzzy lines and compressed background on all these photos, caused by JPG compression.
    Agree with Gerardo.

    If you are already saving at the highest quality, there are some other possible causes:
    the original is a lower quality (low resolution) to begin with
    you cropped too much on long distance shots
    something in the postprocessing, like sharepening before resizing, check this thread: http://forums.jetphotos.net/showthre...ected-for-soft

    Leave a comment:


  • LX-A343
    replied
    I see fuzzy lines and compressed background on all these photos, caused by JPG compression.

    Leave a comment:


  • akerosid
    replied
    Here you go: originally rejected for CMOS Dust spots, so this is the only rejection shown, but (apparently) should also have been rejected for compression:

    http://www.jetphotos.net/viewreject_b.php?id=5290365

    http://www.jetphotos.net/viewreject_b.php?id=5290343

    http://www.jetphotos.net/viewreject_b.php?id=5290353

    http://www.jetphotos.net/viewreject_b.php?id=5290356

    Leave a comment:


  • Alex - Spot-This !
    replied
    Could you please select a few rejections so that we can see better and try to understand where the compression comes from ? Thanks

    Alex

    Leave a comment:


  • akerosid
    started a topic The "Compression Artefacts" issue

    The "Compression Artefacts" issue

    I had some photos rejected on appeal and the screener also suggested that they should have been rejected for compression artefacts too. The screener also suggested that I should "save in a higher quality".

    But I always save in the highest quality available. This rejection reason is coming up increasingly and I would like to put a lid on it.

    When I have done all the bits and bobs - sharpening, cropping, etc etc and then reducing to the acceptable size, I then save the photo under a file name; I am then asked to pick the image quality and I always pick "maximum".

    Is there anything further I should be doing that I am not doing during the preparation process, that would avoid compression artefacts. I have asked (and I know others have asked) this question before, but the reason given last time was different.
Working...
X