[Wayne Waag]

Geoff,

So glad that I could be of help to you. I don’t think you’ll be sorry about upgrading to V13. IMHO, it’s a very capable editor and the latest version is also very stable. Just to clear something up, I’m also an amateur, or as I prefer to be called, a “serious enthusiast” (sounds better – LOL). Like you, I’ve been working with Vegas for about 10 years now and seem to learn something new almost every day. That’s the thing I enjoy most about participating in this forum. Thanks so much for your kind words, Geoff. You kind sir, have made my day.

wwaag

[Wayne Waag]

Glad you’re making progress. Since your source footage is interlaced, the best is to render to an interlaced delivery format. However, if you do want to render progressive, e.g. render for youtube upload, you must use a de-interlacer as you’ve discovered. Although they work, the de-interlacers in Vegas are not the best. You might try the Yadif de-interlacer. There is a plug-in that has been developed for Vegas Pro. Here is the link. https://www.yohng.com/software/yadifvegas.html There are better de-interlacers available, but they require use of avisynth and virtual dub. For the moment, I’d give the Yadif de-interlacer a try. Most of my current projects are 1080 60P. However, when using 1080 60i clips in those projects, I have used the Yadif plug-in and it seems to work pretty well. And finally, there are better encoders than those built into Vegas–notably Handbrake. There is even a one-click solution to do your encoding in Handbrake that I use all the time. https://www.vegasvideo.de/vegas-2-handbrake-en Again, glad you’re making progress.

wwaag

[Wayne Waag]

Paul,

Something must be wrong with your system or the Vegas installation. I also have V12. I do NOT have to run as administrator for the script to work. I can also do drag and drop. As far as the hypothetical problem of having 15 takes, it’s a “one-click” option in Vegasaur to remove unused Takes. There are also freeware scripts readily available that will do the same thing. But, if that’s your preferred way of dealing with the problem, then by all means, do it. I only mentioned the script for some who might not be aware of its availability and usefulness.

BTW, did you ever get your Qosmio fixed that was “pulsating on render”. Just curious about the solution.

wwaag

[Wayne Waag]

Download the free 30 day trial of Vegas Pro 13 and see if your problems disappear. If not, you will have to provide more information regarding your source footage, project settings, and render settings. Screen shots of these are the best. Vegas 8 was introduced almost 9 years ago in the days of HDV and was not designed for use with today’s newer formats.

wwaag

[Wayne Waag]

An even easier solution is to use the script “Open In Graphic Editor V1”. Once set up, you simply select an image on the timeline and run the script. It makes a copy of the image, and opens the copy in Photoshop or whatever editor you choose. Once you’ve completed editing, save and close. Back in Vegas, the edited photo has been added as a Take, an advantage being that if you’re not happy, you can always go back to the original. Works very well and avoids the problem you describe. Here is the link to where it can be downloaded, along with some other very useful scripts. https://sony.vegas.1.free.fr/

wwaag

[Wayne Waag]

No problem here either. You’ve written quite a bit about your complaints with Vegas, but have never provided any useful information that anyone could use to provide some assistance. You’ve given absolutely no information about your source footage, project settings or render settings. Without such basic information, best in the form of screen shots, no one has a clue where the source of your problem might lie.

wwaag

[Wayne Waag]

Have a look at this thread using freeware Deshaker. You simply capture the motion from a “real” clip and add that motion to another. https://www.sonycreativesoftware.com/forums/showmessage.asp?forumid=4&messageid=934171 If you’re interested I can provide details.

wwaag

[Wayne Waag]

The problem seems to be that you are saving your files as trec rather than avi. I only have a very old version of Camtasia that gives the options of recording avi or camrec files. Apparently, starting with version 8.4 it changed from camrec to trec. To quote from their website.

These files can be used to build and produce videos with the Camtasia Editor, but are not sharable videos in themselves. For example, you cannot upload a .TREC or .CAMREC to YouTube, nor can you ask someone to view those files using a standard media player. Camtasia recordings can only be opened with Camtasia.

In the past when using Camtasia, I always recorded avi files which had no problem being imported into Vegas. You might search for a way to transcode these trec files to avi. In the future, save as an avi. Good luck.

wwaag

[Wayne Waag]

Do you have the tsc2 codec installed? Here is a link. https://support.techsmith.com/hc/en-us/articles/203729988-Camtasia-Windows-Download-the-TSC2-standalone-codec

wwaag

[Wayne Waag]

Here are two other ways.

First, you can temporarily change your drive letter so you can at least open the project file. Not an ideal solution though since you will probably also have to rename your working drive’s letter as well.

Second, you can actually change the drive letter within the veg file itself. I just tried this and it actually works quite well and is pretty simple (once you know how, LOL). You will need a hex editor, not a text editor like Notepad. The one I’m using is the freeware Hexplorer. You will first need to find the hex code in the veg file for the project’s drive letter. As an example, I always use F as my project drive, so I found the hex code for “F:”, which will always the first 2 characters in your file path. Within the veg file, the hex code turned out to be 46003A. As a test, I simply changed the drive letter from F to G, which translates into a new hex code of 47003A. Using find and replace, I made these changes and saved. The saved file then opened OK in Vegas and produced the familar message that the file could not be found in the specified location(now drive G). I specified a new location (back to the orginal drive F) for the first file and it successfully changed all the remaining items to the new location. So the procedure does work. If you try this, just make sure that you are working on a copy of the veg file, so if things go awry you will always have the original. Perhaps not for the fainthearted, but it does work.

wwaag