.trec not recognized

  • 1
  • Question
  • Updated 4 months ago
Every time I try to make a recording of my desktop, the camtasia recorded takes much longer than usual to create the .trec file and when it is done, the camtasia editor doesn't recognize the file type. I can open any previous recordings before whatever happened, but any file I've made today keeps bringing up the same error, even though they are the exact same type as the ones that still work


Photo of jmarti52

jmarti52

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 4 months ago

  • 1
Photo of Joe Morgan

Joe Morgan

  • 9161 Posts
  • 4821 Reply Likes
It sounds like the recording isn't being saved properly.

This could happen if the drive/drives your recording and saving to don't have enough free space to capture the recording.
That might explain the delay.

If thats not the case, I see by the screenshot you're using Camtasia 9.
I would check recent Windows updates. See it one was installed at the same time errors starting showing up. If theres an operating system update, I would uninstall it.

You could try a repair install,Its quicker than a re-install and nearly as good.



Theres also a complete re-install to consider.
Including deleting the Camtasia 9 folder from the registry before reinstalling Camtasia.
This is a more desperate approach.
As it will re-set Camtasia to a like newly installed state. Everything will be re-set to default values. Including user preferences.

Regards,Joe


(Edited)
Photo of David Bookbinder

David Bookbinder

  • 120 Posts
  • 73 Reply Likes
One thing to check is whether the file is still open inĀ  the recorder. Use a program like "What is locking this file" after you've recorded the .trec file and see if it's still open in Camtasia Recorder.

I've had this problem in Camtasia 2018 several times with large .trec files. The files won't open, but if I reboot, I can then read the files. Sometimes just closing the recorder or killing its process does it, but other times it's taken a reboot.

I reported this to support, but after a long and frustrating exchange got nowhere with them, just a vague statement that development hadn't seen that problem. Perhaps if you report it, too, they'll at least have seen it twice.