Prerender bug still in 8.0c

Sebaz wrote on 9/19/2008, 8:24 PM

I just realized that the prerender bug is still present in 8.0c. After just a few prerenders to 1080i MPEG2 to preview color and level adjustments, now it shows the prerender progress, but when it's done, no blue bars, and no playback from the prerendered files. The only way to get back to normal is to close Vegas and reopen it, wasting time waiting for the project to load.

So Sony, how many people did you have testing this thing? Just one high schooler one or two hours a day, right? Heck, I would've caught it even if I had tested it that much.

Back to post

Comments

PeterWright wrote on 9/22/2008, 1:39 AM

Shouldn't make much difference Grazie - the complexity may affect the Time it takes, but you still end up with n seconds of rendered video in RAM - I'm just trying this out on a compositing project ...... there - just got 20 seconds of a 5 track composite, then 24 secs further along the T/L where there were 3 tracks, plus pan crop & motion, so it does seem to affect it, but not by much.

This is a 1920 x 1080 project - I have 2 Gb of Ram total, of which 1Gb is allocated to Preview.

Grazie wrote on 9/22/2008, 3:34 AM

My profound apologies Peter!! - It was your

"1Gb is allocated to Preview" that twigged my OWN memory . . .

( .. slinks away in shame) . . I still had my allocation set at . . er .. er . . 120mbs! Now set at 600 mbs

Grazie

PeterWright wrote on 9/22/2008, 5:30 AM

No shame needed Grazie - I do much siller things several times a day!

rmack350 wrote on 9/22/2008, 6:15 AM

I was told ages ago by an SCS support person that RAM preview will stash away enough frames to get playback going. If you have a very fast machine then Vegas might only cache every other frame, or every third frame...the point being that a ram preview goes farther on a faster system. (I'd want to test that to see if it's true but I think you could do the test on complex and non-complex regions of the timeline to verify this.)

I'm not in need of any sort of HD capability but I tested Sebastian's problem out last night and yes, vegas eventually starts ignoring selective prerenders. It creates the files but doesn't use them unless you restart Vegas. I filed a support ticket to add to the push. Vegas shouldn't have a bug like this. Sure, it's not a show stopper, but it's also the sort of bug that destroys confidence in the product.

Rob Mack

Sebaz wrote on 9/22/2008, 6:20 AM

RAM previews may work to a certain extent, but they are not bug free either. Half the times I do a RAM preview I press the Play button or hit Enter and I still get stutter playback. So I have to press Shift+B again and I see that Vegas stops at some of the frames in the loop to render them again. The program is supposed to grab that 1 GB of RAM and once it rendered it keep it to itself, but it doesn't. Usually with a second pass it's good to go, but I have seen instances in which it takes three passes to finally playback the loop in real time, and this is with 4GB of total RAM, 1 GB assigned to RAM preview.