Old Snagit Images Washed Out/Dithered - macOS High Sierra 10.13 beta 9

  • 2
  • Problem
  • Updated 1 year ago
I'm beta testing macOS High Sierra and just noticed that Snagit Viewer/Editor is not behaving normally. I recognise you may not fully support beta version of the OS but the full release is just around the corner so wanted to raise this in case it's been missed.  Previous snags appear washed out and dithered. New snags taken after the update to High Sierra appear normally.



Snagit file previews in Finder also appear normal in full colour. When opened in Snagit Viewer they revert to washed out.

Photo of chadmhart

chadmhart

  • 1 Post
  • 0 Reply Likes

Posted 1 year ago

  • 2
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 557 Posts
  • 283 Reply Likes
Official Response
Hi Chad,

Apple was not correctly saving image metadata and then was displaying images based off that bad data in 10.12 (and maybe previous versions) when Snagit saves a snagproj. (There were two issues there the writing and the reading). They fixed both those issues in 10.13. But the problem that remains is that snagproj files have the bad metadata and appear washed out.

We are testing out a fix that will hopefully be released in the next week that will fix this for those running 10.12. It will go through your library and fix all the incorrect metadata on your images. Snagit can only do this on 10.12 at the moment. We believe Apple introduced another bug the prevents us from correctly changing that metadata on 10.13. We are currently investigating a way to work around the Apple code for those already on 10.13.

If you make a change to an image that appear washed out in 10.13, it currently saves that washed in image data to the snagproj. So I would refrain from making edits to older captures until we have a fix for 10.13. Any new captures in 10.13 should be fine. (All hope is not lost if it is an important image though, they can still be recovered manually by adjusting the gamma of the image. Let me know if you'd like instructions and I'll post them a bit later.)

We may ask you to try out a build in the near future if you are willing. Thank you for the report! We're on it.
Photo of Luke Griffioen

Luke Griffioen, Employee

  • 704 Posts
  • 173 Reply Likes
Official Response
Following up on this issue, our 4.1.7 update fixes this issue. If you're on version 3 and don't wish to upgrade, we have a small tool you can use to correct your captures. You can download that here, on step 2.