Camtasia 8 Crashing is becoming very frustrating!

  • 1
  • Problem
  • Updated 3 years ago
Ok recordings and sound is not my forte, but editing recordings is a part of my job. We have 2 hour training sessions which I have to edit and clean up, There are lots of small minute cuts in every minute of a recording, but it I think I can go one minute without saving I end up with a rash and have to redo it. Having to save after every single cut is becoming very time consuming.

So my question is, are there some general settings I could look at that may fix this problem, I am working on Windows 8 64bit, is the fact that Camtasia is 32 bit the cause of this? Please help, I have been on a two hour recording for 3 days now (admittedly not full time) Any Suggestions?
Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes
  • beyond frustrated!

Posted 4 years ago

  • 1
Photo of Joe Morgan

Joe Morgan

  • 7546 Posts
  • 4136 Reply Likes
The fact that Camtasia is still  32 bits is a big part of the problem. 2 hour recordings are a lot for Camtasia to process.
When I'm working on a intense project I open the Taskmanager and keep an eye on RAM usage. When RAM usage gets close to 2,000 MB I save my project. See Image, Click to Enlarge.



Then, you need to close Camtasia completely and relaunch the program. When you reload the project it will free up a lot of RAM in most cases. An example of the usage drop between the above screen shot and
after relaunch is shown below.



I use a lot of video editing programs. None of them Dump the accumulated RAM memory usage that builds up during normal editing processes. That's why a complete restart is required.

I also run Adobes Premier Pro a lot. It's a 64 bit program and I'm currently running 16 GB of RAM. Depending on what I'm doing RAM usage can accumulate pretty fast. At around 12GB Premiere Pro will start to get sluggish and I know it's time for a restart. Monitoring RAM usage is not as critical as with Camtasia because there's a lot of overhead available. It usually takes an intense project and at least a couple of hours editing to reach that point.

This technique will not work for all projects but it will help you get through most of them.

There are more laborious techniques to produce small sections of your video to AVI and string the productions together for a final render. Save sections to the library. Things of this nature.

kayakman knows how to do this better than anyone else in this forum. I was looking for a link to his advice and didn't have much luck. Perhaps he will jump in here.

For myself, I find needing to jump through that many hoops a bit ridiculous and incredibly unproductive. But his techniques do work.

 64bit  Camtasia is coming. Until then Camtasia is what it is. 

Regards, Joe
Photo of kayakman

kayakman, Champion

  • 7221 Posts
  • 2412 Reply Likes
The fact that ... "There are lots of small minute cuts in every minute of a recording" is what is probably causing your issues ...

"is the fact that Camtasia is 32 bit the cause of this" ... no

your 2 hour recording with many edits is creating a project file that is so complex that it is affecting editor performance, and likely causing CS to run out of process memory

suggest you simplify by "divide and conquer"

perhaps watch this tutorial ...

How To Build Out And Produce Very Large Projects
Photo of kayakman

kayakman, Champion

  • 7221 Posts
  • 2412 Reply Likes
the above tutorial location has changed ...

http://www.screencast.com/t/PdRvG5hN7 
Photo of Marsha H

Marsha H

  • 21 Posts
  • 3 Reply Likes
Hi yvonne,
I had the same experience and the suggestion kayakman gave is exactly the solution I used. I've never worked with a recording that was 2 hrs. in length but my file size paired with the number of edits and visual effects I added made it unbearable.

RAM is a big culprit. Since I've upgraded my machine, I haven't had any of these problems. But that is most likely not a solution for you at this point.

The only thing I was able to do on my previous machine was to divide my project into smaller sub-projects and then combine the produced results together into a master project. That was the only thing that worked and saved my sanity.

Good luck.
Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes

Hi Marsha and Kayakman

