Camtasia 2018 on Mac OS X - default AVI, not TREC. How?

  • 1
  • Question
  • Updated 3 weeks ago
I would greatly appreciate if someone could please tell me how to set the default encoding to AVI in Camtasia 2018 on a Mac OS X platform. I am recording my lectures and processing them automatically on a Linux box and TREC file format does not fit in my workflow. Camtasia 9 running on MS Windows provides an option to set AVI as a default format. I do not see any such functionality in Camtasia 2018. Needless to say, this is very annoying.
Photo of mtrutsch

mtrutsch

  • 2 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of erik.groenhaug

erik.groenhaug

  • 93 Posts
  • 33 Reply Likes
Sorry, but you cannot change the internal format, since that contains so much more than a standard video file. Sfter recording and editing you may produce a mp4 or avi file
Photo of mtrutsch

mtrutsch

  • 2 Posts
  • 0 Reply Likes
Thank you, Erik. Well, you can set AVI as your default format in Camtasia 9 (at least under MS Windows). Why not in Camtasia 2018 (at least not under Mac OS X)? In Camtasia 9 on MS Windows, you simply navigate to Tools > Options and select "Record to: .avi" in General settings tab (see the images below).



 

I cannot see anything remotely related to this in the latest version of Camtasia 2018 on my Apple machine. :-(




(Edited)
Photo of Jeff Thompson

Jeff Thompson

  • 1 Post
  • 0 Reply Likes
"Sorry, but you cannot change the internal format, since that contains so much more than a standard video file. "   This is silly, since the Windows version of Camtasia allows the recorder to create either TREC or AVI files.  It can record as either.  Why not the Mac?   If Camtasia for Windows does not need "so much more than a standard video file" then why does the Mac version?
(Edited)
Photo of paulwilliamengle

paulwilliamengle

  • 72 Posts
  • 30 Reply Likes
I think it would be helpful to ascertain if this Camtasia 9 function was retired on Camtasia 2018/2019 windows platforms.

I think the answer to that question would help answer: is this a parity issue or functionality being retired issue.