Camtasia, crash crash and crash.

  • 6
  • Problem
  • Updated 6 years ago
So, Camtasia decides that it likes to crash a lot. I find this very frustrating and annoying, especially when you are having fun editing your video, then it crashes from nothing. It gives you an error saying camtasia has stopped working, and says it needs to be closed. I think Camtasia needs to have this fixed, as well as implementing some sort of auto-save every configurable time, so that you dont end up frustrated after lots of work.
Photo of Jadia

Jadia

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 6 years ago

  • 6
Photo of kayakman

kayakman, Champion

  • 7335 Posts
  • 2487 Reply Likes
Camtasia has a default auto-save that fires every 2 minutes; you can change the time period using the Tools|Options menu

personally, I execute a manual save after every important edit, while using a 5 minute auto-save value

if you work with large projects, best practice is to break them into small segments [use the Library], edit them separately, then re-combine them at end, and then produce; large projects can be demanding on even powerful systems, yet Editor performance is superior when working with short "snippet" projects


Photo of John Hall

John Hall

  • 71 Posts
  • 18 Reply Likes
It's actually gone beyond crazy. It happens with every project I have at the most inopportune times. This is consistent with various media type and resolutions. I can't believe that Techsmith keeps providing bandaid solutions. There's obviously some huge memory leaks or some really bad code in there. 

I love Camtasia - or used to. The interface and purported functionality is exactly what I need. However, this just gets crazy after a while. Any size project, no common variables (three different Windows machines all running Windows 8 64-bit) and each time the suggestion is send in the project. 

On occasion, it actually has saved a backup that is useful. I also save after every edit (not sure why that's an acceptable solution as many times that's exactly when it crashes, when I'm doing a manual save). 

I know nothing will come of this rant any more than others, but I have been working with Screenflow lately to get around the loss of production. I'm not as comfortable with a Mac as I am with Windows, but I'm becoming so and it's certainly worth the effort to start switching to a workflow that doesn't require recreating work all day long.

Just very frustrating. I'm sure it's difficult software to develop but it's no longer a real useful tool, imho.
(Edited)
Photo of Dave O'Rourke

Dave O'Rourke, Senior Software Engineer

  • 1444 Posts
  • 420 Reply Likes
John,

What you're experiencing is definitely not normal behavior, and not something we've seen with the current release (version 8.3.0, as of today).  The best way for us to help is for you to open a ticket with our TechSupport staff by visiting http://support.techsmith.com.  We ask for the project so that we can try to reproduce the issue on our end.  If we can reproduce the issue, then this helps us toward a fix.  If we can't reproduce the issue, then there are other methods we can use to try to narrow in on the root cause, such as collecting a crash dump or process monitor log from your machine.  It may take some back and forth, but we'd certainly like to try.  If you're willing, please visit the support link and we'll get going on the troubleshooting process.
Photo of John Hall

John Hall

  • 71 Posts
  • 18 Reply Likes
I'd be glad to send logs again. I'll try to get 4 or 5 projects to crash to see if there's something in common. Before, I've disabled GPU acceleration and other items suggested. I've changed the temp file location and it's just so consistent across machines that it's hard to believe this isn't more prevalent. 

Edit: Unless, of course, there's something consistently installed on all three machines (like an anti-virus program) that would account for it occuring across locations so frequently.
(Edited)
Photo of John Hall

John Hall

  • 71 Posts
  • 18 Reply Likes
I have found one thing today that significantly reduces the crashing for me! I, like I'm sure a lot of people, have developed a rhythm of editing that includes previewing, lining up the playhead, deleting a section of audio or video, slide back on the timeline and preview again to get a sense of the timing. I do this very quickly using my thumb on the spacebar to restart the clip for a confirming preview. I have found that if I wait until the preview image at the top right of the screen, the large image, loses focus (or whatever it’s doing, you can see the bounding box change) before starting the preview again, I have reduced the kind of crashes I was getting by about 80% today (yes, I did a count for 2 hours – it’s actually closer to 76% but I tend toward hyperbole). If I don’t wait for the bounding box to lose focus, I have approximately a 1 in 10 chance of the program crashing.

If others have tips that help the situation, please share. Maybe with enough data points, something will start to add up to the engineers about what’s being buffered or something during the time of most crashes people experience. I don’t claim this is anything but one data point that I’m excited about.

BTW, I had experimented with enabling/disabling GPU acceleration and that has not made a difference for me so far.

PS: Unfortunately my luck did not hold up while adding captions the following day. Constant crashes. Too bad.

(Edited)

This conversation is no longer open for comments or replies.