well not exactly.. but these are manually rendered clips of certain sequences which have been prerendered and placed above the original edit.. I do this to alleviate render times and i can have a faster preview...

anyways. i was working with some 4:3 footage and decided to convert the pre-render to 16:9
Easy and faster than realtime on the quad core...

So i do my pan and crop and change my project properties. i then start the render and WHOOMP... its telling me a 4 minute clip will take 43 minutes to render..

cancel that...

go back into my timeline and mute all other video tracks...

go back to render and WHAMMO... a 4:3 clip with a duration of 5min 10s rendered to 16:9 in 3.16minutes..

OK, so whats happening here?
Isnt vegas overwriting the need to run filter?
Isnt vegas checking to see which video track takes priority before processing then "nulling" all underlaying tracks?

I tell you what, there are users out ther who WOULDNT think to mute their underlaying tracks and would continue to have issues with render times.
.
As it now renders to a 2pass MPG2, its hitting the 6 minute mark.. which is pretty good considering its doing a conversion while it encodes to MPG2 2 pass...

At least i found and fixed MY issue... i wonder how many others have done this to as well..??
I never had an isue with this in the past, but with V7 on this new quad it seems ive unleashed a new headache...