Camtasia 3 for Mac is very "buggy"

  • 1
  • Problem
  • Updated 2 years ago
I've used Camtasia for Mac for years, pretty reliably.  There have been a few bugs here or there, but they were either minor or they got fixed in the next version.
I upgraded to version 3 last week and I feel like I dropped back 2 versions.

Overall, the audio is terrible.  

 • There are noticeable audio thumps at every cut I make on the timeline.
 • Applying the new Noise Removal filter will actually cut off words.
 • If I had a track muted in v2 and I convert the project to v3...there is no way to unmute that track in v3.

So after I edited a 14 minute video in v3....I realized all these bugs.  I contacted tech support and they are working on the biggest issue (audio thumps at cuts).  In the meantime, I decided I'll just drop by project back to 2.10 or 2.9.2 (less buggy imho) and continue editing in that version for the time being.

Nope.

You can't open the file in a prior version...or at least copy/paste the audio.  So, my project is basically stuck on hold. :(

Sorry for venting, but has anyone else experienced any of this?
Photo of myles.debski

myles.debski

  • 6 Posts
  • 0 Reply Likes
  • frustrated

Posted 2 years ago

  • 1
Photo of Paul Middlin

Paul Middlin, Employee

  • 835 Posts
  • 185 Reply Likes
Hey myles, I'm sorry you're having trouble. I'm glad you're in contact with Tech Support, so we can get ahold of your project and see if we can reproduce the same problem here.

In the mean time- you're right, once you've upgraded a project to Camtasia 3, you can't bring it back into Camtasia 2. So, let's see if we can give you some things to try to get this working while we sort out the bug you found.

In the audio where there are cuts, is the media "stitched" together?

If they are stitched, try unstitching. Or the opposite- stitch together clips that aren't (select both, right-click, and choose "Stitch Selected Media"). This might help us figure out the cause. Neither should have audio problems of course, but we're trying to get you a workaround here.
Photo of myles.debski

myles.debski

  • 6 Posts
  • 0 Reply Likes
Hey Paul, thanks for the reply!

I have my clips stitched together...since that use to fix the issue of "popping" in prior Camtasia versions.  But in v3 I get the same result whether they are stitched or not. :/

Was there a big change in the audio support in v3?  Or is it because of the file type change?
Photo of Paul Middlin

Paul Middlin, Employee

  • 835 Posts
  • 185 Reply Likes
Well, that's frustrating. One of our developers mentioned that he'd like to look at your project (it doesn't happen here, of course). 
There were some minor changes, and bigger ones with the noise reduction, but of course it was to make things work better not worse! And while that held true for most, there's clearly something odd here for us to look into.
Photo of myles.debski

myles.debski

  • 6 Posts
  • 0 Reply Likes
He could probably get copies of the files I sent to Aaron S in Tech Support.  Or he can email me and I'd love to provide any files or help on getting the ball rolling towards a resolution.
Photo of davemillman

davemillman

  • 460 Posts
  • 140 Reply Likes
I've created several projects in V3 and not seen the audio thumps issue, despite having over 100 cuts/splits on audio tracks on the timeline. 

My audio is all recorded in Audacity as .wav or .aiff. None is recorded using Camtasia, if that helps debug this.
(Edited)
Photo of myles.debski

myles.debski

  • 6 Posts
  • 0 Reply Likes
Thanks for the feedback Dave!  Ya, my source isn't recored in Camtasia either.  What version of macOS are you running?
Photo of davemillman

davemillman

  • 460 Posts
  • 140 Reply Likes
OSX 10.11.6
Photo of matthew.oldfield

matthew.oldfield

  • 3 Posts
  • 0 Reply Likes
I'm also having a similar problem. When I split audio on the timeline (not stitched, I'm inserting pauses), the audio glitches when it starts again. The only way I've found to fix it is to move the split audio onto another layer, which is annoying and messing. Is this a known issue?