What we're losing with Snagit 11 upgrade

  • 13
  • Question
  • Updated 4 years ago
  • Answered
According to the Snagit version history the following are part of the upgrade to 11

* Restricted the use of GIF and 256-color image files to only during opening and saving.
* Removed support for several file formats including .msp, .cal, .pcx, .raw, etc.
* Removed the ability to capture full screen DOS windows.
* Removed the ability to capture icons from .exe and .dll files.
* Removed the "Create Web Page" feature.
* Removed the Web Capture mode.
* Removed the ability to capture from DirectX applications.
* Removed various region capture options including capturing triangle region, a rounded rectangle region, an ellipse region, etc.

I'm used to upgrades adding but not removing. I can't find an explanation but would like to understand the reasoning before I decide whether to upgrade.

Photo of Catherine Kubitschek

Catherine Kubitschek

  • 2 Posts
  • 0 Reply Likes

Posted 8 years ago

  • 13
Photo of Geoff Bomford

Geoff Bomford

  • 1 Post
  • 4 Reply Likes
I won't be upgrading, I've never seen an upgrade with fewer features before!
Photo of raylasky12


  • 11 Posts
  • 9 Reply Likes
Ive Not up graded my TechSmith products twice now...and have left my real money on the table...because of the poor choices in removing features. This kind of mindset and behavior at TechSmith needs to be "removed". It creates bad will in a customer centric marketplace. It isnt cute or smart...or appreciated by your money paying customers. I love your products...they are brilliant...but whoever fosters this attitude at Techsmith (Even the CEF/CFO)...it need to stop. Your research is way off.
Photo of cwoolfork


  • 7 Posts
  • 7 Reply Likes
Well said!...
Photo of atty


  • 7 Posts
  • 5 Reply Likes
Once again Tiffany, I realize you are saddled with the burden of advancing management's "excuses" and are not an author of the "canned scripts".

That having been said, this constant reference to "Our user data....." is apparently in error judging from the responses that you have received on this forum. It is pretty obvious that "our" data tells us, and should tell your management, that this little maneuver is not in favor with the end users. Your "workarounds" are not a substitute for what end users feel is a major short change in functionality. I understand the need for software engineers, but marketing needs to realize that if customers feel that the package has been shorted, and to add insult to injury, marketed as an "upgrade", they are naturally a little upset.

"Our data" is only as good as the people, with their varying perspectives, interpret it. This rather substantial reaction (just on this forum) should tell somebody that it might be time to re-think.
Photo of AnySupport-Eliz


  • 1 Post
  • 3 Reply Likes
I've been following this thread and just wanted to add two cents as this whole conversation has me intrigued..

I use SnagIt on both a PC and a Mac and have for a couple of years now. I primarily use the PC version, and admittedly most of my usage is pretty simplistic. Clipping screens for later notation or sharing. Nothing too complicated.

While I cannot think of a situation yet where I've been directly (or at least noticeably) impacted by the features removal, I am also curious about the reasoning for removing functionality.

First cent:
If something, perhaps in the OS, hasn't changed that would make a continued availability or functionality impossible, I can't quite come up with a case against (or for the harm of) leaving the existing feature in, even if it is was perhaps marked as a 'legacy' feature and that it would no longer be enhanced or developed further.. but kept in place at least.
It seems a poor method of software development in something with widespread use as a full product and not just coming out of some initial beta testing phase.

  • Was there a limitation or restriction of leaving these features in at all?

  • Or was it more simply (and generally stated) a cutting of the '10 least used' features to keep future development more streamlined? (separate from the debate of how the criteria was determined and gathered to make these decisions)

Second cent: I'm curious mostly...
  • Is the data gathered only from people who choose to be included in the User Design Initiative?

  • There may be people who choose not be included for personal excuses or perhaps can't for perhaps business policies.
    Is there an understanding of the breakdown of people included in the Initiative vs not?

  • How are the usage and voices heard then from the group that aren't/can't be involved in this method?

Photo of cwoolfork


  • 7 Posts
  • 7 Reply Likes
Good questions!!!...Now, let us see if Tiffany Wood or someone else at Techsmith is willing to answer them!
Photo of Manny Carvalho

Manny Carvalho, Champion

  • 1171 Posts
  • 185 Reply Likes
I'm not from TechSmith but let me talk to your first point about removing features.

Software that has features that hardly anyone uses runs into the danger of becoming bloated and consequently causes performance to suffer. It's certainly a fine line to draw as to what to keep and what to discard but when usability data shows that only a small percentage uses a certain feature than certainly one has to wonder why that feature needs to be kept in.

It's the conundrum of maintaining the product performing well [and certainly good coding goes along with that] versus just keeping features around.

Unfortunately, v11 saw a cleanup of many of these features so it kind of hit all at once. If you were one that depended on that feature then, of course, none of this matters because it was useful to you. If that's the case then making a good argument as to why it is useful and getting others to agree goes a long way in getting those features returned. After all TechSmith removed these things because they were looking at their user data and that does mean they are responsive to users.

That's my two cents worth.
Photo of NZ


  • 28 Posts
  • 8 Reply Likes
As elizB said, not all of us are allowed to partake in the user data sharing process (company policy), and some of the features removed are used very often, which makes Snag-it now much less usefull. And then I have to pay for that too?
Photo of Public2


  • 8 Posts
  • 2 Reply Likes
Excellent questions.

This conversation is no longer open for comments or replies.