They managed to ruin RAM preview too.

Sebaz wrote on 9/22/2008, 3:26 PM
Look, I know some people here thinks I'm bitching all the time, but I wouldn't bitch if I didn't have anything to bitch about. I started using Vegas in version 8.0a, and sometimes I use RAM preview for some small loops where I want to preview something quick. It was a little buggy in the sense that sometimes some of the rendered frames in memory were gone and I had to do another Shit+B to get those frames rendered back to memory.

But now, not only they haven't fixed that bug, they actually rendered RAM preview useless. I made a selection, pressed Shift+B and it started rendering horribly slow, about 1 frame per second. We're talking about AVCHD footage without any filters, effects, or overlays, in a simple one video, one audio timeline. When it finishes rendering, playback is not smooth at all like it was whenever I did a RAM preview in 8a or 8b. So I press Shift+B again. It starts rendering slowly again as if the previous render had not existed.

When the render is finished, playback is still terrible. I press Shift+B once more, and I get the same result. I could keep typing the same thing over and over, because I simply can't get Vegas to render to RAM and playback smoothly.

I restarted the computer, I even selected another project, I made sure no other programs were running, pretty much everything I could think of.

This is getting ridiculous. I want so bad to keep using this program because I enjoy editing in it, but Sony with their lack of care for this product is making it really hard. It's frustrations all the time. Last night I left a timeline rendering to 8 Mbps 1440 AVCHD just to put it on a DVD-RW and preview it on my BD player, and this morning I woke up and it had stalled at 5%. The program didn't crash, it was just there doing nothing. When I wanted to close it, it asked me if I wanted to stop the operation, to which I clicked yes, but nothing happened. I had to kill the process from the task manager after hopelessly waiting for Vegas to close by itself. And it's just one more bug for the list...

Comments

Marco. wrote on 9/22/2008, 3:50 PM
Mmh, Ram preview works fine and fast here with V8.0c on three different systems. AVCHD color corrected.

Marco
Serena wrote on 9/22/2008, 3:52 PM
RAM preview works fine here for 1920x1080 cineform encoded avi.
Spot|DSE wrote on 9/22/2008, 4:14 PM
RAM preview works fine for us too, we use it religiously. Would have likely been the first bug detected during Beta for us.
Sebaz wrote on 9/22/2008, 4:29 PM
Well, I don't know what could possibly be wrong with my setup. I mean, right now I'm running with just 2 GB because I had to send the defective stick to OCZ and they wanted the full set so I had to send the other one too. But when I began using Vegas and RAM preview, I only had 2 GB in my system and it was like that for quite a while, and I had no trouble rendering 1 GB to RAM.
farss wrote on 9/22/2008, 4:45 PM
Something could have failed or come loose.
Try reseating your RAM, make certain it's correctly in the sockets and latched in. If that fails to help then try cleaning the contacts on the sticks. Just wipe the contacts with a paper tissue but make certain you don't leave any paper fibres behind.
It's also quite likely that changes in code can make a CPU etc work harder. The obvious thing this can expose is cooling problems. The not so obvious problem it can expose is power supply issues.

If all that fails to fix your problem(s) and I mean after you've made a concerted effort to eliminate hardware issues then try to construct a simple project using a very small amount of media that will fail.
You can then get others to download it and see if they can repo your problem. If we can then you get a pat on the back for finding a bug.

Bob.
TheHappyFriar wrote on 9/22/2008, 6:25 PM
i tested ram preview in 8c on DV & HDV footage. renders just as fast as 8b (good/full quality).
fldave wrote on 9/22/2008, 8:17 PM
The main time I have had issues with Dynamic RAM preview is when I am zoomed in very close on the timeline. Never any dropped frames, but simply redrawing the timeline as it is scrolling across the screen takes time. My main machine is a lowly P4 3.2Ghz machine.

So I select my timeline section, zoom way out so the selected section is about 1/10th of the screen, then generate the RAM preview.

Slick as a whistle.
xberk wrote on 9/22/2008, 8:48 PM
I have no issue with RAM preview in 8.0C .. I have dynamic RAM set to 256 and number of threads to 4 as I have a Quad..The lower I set the dynamic RAM the less video I can RAM preview. Don't really know much more than that about RAM preview. It's handy. I do use it but frankly don't understand it's relation to dynamic RAM or system RAM.

Regards other issues, sounds like you might benefit from a baseline with your system. It's a pain, I know but if you really want to find out what's up ---- Make a DVD with media enough to do some testing of Vegas. Get a spare harddrive that is decent, pull your main drive and install a fresh copy of Vista on that spare drive (no need to register it), load the motherboard drivers, video driver, do the Vista updates and load and register Vegas 8.0C on this new and clean system. Load only codec needed to run your tests. If under theses conditions you still have rendering and RAM preview issues, you'll have narrowed down the problem a great deal. But if all is well -- then you could gradually add the things you suspect might cause Vegas problems... Yeah, I know...not fun.

Yes. This is a pain. But none of us here can duplicate your system -- we all get system problems. I just had mine big time and couldn't even load 8.1 AT ALL.
I'm not saying Vegas doesn't have problems, but likely RAM preview is not one of them. If it was my system, I'd want to track down what gives!

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

tumbleweed2 wrote on 9/22/2008, 8:57 PM

DrLumen brought up the fact that the original computers were quite large, & actually had real "bugs" in them causing problems...

maybe all thats needed here is a good dousing of bug spray?... : )
DrLumen wrote on 9/22/2008, 9:26 PM
The way it sounds, it doesn't appear that hosing down sebaz's system with Raid will hurt much...

Moth found trapped between points at Relay # 70, Panel F, of the Mark II Aiken Relay Calculator while it was being tested at Harvard University, 9 September 1947.

intel i-4790k / Asus Z97 Pro / 32GB Crucial RAM / Nvidia GTX 560Ti / 500GB Samsung SSD / 256 GB Samsung SSD / 2-WDC 4TB Black HDD's / 2-WDC 1TB HDD's / 2-HP 23" Monitors / Various MIDI gear, controllers and audio interfaces

video777 wrote on 9/22/2008, 10:19 PM
Not much help but RAM preview works fine. That doesn't mean that it's totally smooth but is certainly acceptable and far better than using Liquid (which pretty much stopped you from working while it was doing supposed background rendering).

Best of luck to you.
rmack350 wrote on 9/22/2008, 10:49 PM
Sebaz's thing with the disappearing prerenders was reproduceable. This one kind of seems like a ram preview forcing the system to use the swap file, but I say that about a lot of things. I'd be watching task manager at this point, and maybe lowering the RAM preview setting.

Rob Mack