jhon , Thanks for your time , the overlap is there , transitions are gone , i am still looking in the prefences , it might be a checked box or so , its strange.

ok , so Pre-rendering only affects the Video preview window for smoother play back , great.

i read here and on the ultimate S plugin that some Film look FX need to be rendered , thats why i thought its somthing i should do every now and then ..

Everything that isn't strait unaffected DV footage needs to be rendered eventually. That's why you use the Render As command to make your output file.

There are two kinds of prerendering: dynamic prerender (Shift B, often called RAM preview) and selectively prerender (Shift M). They are used for slightly different purposes. Dynamic prerender quickly renders short sections to RAM so that you can preview the finished version quickly and smoothly in real-time. These are purely an editing tool to help you decide if you've got the right effect/transition/composition, etc. They disappear almost as soon as you make any change to the timeline, or if you prerender something else and both prerenders won't fit in RAM.

The selective prerenders are stored as files on your hard drive. While they also allow smooth real-time playback, the main purpose of these is to, well ... pre-render sections that you know are finished and won't be edited anymore. This way when you do the final render these sections are already done and can be included in the output very quickly. Of course, making any changes to a pre-rendered section makes that pre-rendered file invalid and that section must be rendered again. If you use these well you can render your project in bits as you go along and the final render at the end should be very fast. On the other hand, Vegas is very persnickety about these files and will use almost any excuse to decide they're invalid and drop them, so often you end up needing to render large portions anyway.

In either case, you never need to pre-render at all. Each type of prerender can be useful for various situations and it's good to experiment with them to see when they come in handy.

And on your other question, i can't think of any reason other than a serious malfunction for your transitions to disappear. Something's definately wrong.

thanks for the detailed info and replay chienworks ..

i found why i lost the Transitions ... and the fades too , but not overlaps.

this is a mixed 4:3 and 16:9 project , and i decided after all to switch the 4:3 clips to widescreen using Ultimate S , so this deleted all Tranistions and fades i did , why? i dont know. i just imported some pics and added transitions then i converted all media to widescreen and there gone.

i should have done the conversion before doing anything else , but its not an issue at all , i just wanted to know why so this doesnt happen again ..

way when you do the final render these sections are already done and can be included in the output very quickly.

Except that if you look at Vegas cross-eyed, it seems to "lose" these pre-renders and just does the whole darn render again. The RAM preview is the way to go for speeding things up. It is too bad, however, that it has to rely on RAM. I think the main reason it is so fast is not because it is rendering to RAM, but instead because it renders at screen resolution (I think) rather than project resolution.

Hold that thought, John!

How about using a Nested Proxy as a Previewing option? Nested Timelines make a proxy file. Does/has anybody expressly used this method to Preview a section?

Grazie

The proxy file is audio only.

I mean the the file nesting file? What is it called? The *.veg.sfap0 . .. thingie? ... The one that gets created when I drop a Veg into a Veg? That file .. isn't that also called a proxy file? No?

Grazie