As I said, sound is not really my forte but that's part of what I need to do We do mainly 2 hour training webinars but I have done 4 hour edits before. It very much depends on the presenter and how many erss and ahhhs and stumbles I need to  cut out, some has irritating habits of saying "right" all the time... So as you can see , literally all I am editing is cleaning up, nothing added nothing fancy, some recordings go swimmingly and others are just a pain in the butt "

and if I have to cut out three ermms and ahhs without saving it crashes, But earlier I did send through an error report, which was the first time I received it

In terms of RAM, I have 16gig f Ram, i7Core and 2,4GHz, basically not too shabby, because I also work with Corel and I know how much it depends on the temp folder I clear out the temp folder every time I am about to start editing a recording

will have a look at the tuttial before starting my next one


Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes
Joe thanks I missed your input earlier
I think your advise sounds good, What I have noticed is that This particular file I was working with the project file was more than double than most of my other projects, the final Project file was over 5Mbs. This is usually a very good presenter but this one was a duzi to work through.... I will look at Kayakmans suggestion and try it
Photo of Joe Morgan

Joe Morgan

  • 7546 Posts
  • 4136 Reply Likes
yvonne,
That is the entire point of saving the project and closing and reopening Camtasia often.

Camtasia crashes when utilizing as little as 2GB of RAM or after reaching  higher levels, a crash is usually unavoidable at 2.5GB or shortly thereafter.
Everytime you edit out a Umm, Ahh, Opps, etc you increase overall RAM usage. That's also why 32 bit Camtasia is so prone to crashing.
When you restart Camtasia all that RAM usage is freed back up. It's really that simple and it sounds like it could serve you well.

As I stated above, even 64 bit programs need restarting when they are consuming most of the RAM memory available on your system. 


To be honest, kayakman's time consuming workarounds should become an unnecessary thing of the past after Camtasia 9 is released. "Here's where it's acceptable to cross your fingers for luck"lol
Unless you have a low powered computer that isn't well suited for video editing. Then it's the under powered computers fault more than the program being used.

Anybody that edits videos using Camtasia fairly regularly as a part of their job probably owes it to the company they work for and themselves to update to Camtasia 9 when it's released.

I don't work for Camtasia or take recommending the upgrade to Camtasia 9 lightly. It's just common sense advice that will save everyone time in the long run. The net result is saving money in the long run as well. Not to mention a lot of frustration in many cases.

Regards, Joe
(Edited)
Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes
I think I may have overcome part of the problem, My C drive partition  is not very big and I spotted this morning was that I did not have my D Drive set as additional Virtual Memory, Did That,

The file I worked on last week refused to render (The project file was in excess of 5 Meg - which is the largest I ever got, think the project file may have gotten corrupted) Anyways,  took another copy of the same recording  and also followed Joes advise and kept an eye on my task manager. and also closed and reopened the project every 15 mins or so. I am now more than half way and have not yet gone over about 800kb.... and only One time out/crash.... will see how the rest of the time goes, this is normally where it gets tricky - I do think the Virtual Memory has an effect...
Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes

Hi all

I managed to get through the recording with only two small crashes in a 2 hour session, I do believe that somehow the recording from Friday got corrupted somehow as a result of all the crashes

For what it is worth, for everyone that is experiencing the same problems with crashing ( I realize we all have different kind of projects, but in the end the logic is still the same) This is where I am in terms of problem solving this little pain in the butt and over the next few days I will test my theory

  1. Check Virtual Memory and set to best you can do on all hard drives

  2. Have a clean restart of the computer before starting on a project

  3. Keep multitasking to the minimum

  4. Save often, keep eye on task manager and stay below 2 MB in (Camtasia Process manager)

  5. Save and close camtasia (in my case every 15 minutes in a 2 hour recording) or as necessary according to the processing % in 4 above – I found that my closing every 15 minutes I stayed below 1 meg most of the time

  6. Towards the end of my recording (Last 1⁄2 hour) the processing % creeped up to about 1.2 MB, I then saved and closed every 10 minutes

  7. I also felt that yesterday by working the program too hard and resulting in crashes can corrupt my file, resulting in an abnormal Project file, which I was unable to render. (The diffs between the corrupted file and the one today was 5+ meg to 2.4 Meg today)

