I have noticed the same and generally avoid dissolves as a result.

John

This may, or may not be related.

I have occasionally found some "flashes" at odd points between clips... not sure if it was just on dissolves.

Anyway on very careful examination I found an odd single frame of another clip hanging around. I cannot for the life of me figure out what I would have done to cause such a thing. The problem ocurred in some long form projects where I am doing a lot of editing and moving things around... so it could have been self inflicted (although how I could have trimmed so that only a single frame was left is beyond me).

I've had projects where I ended up with single frames left on the TL. Don't know if that's related or not but it could easily be. If one of those ended up in the same place as a dissolve or fade would explain it. Here's a thoery as to how it MIGHT happen:
Swicth off quantize to frames, trim so event is not a whole number of frames, swicth on quantize and then delete even. Vegas deletes clip upto nearest whole frame leaving partial frame behind.

I will not have an opportunity to test this theory for a while but when I do I'll post results.

I think the other way you can make dissolves go a bit wierd is having a fade at the end of an event as well as a dissolve.

In my particular case I never touched the "quantize to frames" thing... but that could indeed be the problem BixGomez is having.

I have occasionally found some "flashes" at odd points between clips... not sure if it was just on dissolves
============================

You are describing the "blank frames" phenomenon which dates back to version 2.0. Sometimes they are black and sometimes they are white. Search it and you'll see. Expand the timeline and you will find them when they occur (for no apparent reason). I have actually had a frame from somewhere else in the video flash on screen momentarily (enough to ruin the whole thing), yet I couldn't actually find it when I expanded the timeline.

SF/Sony never quite got a handle on this and some of those who have never experienced them don't even deny their existence after this long. Personally I think they have something to do with the quirky ripple editing feature which hasn't differed much in the last three versions, but I am sure I could be way off base as well.

John

“…full-opacity "flashes" of the scene I am dissolving into.”

Not sure if this applies here but, depending on your CPU, some transitions may not preview at the full frame rate, which would cause a choppy playback. To check, you could loop the transition and let it replay while you watch the frame rate and see if it improves with consecutive plays, or alternatively prerender the section.

JL

Thats why I view the entire veg file before rendering. I always find gaps, one frame pieces, overlaps and cuts that blink too much. The cuts have to be sometimes recut to get a good unblinking cut.

JJK

Nope.. in my case what I got was an odd frame from another clip in the video. I don't doubt that what you are describing happens... but I am not describing the "blank frames" phenomenon.