We're running Camtasia 9.1.1 (Build 2546) on Windows 7 Enterprise (soon to be upgraded to Win 10). we save projects on drives shared by 3 - 4 other members of an eLearning Development team - although only one developer ever accesses a given project. Projects are saved in separate locations on this shared drive, each labeled with the project name...normal file handling technique.
We've noticed that over time, if Camtasia is saved repeatedly in the same location (again, normal technique), it loses files (see screenshot), rendering a project unusable. You'll close out a file the day before, come in the next day and see the screenshot. It seems the file loss syndrome is selective: objects such as text boxes survive; the source audio and/or video files do not. In every case no files are moved prior to this happening.
This is extremely frustrating given the time it takes to generate projects. One workaround we've devised is to save projects in different locations each time they're opened. This is a wasteful way to manage files, but Camtasia seems to like not being saved in the same place after a certain indeterminate time.
Has anyone on your team experienced this and, if so, is there a better workaround to prevent file loss?
Many thanks!
Rob Weir
eLearning Developer
Einstein Healthcare Network
weirrob0@einstein.edu
215-456-8306

We've noticed that over time, if Camtasia is saved repeatedly in the same location (again, normal technique), it loses files (see screenshot), rendering a project unusable. You'll close out a file the day before, come in the next day and see the screenshot. It seems the file loss syndrome is selective: objects such as text boxes survive; the source audio and/or video files do not. In every case no files are moved prior to this happening.
This is extremely frustrating given the time it takes to generate projects. One workaround we've devised is to save projects in different locations each time they're opened. This is a wasteful way to manage files, but Camtasia seems to like not being saved in the same place after a certain indeterminate time.
Has anyone on your team experienced this and, if so, is there a better workaround to prevent file loss?
Many thanks!
Rob Weir
eLearning Developer
Einstein Healthcare Network
weirrob0@einstein.edu
215-456-8306
