Put trec files with project file, or at least re-find them relative to it.

  • 2
  • Idea
  • Updated 7 months ago
I see that Camtasia has ongoing issues with file management, with some kind of hoopla with producing (multi-gigabyte?!) zip files and the like. That doesn't cut it.  

1) I should be able to say that I want all trec files (and audio files from Voice recording) saved with the project file. I'd then set the project file first, into a new subdirectory for the project, and all the recordings would go into it. 
2) In all cases, when opening a project file, if the trec or audio files aren't found at their original absolute path name, then they should be searched for relative to the project file, ie by stripping the common section of the absolute path name first, and looking in the same flat directory second. Under no circumstances can a project be unusable when all the files are present, just because they happen to have moved. 
3) Most modern software allows you to re-find missing media, ie if it is not found, even as above, a proxy is provided, and the user can then explicitly provide the location of the media, ie using an open-file dialog that navigates to the new location. (See Adobe software, for example)

This isn't hard, it doesn't take debate. Stuff moves, ALL THE TIME. To different machines, different operating systems, you name it. You can't require that some magic hoops be done IN ADVANCE.  It doesn't require any user-level interface or visibility at all---in most circumstances it should "just work" behind the scenes in almost any situation.

Likewise, what's the thing about mac captions not being readable on windows, and vice versa? Just NO. It's just text! There's no excuse for anything like that. 

PS - I don't get the Library thing. I've never used a piece of one tutorial in another tutorial, and I've been using Camtasia (primarily on Windows) for quite a long time. 
Photo of russ


  • 13 Posts
  • 0 Reply Likes

Posted 7 months ago

  • 2
Photo of Mal Reynolds

Mal Reynolds

  • 435 Posts
  • 280 Reply Likes
You have one vote from me, though you'll find votes for this scattered amongst a whole range of other threads as well.

(Which, incidentally is why this forum is a really bad way of aggregating demand for a feature. A feature might have been voted for a couple of hundred times but if those votes are scattered across multiple threads stretching over half a decade - and this topic has been kicking around in this thread or that for at least that time - a look at one individual thread suggests that only a handful of people want it.)

Relative paths is one that I've been arguing for for ages.

As for this:

This isn't hard, it doesn't take debate. Stuff moves, ALL THE TIME.

This. Just. This.

My current workaround is to dump all of the assets in the same folder as the project file. If the program can't find them on the original path, it will at least look for them in the same path.

I do disagree about the utility of the library, though. I use it in every project. It allows me to store a collection of assets which have as close to a uniform look and feel as I can get allowing for the Amazingly Elastic Text in Camtasia annotations. I have a range of annotations, sound effects, intro and outro clips and so on in there, organised into folders. In that way I don't need to go hunting for the right annotation or other asset (and this includes groups of assets) and format them, I just stick it in from the library and I don't need to have another copy of it in the project folder.

The nested folders in C2018 are a good idea in theory but in reality you want to get to your assets as quickly as possible so I for one will be staying with top level folders.

Where it DOES have an issue is in the fact that it is not cloud-based so that it can be shared between machines and workgroups, but that is also a problem with the Snagit library.

That, however, is a digression. The main reason that I adopted the practice of putting everything in one folder is that I got soooooo sick of "Camtasia cannot find..." dialogs when I archive a project.

And before anyone suggests it, as they almost inevitably do:No. Zipping. Every. Project. Before. Moving. It. Is NOT a "best practice". Not in this universe or any other. It is an ugly, kludgy, inefficient, time consuming practice which deserved to be left in 1997.
Photo of Paul Middlin

Paul Middlin, Employee

  • 873 Posts
  • 198 Reply Likes
Hi, there seems to be a little confusion I'd like to clear up.

First, all trec (and any other media) does indeed get saved into the project file. Or at least, this is what it does by default, though you can override this and turn that off if you choose. When you click "save" for the first time, and choose where you want to save your project, you'll note that there is a "create standalone project". This is what causes all of your media to be saved into the project, instead of referenced from wherever it came from on your hard drive. 

To your third point, you can indeed find missing media. If your timeline shows a media that has gone missing, you can right-click on it and choose to browse for that file, wherever it has moved to. 

I like your suggestion of at least attempting to find the media if it is missing by looking in the same folder as the project, though I worry it won't help many people since by default recordings, movies, audio, and projects are all saved into disparate locations. There is also a danger of picking up the wrong file just because it had the right name. Still, it might work out well more often than not? Something for us to consider for sure, so thank you.

Last, I'm not sure what issue you are having with captions. Projects you've captioned on one platform and take to the other should still work.

Oh, Mal- I agree, there is no need or reason to zip the project all the time, given the points above. That's meant for when you transfer projects to another platform, because of the funny way our filesystems work on Mac vs Windows:
On Mac- you can put all the media right inside the project file, because on Mac they have this somewhat sneaky feature where folder can look and behave like a file, and that's what our project files are. Unfortunately, if you moved this to a windows PC, it would just look like a folder.
On Windows, project files are just one file, and trying to stuff all the media into that file would require a lot of thrashing on your hard drive in order to pull large media in and out, which wouldn't be performant, and would be very frustrating. So, we use a file and some folders, and have to zip it up to move it across platforms and kinda... convert between the two file management systems.