Dynamic RAM previewing crash!!

SHTUNOT wrote on 11/15/2001, 1:38 AM
Vegas 3 says that out of 384mb of ram that 255mb is available to use. I had it set to 200,and did a rendering of about 50 seconds. Yes...50 seconds...I thought that vegas would just say "need more ram" or something.1 stereo audio track[mostly silence], 46 second avi,10 bitmap images,bunch of them composited on top of each other. Lots of position keyframed movement[side to side,large to small,different shapes,etc]. At about 35 seconds the screen redraw gets F@CKED UP and it looked like my computer was on acid[the drug]. Screen goes white and you can see my desktop icons. Shows me this error:Explorer caused an invalid page fault in module explorer.exe at 0167:00401f31. There was more but I coudn't copy it down. My system is win98se,directX8a,all up to date programs,600mhz cpu[pentium 3],2 Ide harddrives[OS...audio/video]What are the best settings to use for this.Sending copy to tech now. Later.

Comments

HPV wrote on 11/15/2001, 2:09 AM
Try setting up a max and min VCACHE setting of something around 200MB or less.
MSCONFIG
GENERAL
SYSTEM INI.
VCACHE

MinFileCache=200000
MaxFileCache=200000

Just a stab, I run 28160 on a 128MB ME system. Dynamic ram in Vegas is just a dream for me at this time.
Window 9x/ME doesn't like more than 512MB total ram use.

Craig H.
SHTUNOT wrote on 11/15/2001, 11:06 AM
I have mine set to 16384 max/min... got that advise from the cubase forum.www.bluelife.de ,good place to go for audio stuff. Tech support said that there was a bug but not sure if it was in my build...said they fixed it though.
He said,
Build number? This could be caused by a resource leak in the keyframe
drawing code. It has been fixed for the next build. Did your Video Preview
image move to the upper-left of the screen too? That was a symptom of this
bug.

BTW, the Dynamic RAM Preview won't beg for more RAM, it will just toss out
frames as new ones come in. The total number of frames is based on the size
of the RAM you set aside for it and the image size in the Video Preview
window.

///dennis adams
Software Design Engineer
Sonic Foundry, Inc.
I replied...
I think its version 3.00.050. Like I said before I had version 2.0h
installed prior with ACID/soundforge/batch...as well.The prview window
stayed in its position but like i said the screen graphics just got all
strange...where the work area meets the explorer pack at the middle of the
vegas work page was blinking black to white...weird. Plus vegas 3 never
really opens a 2.0h program right. Always added extra stuff in the media
window...stuff that isn't supposed to be in the video[extra bitmap
images,wave files,songs]. doesn't happen in 2.0h. Plus the track maximize
button doesn't minimize correctly when you click on something like the
"expand track keyframe" button.Max track...click on expand trk key[max to
min]...Minimize track...stays the same height.
Has anyone else had these problems...I keep ckecking...Later.
SHTUNOT wrote on 11/15/2001, 2:31 PM
I've gotten two replys...#1
Thanks, Eddie, for the explanation, I can repro that just fine.
Unfortunately, we are far enough into the release cycle that I'm nearly
positive this bug is going to get deferred until a maintenance release. I
hope it doesn't inconvenience you too much. Ivan: would you please put this
in the bug database when you have time?
#2:

> Eddie:
>
> Actually, Shift+B will stop creating new frames when the RAM is full, and
> adjust the time selection to what it was able to do. This is new, and I
> just learned about it myself.
>
> ///d@
My reply:Thats not entirely true...I made the loop region to be"dynamically rendered in ram" by selecting: tools-and clicking on the button for dynamic....etc. I didn't click shift+b right off the bat. I'm afraid to try it because I'm mixing 2 songs today and can't afford a crash.Let me know.
Hopefully this WILL get fixed before the shipping date which looks to be sooner than later. Not a big deal though when it comes to the tracks max/min correctly[I just want a working stable product of course]...But the dynamic ram previewing scares the crap out of me now...please take care of that first. God forbid a client had that happen in front of them...Later.
FadeToBlack wrote on 11/15/2001, 2:45 PM
SHTUNOT wrote on 11/16/2001, 2:54 AM
It always is trust me... I didn't want to imply that I would use a beta in front of "ANY" paying client...please give me that much credit dude!!! I was only implying that would be a bad thing to let something like this slip by...thats it. And that the fix was added in recently,I don't know.Lucky I guess.