Camtasia 2019 Intermittent freezing, choppy

  • 1
  • Problem
  • Updated 4 months ago
Hi there, 

My colleague and I both have Surface Book 2 laptops (16 gb RAM, GTX 1050) and are running Camtasia 2019. We are both experiencing an issue during editing / timeline navigation, where every 30 - 40 seconds, the program locks up, the cursor disappears, and the windows "wheel" appears, preventing selection. This lasts for 3 or 4 seconds, and then goes back to normal. 

We have tried updating our graphics drivers, switching to software-only mode as others have suggested, and we are working off of local-only files (no cloud syncing or network drives to blame here, unfortunately). We never had this problem on the older versions of Camtasia, though admittedly they were running on different hardware (older desktop PCs. We have recently upgraded to the surface books). 

If anyone has any suggestions to remedy this, it would be much appreciated! 

Thanks in advance, 
-Tyler
Photo of tyler.hewitt

tyler.hewitt

  • 3 Posts
  • 0 Reply Likes
  • frustrated

Posted 4 months ago

  • 1
Photo of Ed Covney

Ed Covney

  • 1042 Posts
  • 523 Reply Likes
The "wheel"? If you open "Resource Manager" [ Task Manager], [Performance Tab], "Open Resource Manager" at the bottom. Down the left side, you can monitor your:
1 - CPU,
2 - Memory,
3 - Disk Drive, and
4 - GPU

One of those is being over-tasked, only you can determine which it is.


Photo of Muscle Whisperer

Muscle Whisperer

  • 176 Posts
  • 94 Reply Likes
I occasionally have this problem as well, and I think it's because Camtasia is having trouble handling one of your resources. If I play around with the video file in HandBrake, sometimes that clears up the lag and hang.
This is absolutely for sure if your container is an .MTS file. Camtasia cannot handle MTS.
Photo of marcusrgnf

marcusrgnf

  • 7 Posts
  • 5 Reply Likes
When it happens with me,  usually it's a lot of opened things in background (Mac here).  Closing other programs usually helps.   Also,  a almost-full drive may be the reason. 
Photo of tyler.hewitt

tyler.hewitt

  • 3 Posts
  • 0 Reply Likes
Thanks for the replies :)

To clarify, I'm talking about the circle/wheel that spins in place of your cursor when windows is busy, or performing tasks in the background: 

I've checked the task manager while using Camtasia, and my memory never goes above 65% usage, while my CPU is never above 45%. During the 4 seconds of "hang time" the percentages don't spike at all. Interestingly however, the power usage does go up, from Low/Moderate to Very High.

My Disk drive is mostly empty (384g free out of 500). I do have Photoshop and some other apps open in the background, but that has never caused this issue for us in the past, so we're stumped. 

I should also mention it seems to happen in all Camtasia projects, big and small, for both me and my colleague. We have tested a few 7-10 minute projects, and one larger 30 minute project. Some have videos in them, and some are made up of only captions/images and audio.

Thanks again.



Photo of kayakman

kayakman, Champion

  • 8018 Posts
  • 2773 Reply Likes
any chance that you're working with a short autosave setting?

I've seen that behavior when Camtasia is autosaving an open, unsaved, edited project
Photo of Ed Covney

Ed Covney

  • 1042 Posts
  • 523 Reply Likes
Try one: "my memory never goes above 65% usage" - In absolute terms does that mean in Performance tab, is it reporting something like 10.3 / 15.9 GB (65%)? i.e. do you have a  "Pagefile.sys" hidden in the root folder?

Try two: Did your Surface Book 2 happen to come with a utility that shows CPU/GPU/MB temperatures?

Try three:  Have you tried with the other apps closed?


Photo of tyler.hewitt

tyler.hewitt

  • 3 Posts
  • 0 Reply Likes
I can't believe it, but I think it was the autosave setting. I turned it off and I haven't seen the issue all day today. unreal. Again on older hardware we didn't experience this issue, but I'd rather turn the feature off and have smooth editing. I save every few minutes anyway.

Great suggestions all, and thanks again!
Photo of Joe Morgan

Joe Morgan

  • 9076 Posts
  • 4784 Reply Likes
I would leave autosave on.
Have it save your work every 15 minutes or so. See if that works for you.
That way, it shouldn't effect you much. If Camtasia crashes 2 or 3  hours into a editing session and you haven't saved your project.
You'll want to throw your monitor at the wall.
Photo of kayakman

kayakman, Champion

  • 8018 Posts
  • 2773 Reply Likes
