+10

I've experimented with the DRP settings and found that anything above 240 will crash my system as soon as the DRP fills up. In other words, if I set it at 2048 I'm good until 2048 becomes full and then crash, Vegas doesn't clear the DRP properly and causes a default. Same for 1024, 4096, etc., anything above 240 and you've got trouble.

64 bit allows for more memory, if Vegas is going to be a true 64 bit program it should act like it!!!!

FIX IT!!!!

Although the specifics have changed, DRP has been problematic for as long as I can remember.

I just did a search of the Vegas forum for "Dynamic Ram Preview" and got 805 hits. Here is a quote from a 4/1/2003 post: "After working and applying lots of dynamic RAM previews and a few prerenders, I notice my system goes slower and slower. I don't understand what's happening regarding memory and use of hard drives for memory (is that possible?)."

I wonder what it is that makes this so difficult for SCS to resolve. As a former programmer, it would seem to me to not be something that would be problematic over so many years and releases - but especially so now that we have a 64 bit only version.

EDIT: I just redid the search using the more likely search term of "Ram Preview" and got 7846 hits! Obviously not all of these are related to ram preview problems, but a quick scan suggests many are.

/jerry

I turned off Indexing on my drive that contains the media files and I now have my DRP set to 2048 and no crashing!

Does this work for you?

By turn off file indexing, you mean you unchecked the box as shown here?

Yes and all folders and files when it asks after Apply.

That's something i always do with all drives on every Windows system. Indexing saves you a few seconds now and then, by wasting tons of time constantly throughout the day. Without indexing, sure, file searches may take a little bit longer. But, really, how often do you need to search large areas of your drives for files? Probably not very often. On the other hand, having it on slows everything down all the time.

Does anyone know if you do turn on, and then off the index of a drive - does Win7 use the last saved indexing while the drive was in the on-index feature mode?

Before the OS formally adopted indexing - there used to be very good third-party archive index tools you could add to the system to make it controlled in this way.

There still is a very good program. See Macecraft Software jv16 Power Tools.
It as a lot of facility for file searches and finds files that the windows search box in the corner of the screen doesn't find.
It also has other utilities including a number for the registry. I use the registry cleaner and compactor once in a while.
Needless to say I have windows search turned off.

Hope this helps.

Paul Masters

Thank you to Paul Masters for helpful tip on third-party tool.

In my configuration of render machines, I continually monitor drive performance with stress testing.

FYI about Win7 indexing - I note that in my case, the setting of Win7 indexing on or off does not affect the write performance under stress.
However, there is a toll of about 1% on read performance when the drive is set index off. This would suggest that possibly the best render performance from a source drive for video-editing is to leave the index on but the destination drive can be either setting. So this could play up a cause for examining the workflow of video editing with VegasPro.

I have file indexing on & ram preview on set anywhere between 400 & 2 gigs for vegas 11. When set to 2 gigs I run into problems but some projects call for this setting so it must be set back when render time comes. Sometimes ram preview does not even work even though vegas has performed ram preview. I'll be making the switch back to vegas 12 hopefully tomorrow. My point is ram preview & file indexing can be on with good results with Vegas 11.

Well I turned off disk indexing on my C and D drives, set my RAM preview up to 1 GB, hit shift-B and ... it crashed about 5 seconds into the pre-render. I'm sure I won't miss the disk indexing, but the problem seems to be something else.

By the way, I think that the majority of my V11 problems was this same issue. I found out about turning off the RAM preview for more stability just before I switched to V12. When I turn on RAM previewing, V12 is every bit as unstable as V11 ever was. I used to set 2 GB (out of 16) aside for RAM previews in V10 though with no problems related to this at all.

I just tried 256mb and it seems to work ok (at least so far). I am beginning to suspect that my problems with V11 all stemmed from having 16GB, and assigning such a big chunk of it to previews. The fact that I'd been doing this for so long with V10 is why I didn't even think about this.

Edit: 256mb still crashes. Not as bad as setting aside more memory, but still pretty bad. With 0mb set aside, V12 is quite stable. With 256mb, it crashes every so often. With 2GB, it crashes very often... at least that's what happens with my system.

Low settings seem to be a happy medium. It is a shame with such a monster memory rig as yours.

Laurence, I have tested that here - and have found no crash at my system.

What I see is a dramatic slowdown in the playback behaviour if I increase the RAM preview to a higher memory. My s3D MVC footage plays back best with 125 MB RAM when I use GPU acceleration - when I increase the dynamic ram to 2000 or 5000 MB the playback drops down. But no crash.

Without GPU acceleration playback is fine with 2000 or 5000 MB dynamic ram allocation too - but also here I see no crash.

AND both my SSD system drive and my raid 5 (where the media files are) have the content index enabled.

That is interesting. I see the performance slow way down with a large preview RAM buffer on those rare occasions where it takes a while to crash. Keep in mind that with V10, Vegas worked really well with a large RAM preview buffer. I used to have it set that way all the time and it was quick and responsive, and yes, I could shift-B preview entire projects at full resolution (which I often did). V12 carries on the V11 degradation of the performance of this feature.