Noise Removal Camtasia 2018

When making adjustments to the noise removal in properties, after a couple of adjustments, the program crashes. Not good. I gave up my flawless version 8.4 for a $250 program that now is stopping me from working. Support couldn't help but they are looking into it.

adjustments can be small or large. The project can be a small voice narration or a large file. I don't get a chance to save. Once I adjust, it crashes. Not always on the first adjustment, just on the small tweaks.

Okay, not always affecting a large area then. I would try to save after each individual maneuver until we hear something further. I record and polish my audio externally before I start making clips so saving more often is as much as I can relate to this.

a practice that works for me is to completely finish editing projects with sound, then,as a final step, export all audio as a single WAV file; noise reduction is then accomplished on the exported WAV using Audacity, and the cleaned up file exported as a single WAV; back in the project, all existing audio is silenced, and the new, noise-reduced WAV imported and put on the timeline; this approach eliminates having to work on video and audio editing "separately"

I have never had good results applying Camtasia noise reduction to "sections" of audio, or, for that matter, on separate clips [like narrated trecs] within the same project; but Audacity does an excellent job on the single exported WAV

Intending to play with noise adjustment, I created a new project and just added an mp3 file to it. When I tried to play it, nothing. The program reacts otherwise, but will not play. Forgiveness is a virtue, but CS 2018 is running out of indulgences. I have worked for software companies, and I know the pressures of getting something out so you can collect revenues. Releasing buggy software may be the last thing you do.

I have
actually worked for software companies that had verification suites and tested
their software. I will also tell you that it is more difficult to do so than
writing the original package perhaps by a factor of 3 or 4. As you allude, most
companies do perfunctory testing that is non-exhaustive and only meant to
uncover major flaws. That’s show business. The fact is that people tolerate it
because 80% functionality is enough for most users.

I'm a technical writer and former Software Q/A Engineer and I don't buy this dismissive attitude toward bugs at all. While it's impossible to test every hardware/software scenario, it is imperative that all functions of a product be tested before it is released. ﻿There is no excuse for not doing this. There will still be bugs, but they can at least be documented in the release notes and if necessary, buggy code can be reversed or disabled until a maintenance release comes out.

From my perspective, it's pretty obvious that CS2018 was rushed to market with insufficient user input and Q/A testing, as the issues raised on this forum clearly show that it's a buggy mess that removed or adversely changed features that the user base liked, with no warning. This is a serious failure on Techsmith's part that needs to be rectified, not blown off as "that's software". Smart, customer-oriented companies don't do that.

While I have no idea how Techsmith's new product team operates, this looks a lot like what happens when you let engineers define how a product works, rather than the usability team.

Techsmith has told me that it is a documented issue with development and will be fixed in a maintenance release. That is what they told us when many of our company moved to version 9. The crashing is totally unacceptable and shows that user testing was not done. Is there another comparable product out there?