Oh really? Like what? This is the first I've heard of it? Pray, do tell Bill? I'm all ears. Up to now all I've heard praise, and render times going down. What is this with memory? Is this in Build Ram Previews?
yeah, here and a lot over at DVINFO.net, there is a subset of users complaining of the unreliability of V8 pro. I notice that these users all seem to be using quad cores. If this rumor is real, no doubt SMS will address it, eventually. Please understand this isn't FACT, but an observation. One gentleman from your neck of the woods was quite vocal about his discontent, so much that he was censored. I beleive he was running a quad core machine; and, quite adamant that it was the Vegas GUI.
"There seems to be some increasing evidence that there is some kind of memory problems with quad core intels and V8"
I have not seen that, using a Q6600.
"Also, do Build Ram Preview times improve?"
Well, maybe in a complete different way then you would expect. I am not talking about prerendered files here - since a quadcore is fast enough to avoid to use such things. But see what I have seen:
A HDV-testproject with 6 streams, 5 as PiPs over another HDV stream, were rendered both in Vegas 7 and Vegas 8. The testproject was 1080 50i HDV2 material, had a length of 1:12 minutes, and render quality was "best". Smartrendering was disabled, to be able to compare the findings with Vegas 7. The Q6600 is equiped with 4 GB Ram, even if it is true that you see only 3 GB with XP (actually, only 2 on that maschine, given the fact that a Canopus NX is installed too).
Then the size of the dynamic ram preview was changed, and the render time was measured. Following findings:
Vegas 7:
4:31 Minuten bei 750 MB
4:27 Minuten bei 511 MB
7:30 Minuten bei 256 MB
9:16 Minuten bei 0 MB
Vegas 8:
5:11 Minuten bei 750 MB
5:07 Minuten bei 511 MB
7:11 Minuten bei 256 MB
9:32 Minuten bei 0 MB
Vegas 7 was faster then Vegas 8, but more: the dynamic ram preview had a significant impact to total render time.
And yes, your . . "I am not talking about prerendered files here - since a quadcore is fast enough to avoid to use such things." - I understand there is no NEED to make pre-renders with QUADs, what I am saying is that I use Prerends as a neat way of doing a Preview. So, have you tried that?
I'd like you to clear-up what you are saying about BRPs though?
I've been running my QX6700 Quad-core machine (Specs here.) for almost a year now and have had no issues with Vegas 7 or Vegas 8a. Vegas 8.0 was a little bumpy but it all got straightened out in 8a.
So I knew a quad would help for cutting render times a lot, but does it make the Vegas preview close to real frame rate/high quality as well? I mean, currently on my old dual-Xeon 2.8GHz system, I always leave my preview window in Preview (auto) to keep my frame rate close to real-time.
I haven't really heard much mention if it helped with the preview window playback, only the rendering.
I would like to know Pre-rendering for PREVIEWING - QUAD Render Times? BUILD Ram Preview times? Is anybody finding improvements?
As Vegas only makes use of faster CPU and faster RAM, I am truly very interested to find out IF QUADies are being accessed and made use of by VP8 for the purposes of Previewing.
I do not need Prerendering for previewing at all! Makes no sense, the preview capabilities are good enough for HDV (4 to 5 streams on a Q6600 2.4 Ghz). Maybe you need it for AVCHD, if you edit that native.
I use Prerenders to PREVIEW. Yes I know and realise that with this sought of speed Prerends are kinda redundant. As I say it is solely for PREVIEWING . .
I have a Q6600 XP x64 machine with 4Gb RAM. Spec here.
Most of the time if I edit just one track I get a full (best) preview at a smooth 25fps over DVI to my external 24" Dell. But just now and then it drops to 18-21fps for a while for no apparent reason. I can't establish a pattern of why it happens. Changing the preview quality doesn't help. Even a reboot doesn't help and it is a pain because I find it really difficult to edit if I don't have the full frame rate. One thing I have noticed is that after Vegas and the project have been open a good while it seems to recover back to smooth 25fps.