So armed with this, I will see how the rest of the week goes, I will be a busy girl and can test my theory

Thanks for all the help and input folks!

Photo of Joe Morgan

Joe Morgan

  • 7546 Posts
  • 4136 Reply Likes

Hello Yvonne,

I’m glad to hear you have successfully completed your two hour video. Primarily by saving your project often, closing and reopening Camtasia, and restarting the project diligently.

As long as you have enough installed RAM memory you should be able to hold off on restarting Camtasia until you reach the 2000 MB threshold in most cases. I only say this because it can save you the trouble of restarting it as often as you do. For myself, if I exceed the 2000 MB threshold Camtasia starts performing sluggishly shortly thereafter. So even if I’ve taken my eyes off of the task manager the program itself lets me know it’s time for a restart.

I’m curious how much RAM memory you have installed on your computer? The reason I ask is that virtual memory is only utilized by the computer when you have filled available RAM to capacity. Virtual memory is also an extremely slow and inefficient source of memory that can slow computer processes to a crawl. Anytime you are relying on virtual memory to keep your computer running you should look into installing more RAM memory. The amount of RAM memory you can install is also limited By the capacity of the motherboard.

The operating system itself doesn’t require much RAM memory to run. Couple that with the Camtasia editor and some other basic processes. RAM memory usage should not climb very high. Especially when you are restarting Camtasia before exceeding that 2000MB threshold of usage. By all rights 4 GB of installed RAM should be sufficient to carry all of your computing needs if you keep your other programs closed.

I’m glad you’re keeping us up-to-date on how things are going. I am hoping to hear further updates from you in the future.

Regards and have a great week, Joe

Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes

Hi Joe,

I have 16Gig of Ram (Max on my Motherboard) i7 intel core 240GHz

