Do Developers Really Update? Missing Content from previous Releases!

  • 1
  • Problem
  • Updated 3 years ago
My original concern was regarding the removal of the Audible Alert from SnagIt. It seems that during the rehash for v13 the Devs "forgot" about this function, leaving me the option of going without it, or uninstalling v13 and re-installing v12. I'm currently using V12

I brought this concern up with Tech Support, and their response was to post it here.

Now I'm left wondering just what I spent my money on. Then after looking through the Forums to see if others had the same complaint, it seems my gripe is just one stone in a wall of frustration.

So, do Developers really update? Where's the missing content from previous releases!

It seems to be a common theme (just look through these Forums) that when the Techsmith Developers decide to 'update' a program, inevitably a much loved feature is butchered or removed.

Just like Vehicle Manufacturers, the 'new' versions always look pretty, and sometimes the ergonomics are much improved. But under the hood it seems some drastic changes are sometimes made in the name of "updating', to the detriment of the programs' and their ability to perform up to previous levels, not to mention being unable to exceed them.

Now, not to be too picky...but my definition of 'updating' is similar to the dictionary definition:

verb (used with object), updated, updating.

1. to bring (a book, figures, or the like) up to date as by adding new information or making corrections : to update a science textbook.

2. Computers. to incorporate new or more accurate information in (a database, program, procedure, etc.).

3. to bring (a person, organization, etc.) up to date on a particular subject: The magazine article will update you on the international situation.


4. an act or instance of updating: to make an update in a financial ledger.

5. information or data used in updating.

6. an updated version, model, or the like.

I will not go into details regarding just how much has been downgraded or removed from our favorite Techsmith programs, simply because that information is freely available in these Forums.

  • that someone from Techsmith will read this post,
  • take a copy of it to the next meeting with them, and
  • pass it on to someone who cares enough to ask the Dev's the same bloody question:

What's going on?

Photo of strabor


  • 2 Posts
  • 4 Reply Likes
  • very, VERY disappointed!

Posted 3 years ago

  • 1
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 599 Posts
  • 325 Reply Likes
Hi strabor,

Some background
Part of our update to Snagit 13 was to change the UI in a way to be more understandable to new and existing users. Our goal was to balance the power with Snagit with how approachable it is. Because we want it to be powerful and help out customer be efficient, but also we need to introduce people to new functionality that features that already exist. Which was definitely a problem in previous versions.

All our analytics show an increase in tool usage in Snagit Editor and the Capture Window. Which is fantastic. We’ve got more people than ever using the tools we’ve built to be more effective at their jobs.

Specific reasoning
We never want to remove a function, because it can be really painful for people using it. But the audible noise at capture hotkey and capture complete were functions that we'd seen low usage of. As a part of making Snagit more approachable we removed it as an option. (We also are able to deliver improvements faster as if we remove functions that aren't used because that's more that we have to test, but that didn't come into play as much in this particular case)

I am curious as to why the noise at capture was important to you. Was it for a specific purpose? Waiting on a long scrolling capture? Or was it a nice affirmation that everything went well?