SnagIt 4.x for Mac Regressions

  • 1
  • Problem
  • Updated 1 year ago
I find it shocking how much SnagIt 4.x for Mac has regressed.  Copy from clipboard is now completely unreliable (sometimes it works, sometimes it doesn't), and there are (new) bugs in several of the editor tools.  SnagIt 3.x for Mac stops working, I'm required to pay for an "upgrade", and it completely changes several workflow elements and regresses on several key features.  What gives?  I've been a loyal SnagIt customer dating back to 2006 (on Windows) and a Mac customer since the start, but you've got me searching for a new tool.  Very disappointed.
Photo of clwalk

clwalk

  • 1 Post
  • 0 Reply Likes
  • disappointed

Posted 1 year ago

  • 1
Photo of Luke Griffioen

Luke Griffioen, Employee

  • 707 Posts
  • 175 Reply Likes
Hi,

We're so sorry about these frustrations, we would love to know exactly what bugs and workflow changes are causing you trouble. Copy from clipboard is a known issue that we will try to fix as soon as we can. As for the other bugs and workflow changes, if you don't mind listing them here, we can look for workarounds or possible fixes. Again, my sincerest apology about the issues you're seeing.
Photo of Blork

Blork

  • 30 Posts
  • 4 Reply Likes
I agree that Snagit on Mac has become weird and unreliable. Here are a few of the problems I deal with daily:

Random loss of “save.” Sometimes I’m working on a a .snagproj file, and for whatever reason it stops saving. “Save” is greyed out on the File menu, even after I make changes to the file. My only recourse is to “Save as” with the same filename. I’ve lost work because of this when I’ve been saving with Command-S and did not notice that doing so was not actually saving the file (because Save is disabled and there’s no warning). So now I basically have to use the File menu every time I save, to make sure it’s actually saving.

Always reverting to “Autosaved” folder, part 1. When I do a “Save as” it often jumps to the “Autosaved” folder instead of the current folder where the original image is. This happens daily. No, hourly. My workflow is to work on a .snagproj file until all the elements are in place, save it, then “Save as” PNG for use in my documents. (I do this dozens of times a day.) So my .snagproj file is in the "Graphics” folder or whatever, and when I do “Save as” it sends me to the “Autosaved” folder and I have to navigate back to the “Graphics” folder. 

Always reverting to “Autosaved” folder, part 2. When I make a new capture and go to save it for the first time, the file browser jumps to the “Autosave” folder instead of the folder where I’ve been working on other files. This doesn’t happen all the time, but frequently.

Autosave file won’t go away. I understand why there’s an “Autosave” folder and files, but I don’t need to interact with it unless I’m recovering from a mistake. Why then does the following highly annoying behaviour happen EVERY SINGLE TIME? I make a capture. I save it as a .snagproj in my graphics folder. But now I have TWO versions in the image browser at the bottom of the editor; one is in my Graphics folder and one is in the Autosave folder. Both have the same filename. Yo, recipe for disaster! Sometimes I end up mistakenly editing the Autosaved one instead of the “Graphics” one. WTF? There is no reason on earth why I need to see that &@%&$ Autosaved version in the image browser!

Those are the problems I deal with daily. There are some other ones too, but I can’t think of them at the moment. 

One other thing, and this is a feature request not a bug report: since “crop” now requires three clicks to execute, it would be nice if “Crop” were an item on the contextual menu. That way I could drag the handles and just right-click to see “Crop” instead of having to navigate through the menus. Given that “crop” is probably one of the most frequently used tools, I think this would be a really nice feature.
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 557 Posts
  • 283 Reply Likes
Hi Blork,

Thanks for explaining your workflow. Luke is definitely correct in his explanation. Snagit has a Library to help manage content automatically. This is used by a significant portion of our users. We can certainly still improve upon it though.

“So if I then SAVE the .snagproj in my ‘Graphics’ folder, then that's the only ‘real’ version as far as I'm concerned. This is how every application in the world works.”
Some other example apps on macOS that help manage/edit images and video would be Photos, Lightroom, and Photoshop.

Photos and Lightroom work similar to how Snagit currently works; keeping a copy and treating saves as more of an export. Photoshop requires you to manage your own source files (unless you choose to use Adobe Bridge).
We have gone in the direction of keeping a repository of images for you because we’ve continually gotten the feedback that people lose their original source files after they save to PNG.
That said, as Luke was suggesting, we can certainly consider changes to help facilitate your workflow.

There is a preference that is targeted at this type of workflow that we could  bring to Snagit Mac in the future.




By unchecking either of these, new captures come into Snagit unsaved in the tray. Once you save them, there is only that one copy of the snagproj.

Would that support your current organization workflow?
Photo of Blork

Blork

  • 30 Posts
  • 4 Reply Likes
OK, I can see where this is coming from, although it's a stretch to compare Lightroom and Snagit, primarily because Lightroom lets you decide where you want your original files, and you can organize them accordingly, as opposed to Snagit which wants you to keep them all in one bucket. (I've been using Lightroom almost daily for close to a decade, and I admit I never use Snagit's "Library" view because it is useless to me.)

Also, I think photographers using Lightroom to maintain a library of images with separate exports is a different kind of beast than writers and illustrators using Snagit, where screenshots (originals and exports) are tied to other non-Snagit projects, like documents or web sites.

Anyway, yes, that preferences item you show WOULD be useful to me and to many other people I would think. That would probably solve all the mystery around those autosave files.

Thanks for hearing me out, and I'm sorry if I sound extraordinarily cranky about this.
Photo of Blork

Blork

  • 30 Posts
  • 4 Reply Likes
Hey, this is a follow-up with another use case that shows how the default workflow is confusing and annoying to working professionals.

A software developer I work with created some screenshots, including some circles and arrows. I asked him to send me the .snagfile files so I can put the screenshots in a document while still being able to edit those markups.

So he does an export and send me PNGs, with the markups flattened. I go to him and ask again for the .snagproj versions. He tries to export them again, but there is no option to export .snagproj format. He has NO IDEA where the .snagproj files are kept, because like most people, his world does not revolve around using Snagit. He's a casual user, so he doesn't learn the mysteries of the default workflow. He relies on it being intuitive (create a file, save the file where you want to save it). 

So now the developer is poking around in his machine trying to locate the autosave folder. Two weeks from now this will probably happen again, and by then he will have forgotten about the default autosave workflow. Wash, rinse, repeat.
Photo of Luke Griffioen

Luke Griffioen, Employee

  • 707 Posts
  • 175 Reply Likes
Hi Blork,

Sorry about this workflow, I'll pass this feedback along to the team. In the mean time, one easy way to find the snagproj file is to right click the thumbnail in snagit and choose Reveal in Finder. I hope this makes things a little easier in the short term.

Photo of Luke Griffioen

Luke Griffioen, Employee

  • 707 Posts
  • 175 Reply Likes
The ability to export to a snagproj is now available in our latest update, 4.1.7
Photo of Luke Griffioen

Luke Griffioen, Employee

  • 707 Posts
  • 175 Reply Likes
Hi,

The issues with Copy from Clipboard should be fixed in our 4.1.6 update, released today.