Joe, I think it's called "saturation advertising."

Works well on TV, seeing the same advert 100 times in one evening. ;o)

I posted twice in the initial thread in what has become a thread blizzard. My posts were ignored, and instead all these parallel posts, which have nothing new to add, have been started.

LarsHD is now blocked on my computer because he doesn't respond to my posts, and seems to simply thinks that by posting the same exact problem over and over something good is going to happen. The problem is real enough, but there are ways to minimize it, some of which I already suggested, and some of which others have suggested. The problem is a combination of how Vegas's underlying structure is designed so that it can handle any video codec, at any frame size, any frame rate, with multiple effects being applied, into an external or internal monitor, at multiple playback speeds ... well, you get the idea. It is a totally different design than an editor that only handles a limited range of inputs, or a media player that only handles playback of already-rendered video.

I'm not usually an apologist for Vegas, and this problem bugs me too (especially the past few days when I've been editing some very unusual film at oddball framerates), but the flip side is that I've been able to edit some very unusual film at oddball framerates, and actually finish the project. Amazing.