I would rather fall in the habit of doing it the way I did it yesterday. That will eliminate any chances of my project getting corrupted as it did on Friday. The reason for that is that I multitask like crazy between Camasia, CorelDraw, Adobe Photoshop, Expressionweb, Office files,  and running my Microsoft exchange account through Explorer at the moment and that one can be a bit of a biatch, need to reload my office to fix that problem but cant find my CD ;-(

As I said I did have two minor crashes but I think it is just my fingers working faster than what Camtasia wants to work at.... have three more recordings and more coming this week,.... so by the end of this week I should have that perfected

Re the Virtual Memory, I hear what you say, but it seems to have (combined with the saving and closing and opening, done the trick) Since some serious invasions earlier this year I am running a very clean computer and almost ALL my work is saved on a removable drive, so I have a huge hard drive that is virtually empty, I do however store my recordings there

Just an interesting thought, My "filing system" is such that I I have a directory called "Recordings" and each recording get its own sub directory and everything for that recording is stored and saved together, the Project file, the course material and the original recording and even the Nero files when I do write to disk. The fact that I do not save my Project files in the Camtasia folder could not have anything to do with the problems I am having? I have noticed that whenever I open a project and ask for "recent projects" it does not pick it up. It may be a stupid thought, but the thought was that when something goes wrong it possibly wants to revert back to the Camtasie folder? in the time I have been using camtasia, only once did I get a "autobackup" pop up after a crash?.....

Happy days ....


Photo of Kelly Mullins

Kelly Mullins, TechSmith Employee & Helper

  • 2901 Posts
  • 656 Reply Likes
Hi Yvonne,

Something that has not yet been expressly brought up in this thread is a discussion on Camtasia's non-destructive editing method. When editing 2-4 hour videos, this can cause the behavior you are seeing.

What do I mean by non-destructive editing? In short, Camtasia never really cuts your video, it only hides the bits you don't want to see. This means when you put a 2 hour video on the timeline, and make one split or cut, and you now see two clips, BUT, you really haven't removed anything from the original 2 hour clip - we are only hiding the part you wanted to cut. In doing that, we have to create the entire 2 hour clip again. So in effect, you now have 4 hours of video on the timeline - no longer just 2 hours.

So, for every cut/edit you make, you are creating less visual time on the timeline, but, you are actually creating MORE processing time requiring a lot more RAM to work through all of that. 

By way of example, in this image, I have a 2 hour video recording on the timeline (in yellow). I have made several cuts and edits to pare my video down to about an hour and 15 minutes. By now, the timeline is struggling to keep up with the edits, I might experience crashing, etc. This is because I really have 16 hours of video on my timeline PLUS all of the edits, callouts, transitions, etc. to keep track of. This is just too much processing for Camtasia to handle gracefully.
Note: You can test this by making a cut on a video to create two clips. Then, drag the end of either of the clips out and you will see you can actually drag out the entire video.




This is why Kayakman and others suggest you render out MP4 clips from your original 2 hour video and bring those back into the project and delete the original clips on the timeline. This way, you are actually removing the "clutter" on the timeline, not increasing it.

Overall, Camtasia has always used this non-destructive method of editing. It is just something that needs to be worked around when using long videos on the timeline.

Kelly
User Assistance
TechSmith
(Edited)
Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes

Hi all....Ok I understand WHY it is happening, but I cannot imagine having to render not stop... I am on very tight deadlines and rendering is time lost.... My schedule is such that I edit (giving myself 4 hours for a 2 hour recording) then  render at night, that is the only way I can churn out one recording/video per day

So far my process as above is working

Joe,... I find that 2meg does not work, I crash when I go over 1.2Meg...

Yesterdays presenter is a much better presenter and I only had two crashes, maybe 3 in the entire 2 hour session, In this particular video most of my cuts very pregnant pauses

The only one other thing I have to add to my list is that

Before rendering, it is best to also restart and have a clean slate  (I render at night) before opening my project to render - the reason I say this, is that yesterday I only saved and closed Camtasia before rendering and I crashed at about 69% at which time my processor was running at 1.5Meg...

I think one thing that is important to keep an eye on is the actual Project size, The biggest I can recall that rendered successfully was 3meg.... 5 meg was a no go.... So next month I will watch the same presenter and see if I need to do the divide and conquer



Photo of yvonne

yvonne

  • 33 Posts
  • 5 Reply Likes

I would like to add this as a second comment/question

Kayakman, I tried watching the link you posted but I kept losing my sound and it kinda froze on me...

When you guys say divide and conquer, please tell me in steps what do I do?

idiots guide please


Photo of Dave O'Rourke

Dave O'Rourke, Senior Software Engineer

  • 1444 Posts
  • 419 Reply Likes
First of all, I'm sorry for the problems expressed in this thread.

Camtasia Studio 8.x is a 32-bit application.  Because of this, it can only use up to 4 GB of memory (on 64-bit systems), regardless of how much memory is on the system.  This is a limit in Windows for 32-bit applications.  In practice, out of memory conditions will occur well before this limit is reached, often between 2-3 GB due to memory fragmentation and the fact that memory requests are only satisfied with contiguous blocks of memory.  This means that users trying to edit at larger dimensions, or with more complex projects could hit this limit, and this could lead to instability.

We've recently released Camtasia 9 as a fully 64-bit application.  This raises the cap on memory, and the result is increased stability while editing larger dimensions or when building more complex projects.  This should help with the problems in this thread.  Camtasia 9 can be installed side-by-side with Camtasia 8.x, so you can download and install it to try it out.

If you continue to see problems on the latest version, please do let us know.  The best way to do that is to submit a ticket at https://support.techsmith.com and someone from our TechSupport staff will follow up with you by email to help.
(Edited)