I'd suggest a alternate strategy; set it to 5 minutes [it's what I do]

like yourself, I manually save constantly, virtually after every edit

accordingly, I've rarely had Camtasia ever create an autosaved project file

item #21 in this collection might be helpful ...
https://www.screencast.com/t/QBXzmB0Dr

Photo of Ed Covney

Ed Covney

  • 1042 Posts
  • 523 Reply Likes
The project files are small as compared to media or trec files, it makes me wonder how tech smith could possible be mis-handling auto saves.
Photo of Joe Morgan

Joe Morgan

  • 9076 Posts
  • 4784 Reply Likes
With Adobes Premiere Pro,  I've encountered this when RAM becomes temporarily  saturated.Like working with FX.
Or the CPU is nearly maxed out.
These scenarios  rarely occur at the instant autosave  kicks in. 

Camtasia can choke the life out of a CPU while playing back a video. Triggering scenario 2.
It a shame they haven't adopted any measures to aid playback.

To me, a setting of 15 minutes is more than enough.
 If you lose power or  something goes wrong, odds are you'll lose less than 10 minutes work. 
Photo of kayakman

kayakman, Champion

  • 8018 Posts
  • 2773 Reply Likes
there's no reason to ever loose any work due to delayed autosaved projects; just manually save often ...

per my tutorial, autosaves are triggered by time that has lapsed since the last, unsaved edit; if you manually execute a save every few minutes, with autosave set at 15 minutes, it will never fire; otherwise, you'd have to make an edit, then don't save it, then wait 15 minutes before the next autosaved project file is created; test this for yourself ...
Photo of Joe Morgan

Joe Morgan

  • 9076 Posts
  • 4784 Reply Likes
To each his own.

I don't manually save my projects often.In my experience, its redundant.
I'll edit for long periods without saving. Saving when I go make coffee or lunch, take a short break,etc.

Why, because autosave has my back for everything else.
Thats its purpose.

I used to save a lot when running 32bit versions of Camtasia. Because it was so easy to crash them.
 
Photo of kayakman

kayakman, Champion

  • 8018 Posts
  • 2773 Reply Likes
As previously stated, I manually save every few minutes, and especially after every major edit

I've never lost any editing work, and never had to rely on an autosaved recovery other than when Camtasia has itself crashed in conjunction with some editing activity

best practice ... save early, save often ... 

better to be safe than sorry
Photo of Joe Morgan

Joe Morgan

  • 9076 Posts
  • 4784 Reply Likes
If saving your work every few minutes is required.
Meaning......... you “actually lose work” when you fail to do so.

I empathize with your plight.

 

If you feel the autosave function cannot be trusted. Or that it isn’t functioning as designed.

You may want to contact support about your concerns.

 

 Based on the autosave settings you've chosen.

An autosave file can contain up to 99%+ of the projects current status/editing state/call it what you wish.

Providing you access to 2 nearly identical project files at all times.

 

That is, up until you launch a manual save.

When updating the project to its original location. You’re permanently altering that file.

 

At the same time.

Under normal circumstances.

You’re simultaneously deleting the only redundant file available to you.

Essentially, leaving a project more vulnerable. With no backup file to fall back on.




Photo of kayakman

kayakman, Champion

  • 8018 Posts
  • 2773 Reply Likes
the above post is riddled with errors and misstatements of material facts, so I'll keep this simple ... as stated above ...

best practice ... save early, save often ... 

better to be safe than sorry
Photo of Joe Morgan

Joe Morgan

  • 9076 Posts
  • 4784 Reply Likes
You've made a sweeping statement.

I'll make this simple............
back up the statement and show me where I've erred.
I stand by my assessment.

(Edited)
Photo of Muscle Whisperer

Muscle Whisperer

  • 176 Posts
  • 94 Reply Likes
Please, Joe and Kayakman, you guys are like parents to us and nobody likes to see their parents fighting!
Kayakman - I see your point about manually saving, which updates the original file.
Joe - I see your point about letting an automatic save created a separate copy of the file.
The original complaint is about the system hanging whenever the program does an Autosave. I've experienced this, and just this week started to experience it again. If turning off Autosave lets me work uninterrupted, that's the solution I'll go for.
We're seeing a situation in which the program takes far, far too long and somehow wraps up resources for 20-30 seconds at a time, sometimes every minute, just because it wants to. No other program I know will do that.
And this is the reason we're discussing this issue.
Respect, man!
Photo of Ed Covney

