Can't solve why, Ray, but I've had an occasional anomaly like this, and I've solved it a couple of times by moving the problem event to a different track - sometimes inserting a new track to do so. Worth a try if you haven't already ..

Well here's one from the old school " Welcome To Windows 101 " rule book:

When all else fails, reboot.

Can't give ya any more info than that but reboot and re-render and ta-daa, all is right with the world. Kinda feel a little like a dumb ass that of all the things I tried before posting, that wasnt one of em. But hey, thanks for the moral support !!!

- Ray

www.undergroundplanet.com

Yup .. that was my was on my tack too . . I was going for a rename and reopen . . kinda like a reboot .. . here it was . . :

"Hiyah Mutts!

Ok . . when I get into "Loosing My Mind" time, I need to throw my hands in the air and just say, "Well, this IS beyond me! - I don't have a current 'cure' for this . .. " what I then do is try saving and renaming the project as something else. Openning this new one up and carry on. Sometimes - I've heard it said - software just doesn't get it! . . . Lotsa tracks lotsa maths . . maybe with callouts to stuff scattered all over the discs . . somehting may just HAVE to "give". - Too much Maths is just that . .too much maths . . . . . I hope someone does copme back with a "solution" . . . GREAT! If not, what then? Bills have to be paid and the bacon has to come home . .. . yeah?

Maybe my post here is premature and a solution is winging its way to here as we speak . .. but if not . ? . .

. . every 6 seconds eh? Very interesting . . ? hmmm . . . . . "


. . grazie

Just a thought here, I've never had this happen or tried this fix but I've rad a few suggestions that this MAY relate to the contents of the RAM preview buffer.
Rebooting would clear that but I also recall there's a more elegant way to clear it but don't quite rememeber what it was, maybe just disabling it?

Bob, think you are onto something . .maybe need to set RAM Preview higher . .. ?

G

While I am a great believer in the magical powers of re-booting, I don't think it will help in this case. I have been tracking down all sorts of weird behavior that has something to do with roundoff errors in how event lengths are stored. I have submitted several examples to Sony.

Without getting into (another) long post, the solution to many of the problems (and perhaps yours) is to first go to the problem spot in your project. Make sure that "Quantize to Frames" and "Enable Snapping are turned on. Now, take any event on any track that starts or stops within a few frames of the problem area and shorten or lengthen it by one frame. "Let go" of the event, and then lenghten or shorten it back to its original size. Make sure to "let go" of the event with the mouse so that Vegas first calculates its new length before you then return it back to its original length. Given your particular problem, this exercise will be especially important for the event that is causing your problems. If your event is a short one, and it both starts AND ends within a few seconds of the problem area, make sure you do this to both ends.

Actually, you can usually tell if you have a problem before you do any of this. First, make sure Quantize to Frames is on. Then, press and hold the Alt key and then press the left and right arrows to "walk" down the project timeline exactly one frame at a time. Zoom all the way in. If the cursor doesn't land exactly at the end of the video event (which it often will not), then you have a potential problem.

There have been many reports about "flash frames" and random blank frames and many other related issues. I believe they are all manifestations of the same issue.

Well here's one from the old school " Welcome To Windows 101 " rule book: When all else fails, reboot.

As opposed to the MAC rule book: reinstall the software, then reboot.

John