Zero out your Dynamic RAM Preview under Options | Preferences | Video and try again. This always causes problems for me while rendering.

What setting DID you have your RAM Preview set at?

G

Hi Grazie,
1) I am using .MTS files, recorded with my Panasonic HDC SD300 camcorder.
2) I am usually using default settings, due to my lack of knowledge concerning this area. When I import media, I normally use the "take over media video settings", if it is called like that (I am using a non-english version, I should change that)
3) I am rendering to .m2t, I found out it produces very nice HD videos, played fluently with VLC player or on YouTube. I use HDV 1080-60i settings.
4) I don't have that much free space, though enough to make videos and still have some free GBs after. I know hat might be a problem. Currently there is 12GB free space on my SSD drive and 25GB free space on my normal disk.
5) Concerning the rendering problem - I didn't use any special effects except fade out and fade in. However, just some minutes ago I was using color correction and and soft contrast on five different video tracks, playing around with values while I the preview video was running - as vegas shut down immediately without showing any errors.
6) "Advanced Micro Devices, Inc (Cayman)" GPU acceleration is enabled.

My Video settings are:
Dynamic RAM preview: 4048MB (I have 8GB max and changed the value manually to half of it)
Maximum render threads: 16
GPU acceleration: Advanced Micro Devies, Inc. (Cayman)
Frame numbers: none
Minuature views to be shows in video events: Beginning, Middle, Endframe
External application for video recording: enabled (VidCap60.EXE)

Btw is it possible to change vegas to english without reinstalling?


Thanks for your fast reply,
Cheers
Phil

Hello SuperSet,
I have read about your solution, but didn't try so far.
I changed the value to zero now and I will tell you if my problems will stop or still continue.

Thanks for your help,
Phil

12Gb on SSD free - what is the size of the SSD?

25Gb on your "normal" - what is the size of this "normal"?

For both of these it sounds really near the limit for rendering. It could be you have a such a small virtual cache/memory disc available for rendering with that you maybe well outside of the comfortable parameters of optimization for the windows cache file (?).

If you've been successful before, with this type of activity, it could be the space you're now having to work, is working against you!

Cheers,

Grazie

I had this happen to me once or twice in Version 9. What fixed it was to make sure I removed any unused media from the Project Media window.

The SSD has 128GB max, so 12Gb free space is a little below 10%.
The other drive however has 1,5TB, so 25Gb free space is way below 10%.

I thought as long as I have enough space available for the file being created, which would take about 3Gb, and I have 25, I would be fine. Maybe that isn't so.

Vegas is installed on the SSD, maybe 12Gb free space is not enough for rendering a video of ~3Gb size - if so, can you explain to me why that is not enough?

I will clean up a little to get more free space available anyways now.

Hi Steve,
that does not make any sense to me. However, if I continue to have those problems I am going to try your solution, still I prefer having a clear reason why something is working or not.
Thanks anyways for your advice!

Philip: I thought as long as I have enough space available for the file being created, which would take about 3Gb, and I have 25, I would be fine. Maybe that isn't so.
I've been caught out by this. Now, as a minimum I make sure I have MORE than 10% available

Philip: Vegas is installed on the SSD, maybe 12Gb free space is not enough for rendering a video of ~3Gb size - if so, can you explain to me why that is not enough?
It's to do with Page files - I think? It is the way WinDoze deals with making elbow room for itself. Again, my system C drive is never more than 70% full.

I've learnt to give this Video Biz stuff lashings of room. 4x internal drives plus a removal HD tray slot plus a tree of FW linked backup drives. All in all, with my library stacks and unused HDs, I must have 4 TBs of storage. I'm still wanting more.... Oh I forgot, I've also got a further presently unlinked tower full of drives which itself has another HotSwap drive bay for HDs.

Grazie

Click on Options, hold the Shift key and click on Preferences then select the Internal tab.
FIRST - do not change anything in this tab unless you know what you are doing - you can truly screw up Vegas here.

On the "Show Only Prefs Containing" box, enter "Path". Here you will see the folders needed by Vegas. Any folder on your SSD can probably be moved to your HDD safely, as long as the folder exists. (Vegas won't create the folder for you).

Make sure your Windows temp folders aren't on the SSD. In a command window, (start/cmd), type "set t" and you will see where Windows is setting your TMP and TEMP folders. If this is on your SSD, then you probably want to move the TMP and TEMP folders to your HDD.

Go to Control Panel, System, Advanced System Settings. This will open a System Properties window. Click on the "Advanced" tab. Here you can edit the TMP and TEMP paths to your HDD. You can change only the TMP and TEMP User Variables, or both the User and System Variables to a temp folder on your HDD. Click OK, OK to get out of the Control Panel.

Thx Steve.
After I intitially changed desktop, download and several other location folders from SSD to HDD, I did this with TMP end TEMP now, too. Hope my sweet SSD lives a little longer now.

Alright, I'm going to take more care of that. Thanks for your help so far.
Cheers

Your SSD will probably outlive your PC. But it doesn't hurt to move temp files off the SSD anyway.

Phillip, have you tried reducing your preview RAM to zero as suggested above? And have you tried rendering with the CPU? (Turn off GPU in Prefs). In almost all cases where I have a rendering problem, this works for me.

So, Arthur, nulling out the RAM preview and in the same time turning off rendering with GPU seems to work. About five renderings in a row went through flawlessly.

I will try to turn one of them on next time, see if it still works, or which one causes the problem.

By the way, by reducing the RAM preview to zero, I cannot use ALT + B anymore for rendering a small part to see what it looks like. I could turn RAM preview on every time I work just to have those small previews available, then turn it off when rendering the whole movie. But that is inconvenient in the first place and I sometimes forget to turn it off in the second place.

Any advice on that one?
Thanks for all help so far, really appreciating this.
Greetings,
Phil

"By the way, by reducing the RAM preview to zero, I cannot use ALT + B anymore "

I hope not - it's Shift-B

I don't recall who, but a few years ago someone did some tests on the amount of Preview RAM and determined that even without ever using the Shift-B preview, renders needed some preview RAM. The sweet spot was 1024Kb.

I suspect that eons ago in an ancient version of Vegas, some programmer used the Preview RAM for some temp scratchpad and it's been long forgotten.

I do know that the loop region preview uses the preview RAM. Make a short region, hit Q then run in a loop and you will see the preview frame rate climb with each loop. If you set Preview RAM to zero, this won't happen.