Serious render flaw V7 and V8

DJPadre wrote on 4/14/2008, 5:41 AM
OK, lay 2 video tracks, throw on some heavyu filtering like MB2 or even a filter chain with more than 3 filters..

make sure both video tracks are not muted
Now go to render and start rendering to any codec you like

Notice how it will run like a bag of crap

Now kill ur render and go back to vegas and, now mute the bottom layer

start the render again using the same settings u had before

Notice the difference?

Seems that vegas is accessing "unseen" (within the edit) video tracks while rendering.
I dont know why, but v6 didnt have this problem at all

So cna someone tell me why clips which are nto visible are beign processed with the visible clips above?

Its a total wast of time now as i do manual multicam work and i usualy leave my 'safety" camera rolling form beging to end on teh lower track then cut to the top track which has my A roll stuff... I never used to worry about the lower layer but now im forced to go over the entire edit and remove the bits and piece which are on dupe tracks...
Waste of time and very bloody annoying..

anyone know how to fix ths or is this jsut another bug we have to live with..

System spec is a quad core q6600 (not overclocked)
AGP 6800GT overclocked (makes a whopping diff to MB2)
2gb ram on WinXP SP2
Vegas 7e and 8b

thoughts?

PS- you dont need MB2 to run this test...

also i tested on a quad core with2gb ram with an 8800GT setup and the same thing happens only difference is that MB2 is much faster



Comments

Opampman wrote on 4/14/2008, 6:49 AM
Just tried the same test with a couple of clips using MB2. Running a core duo 4gigs of ram. The first 100 frames took 1:25 to render and then I muted the second track and the first 100 frames took 2 seconds.
farss wrote on 4/14/2008, 2:43 PM
Have you tried this with 7d?

After a few days of grief with 7e I've pulled the last of it and gone back to 7d.

Bob.
DJPadre wrote on 4/14/2008, 3:11 PM
actually i might try that, but i just spent 2 whole days configuring this new multirig setup (and still cant get the bloody networking happening)

but yeah to say i was dissapointed would be an understatement.

It is a serious flaw and it shoudlnt exist on either 8 or 7 for that matter

this is what Beta testing is for, not client testing.. hell if i didnt know what to look for id still be bitchign bout vegas render times

Now how would one go about goign back to 7d? Id i uninstall V7 and install 7d, all my settings are going to be nuked are they not?
rmack350 wrote on 4/14/2008, 3:44 PM
What happens if, instead of muting the lower track, you just kill the render and then start it again, without changes?

I suspect that since Vegas is showing frames while you render, it's also caching them in RAM. A second render might go really quickly no matter what. Just a hypothesis, I'm not in a position to test this.

A 100 second clip might be affected this way but a ten minute program wouldn't be affected much. As far as DJ's scenario goes, I don't know how long the region he's rendering is.

Rob Mack
DJPadre wrote on 4/14/2008, 3:45 PM
just went into the internal settings...

Change my render threads to 8 instead of 4 (yes this is a single quad core)

didnt do much to fix my problem,but im now checking my render times and they DO seem faster

Just under though i noticed it had a setting for enable multicore on playback, so i turned that on, and now, i get near realtime playback, off the timeline at full best with 2 filters with hdv, so at least THAT is taken care of...

now for the multitrack issue...
Guy S. wrote on 4/14/2008, 5:00 PM
Render threads - I couldn't get more than 4.

I also could not find a setting that would enable multicore timeline playback, nor could I find anything in the Help files. Where might I find this setting?

I have an HP XW 8400 with two dual-core Xeons -- I assume this counts as a quad core?