Not seeing the issue myself. But I don't leave the Vegas temp folder set to it's default location on the C drive. I set it to d:\scratch pointing to my Vegas work ssd (set at the bottom of Options/Preferences/General) and that folder just has a bunch of little stuff on it... mostly restored.veg and autosave.veg.bak files. My AppData\Local\Temp folder over on C: has mostly small log and tmp files... all from other apps.

“If you have to ask what jazz is, you'll never know.”

― Louis Armstrong

"If you have to worry about the size of temp files, your boot partition is too small."

__ John Dennis

The $65 solution. The $120 solution

The free tool to move your system.

Thanks, I appreciate the ideas, but I'm really hoping to find a solution that gets Vegas to use the intended temp folder and stop filling up my other drives.

Not seeing the issue myself. But I don't leave the Vegas temp folder set to it's default location on the C drive. I set it to d:\scratch pointing to my Vegas work ssd (set at the bottom of Options/Preferences/General) and that folder just has a bunch of little stuff on it... mostly restored.veg and autosave.veg.bak files. My AppData\Local\Temp folder over on C: has mostly small log and tmp files... all from other apps.

I do the same thing, my temp folder is on my D drive. The files that I'm getting on my C drive are .tmp files that are only generated while rendering videos, once rendering is complete the files disappear.

The files that I'm getting on my C drive are .tmp files that are only generated while rendering videos, once rendering is complete the files disappear.

And those bother you? They may be undo / redo buffers.

The files that I'm getting on my C drive are .tmp files that are only generated while rendering videos, once rendering is complete the files disappear.

And those bother you? They may be undo / redo buffers.

Yes, they are bothering me. That's why I'm posting here seeking a solution for my issue.

To be more clear, Vegas generates a single temp file during rendering, usually with a file name like "sgqs.1.tmp".
I am trying to render a large video file, and the temp file on my C drive is growing upwards of 50 GB.

I'm pretty sure that the undo/redo buffers are generating in the temp folder on my D drive like they are supposed to, but Vegas 19 has introduced this new issue of generating .tmp files on my C drive during rendering, and the file sizes increases throughout the duration of the render.

Just in case I'm being unclear, I have rendered videos much larger than this current project many times over on several previous versions of Vegas. This is a seemingly new and unique issue with Vegas 19 in particular.

Have you double checked with simple steps like adding sole media file onto timeline & rendering?

If the issue is still there, have you reported the bug to Magix?

Have you double checked with simple steps like adding sole media file onto timeline & rendering?

If the issue is still there, have you reported the bug to Magix?

Yes, I've tried a bunch of different files and rendering options. In every situation, the size of the temp file is directly related to how long of a render I'm doing.

I have also report to Magix, but they strongly suggested posting here for quicker help.

Are you generating .MOV files?

Are you generating .MOV files?

No, I usually render to mp4.

The OP is right about Vegas renders. If you open the folder C:\Users\<yourName>\AppData\Local\Temp and begin a render using a Magix AVC/AAC MP4 template, you will see a temp file that increases in size during the render.

However, when trying Voukoder with the default x264 template, an entry does appear but remains at 0 bytes and is removed as soon as the render is cancelled. I found that the 2 Vegas temp files remained even after the render was cancelled. Rendering with HappyOtterScripts produced no entry at all.

The recommended solution--use Voukoder (it's free) plus better quality to boot.

I was using Voukoder with Vegas 18 and just neglected to update it to 19. Will give this a shot, thank you!

This expanding .tmp file seems to be a new feature in VP19. Not all VP users read these forums and the expanding tmp file could well create issues.

Voukoder with VP18/19 produce 0 tmp file, likewise VP18 (MAGIX AVC/AAC MP4).

Again not all users will be aware of Voukoder.

This new feature should be drawn to the attention of the developers for future correction.

Edit: Have just rechecked using VP18. There appears to be only 1 .tmp file associated with a render and is not cleared on completion of the render. However when a new render is started the existing render is zeroed and a new .tmp file opened. Maybe there is a case for a desktop folder %temp% which could be cleared manually.

This expanding .tmp file seems to be a new feature in VP19.

Or, perhaps a bug?

@wwaag

I don't think the choice to create a .tmp file could/should be considered a bug. Give the developers some room to accomplish their task.

What happens to the .tmp file under normal conditions or through exception handling routines is subject to debate, as is the effect on ones system from possible repeated mishandling.

Many of us would never notice even a very large stranded .tmp file because 1) we don't run the boot disk that close to the brink, or 2) we refresh the image of the system frequently for other reasons.

@wwaag

I don't think the choice to create a .tmp file could/should be considered a bug. Give the developers some room to accomplish their task.

What happens to the .tmp file under normal conditions or through exception handling routines is subject to debate, as is the effect on ones system from possible repeated mishandling.

Many of us would never notice even a very large stranded .tmp file because 1) we don't run the boot disk that close to the brink, or 2) we refresh the image of the system frequently for other reasons.

Just throwing my two cents in here- I don't run my boot disk super close to the brink, I only noticed the .tmp file after it hit 60 GB.