Mystery frame appearing - bug?

Comments

BillyBoy wrote on 2/12/2005, 2:13 PM
Rebooting ALWAYS is a good idea IF you going to be doing a longish render. In actual tests I cut rendering time by roughly 10%. If rendering time is important to you, and it always is a hot topic, then this is one simple way to get a leg up.
jeff-beardall wrote on 2/12/2005, 2:29 PM
I've had the same problem with iris xitions...one stray frame from the end of the xition shows up at the beginning of the xition. I've had them show up in a final render and then not show up in a final render and then show up from a good render again in DVDA2....it has got to be caused by something both apps share...maybe something to do with the fact that Vegas can work with video events that aren't quantized to frames?
neanderthal wrote on 2/12/2005, 3:57 PM
I had a black frame appear to me too. I thought I was going nuts.... I redid the clip (a loop) over and over, moving split points, changing all sorts of stuff. I finally got a render without the frame, but have no idea how....
Blues_Jam wrote on 2/12/2005, 11:42 PM
I have also had the stray frame issue several times and always thought it was a problem with Dynamic Ram Preview which is why I would love to see a "Clear Dynamic Ram" function added to Vegas 6.

Until then I try to remember to shut down Vegas and restart it before rendering. I have never seen a stray frame after freshly restarting so it must have something to do with ram that initializing clears, IMHO.

Blues
craftech wrote on 2/13/2005, 7:51 AM
It has been there since Vegas 3 along with the audio flatline problem and the blank frames issue. All three ARE bugs that go unaddressed because all of you clamor to buy the latest version anyway and these problems never get fixed. To make sure it doesn't end up in a final render you have to sit and watch the entire video glued to the screen every time you re-render it.
If it is 2 hours plus, that's really annoying and unnecessarily time consuming. That is one of the primary reasons why I refused to buy Vegas 5.
Not to mention transitions that have to be fiddled with, a poor titler, and a limited credit roll application amongst other things mentioned for years on these forums and un-addressed in new versions of the software. What good are bells and whistles when the basics suffer from unacceptable bugs.

John
monchavo wrote on 2/13/2005, 8:23 AM
The first time I saw a mystery black frame, I assumed it was a fault in the decompression from the source I was using. I took a fairly extreme route, and split around the frame, rejoined the clips up and presto it was gone (natch!)

I'd be interested to know if it would have been there had I not split, and just restarted vegas.

[r]Evolution wrote on 2/13/2005, 10:01 AM
Just happened to me... AGAIN!
V5d
craftech wrote on 2/13/2005, 2:54 PM
The closest I have come to figuring out how to reduce the likelihood of these things is to stretch out the timeline and eliminate gaps in the audio and/or video frames. That SEEMS to reduce the likelihood..............................I think.

John

PS: Doug (original poster),
Would you consider editing the title and putting the word "flash frame" in there? When people search past posts, there are years worth of references to "flash frames" as opposed to "mystery frames". That way this thread will come up along with the others when people using Vegas 16 are looking for answers to the "flash frame" phenomenon.