Ed Covney

  • 1042 Posts
  • 523 Reply Likes
We should all be reserving our frustrations for Tech Smith's idionuget programmers (I wouldn't call them idiots on their site). I'm on my new system now, installed Camtasia to D:\ but it still only allows auto saves to:
     C:\Users\usern\AppData\Local\TechSmith\Camtasia Studio\19.0\Auto-Saves, idionugets indeed.

Of course they think I'm stupid for wanting to control the whereabouts of MY files, imagine a user who thinks he knows his own system better because he has planned tediously for and thoroughly tested everything. A user who knows how to spread the OS, Software, and Data across two or more drives for the best possible performance (It's called load sharing on mainframes.).

<end rant>
(Edited)
Photo of Joe Morgan

Joe Morgan

  • 9076 Posts
  • 4784 Reply Likes
I understand the problem and the proposed workaround.

Perhaps its the autosave file location that is to blame?
Camtasia defaults to the AppData folder on the C-Drive.
You cannot change this location.

I store my projects files on a separate drive.
I have autosave set to 2 minutes with Camtasia.
I don't run into this issue.
For those that store their projects on the C-drive as well.
The autosave file will be both read from and written to the same drive. Perhaps that creating a bottle neck for some users?

When you save a project manually.
Using the original name and location.
Camtasia deletes the existing autosave file.

I consider this pertinent the discussion. Not an error or a misstatement of material facts.
Its simply what occurs. Tech Support could confirm this.

To me, this hinders autosave greatly.
Case in point.
If you set autosave to save your project every 15 minutes.
Then, continued to save manually every few minutes.
An autosave file will never be generated.
What good is this when the power goes out, Camtasia crashes, you've recently saved, etc.?



Premiere Pro not only saves the most recent autosave created.
It will save as many versions as you want.
The default setting is 20.
With a new file created every 15 minutes. You can choose the duration intervals as well.
Once you reach 20 save files.
Its starts overwriting the oldest one.
Leaving you with a history state reaching back 5 hours.
Premiere Pro will allow you to save up 10,000,000 autosaves per project. Which seems ridiculous. But it is what it is.


Set up and used correctly.
Autosave can save your hide when things go south.
Its functionality or lack there of. Is best understood.

Allowing one to make informed decisions based on its Pros & Cons.

Photo of Ed Covney

Ed Covney

  • 1042 Posts
  • 523 Reply Likes
YES !!  When Windows does something in C: drive, that something has a higher priority and Camtasia can just suck its thumbs until Windows is done.  It's so easy to resolve if I can just figure out whose head to thump!  The very large trec are also placed on C:\, to the documents folder. Why would anyone (TechSmith) stream a file to the Boot drive - MORONS, MORONS,  . . . . 

A 720p streams at about 4MB / second, 1080p at 9 MB/sec. When will they ever learn that stupid stuff like this is the root of many of our evils.
Photo of Joe Morgan

Joe Morgan

  • 9076 Posts
  • 4784 Reply Likes
To be fair,
I've configured the temporary recording file location to my M-Drive.
I save those recordings to the same drive.The M represents...... "Media Drive"

By all rights, when I save the recording, they shouldn't have to be relocated. I would think altering the associated metadata is all that would be required. Placing it in my Camtasia recordings folder.
If not, my 1TB 860 EVO's are rated to 600 terabytes of writes before any degradation may set in. Thats a massive amount of data.

I've stored some files on my C-drive for convenience.
 Relegating it to Programs and the Operating System for the most part..
(Edited)
Photo of kayakman

kayakman, Champion

  • 8018 Posts
  • 2773 Reply Likes
an extra conservative approach to saving projects as editing advances ... works with whatever autosave setting you prefer ...

load your project in Camtasia editor

immediately execute a save-as [Alt-F,A]; save to a location of your choosing, preferably in their own folder; give this copy a simple numerical name, like 000; you now have 2 identical project files

do some editing, like for several minutes; execute another save-as [Alt-F,A]; name it 001

do more editing; for another several minutes; execute another save-as [Alt-F,A]; name it 002

continue editing and execute save-as's as long as desired; use a different sequential numerical name for each

during this process, you never loose a previous good copy of a project file

at the end of last editing session, do a save-as back to original project name

at this point, you still have a copy of the original, unedited project [#000]

entire editing history is preserved in all the number sequenced save-as files

when project is all finished, and after production and zipping, just delete all the save-as files [they should just be in their own folder somewhere]