Thanks Ed,

I guess that kills that theory.

John

There was a thread that I read in here a few days ago that basically said turning off "Auto Ripple", seemed to fix this problem.
Mark

There was a thread that I read in here a few days ago that basically said turning off "Auto Ripple", seemed to fix this problem.
================
I have NEVER used "Auto Ripple" yet I frequently have the flash frame problem.

John

John,

Do you turn on/off "quantize to frames" during projects? I usually leave it on, but have noticed the flash frame on occasion after turning it off, making adjustments, and turning it back on.

-Les

John,

Do you turn on/off "quantize to frames" during projects? I usually leave it on, but have noticed the flash frame on occasion after turning it off, making adjustments, and turning it back on.
=================
I have done both. Doesn't seem to matter.
Quantize to frames sometimes causes (I believe) the Blank frames issue not the Flash frames issue. Not 100% certain about that either though (Blank frames/quantize relationship).

I still think it's just inaccurate snapping on Vegas' part. "Snap to Grid" is particularly troublesome if the end of an event is just a hair from one of the grid lines. I've had much fewer flash frames turning all the "Snap to" options off and turning "Quantize to Frames" on.

I've had much fewer flash frames turning all the "Snap to" options off and turning "Quantize to Frames" on.
=========
Brian,
The point is, you shouldn't be having ANY. That is what we are trying to resolve.

John

I just finished a 58 minute project in Vegas 4 and had no flash frames. The project was very clean, though. I used the group function a lot and if I needed to move some stuff around, I moved sections and luckily didn't have to mess with any inserts in areas where I previously had placed a crossfade or other transistion. I did not sweep the unused media from the pool. I just let it stay. I also risked keeping the same veg name throughout all saves and revisions.

My Theory is as the memory starts to be "tasked" Vegas does funny things.
The memory quality, motherboard processor combo's, etc. That's why the programmers don't see it, they have the best stuff and can't afford to have run of the mill stuff like us. I have only noticed the frame thing on 30 minute or longer clips. On short stuff I never see it. Sometimes with complex variable 3d combined with track motion and panning the render will stop dead in it's tracks and not give a reason. This is on a 1 hr clip. So I pre-render the complex stuff to avi and there is no problem. I'm guessing it's all memory related. Anybody out there an electronic clarivoiant? Grazie, how do you speel that?

JJK

I'm still new to Vegas, so haven't experienced the problem.
For those that have, how do you resolve the problem and make the flash(es) go away? Or can you?

For those that have, how do you resolve the problem and make the flash(es) go away? Or can you?

==============
Since they are never visible no matter how far out you stretch the timeline to look for them you have to rerender until they go away. That means that every time you rerender you have to sit and watch the entire video to see if it is gone and new ones haven't appeared. In my case that means 2 hours plus for my average video. That is ONE of the reasons I refused to buy Vegas 5 in protest. New bells and whistles, but flash frames, audio dropouts, blank black frames, inexplicable video gaps, impractical ripple edit, amateuirish credit roll, etc always go unaddressed. Too much time is wasted checking for glitches. I'll take fixing these problems over the ability to do HDV any day of the week. It's called "basic editing".

John

For those that have, how do you resolve the problem and make the flash(es) go away? Or can you?

The best way it to exit and restart Vegas just prior to rendering.

Maybe that why I have never experienced It.
I do a cold boot before a long render.
Who knows?

Jimmy

Never seen any of these problems as long as I've been using V5 - though I don't have slow stuff either. Never had a drop out - never had a flash frame - never had much of anything go wrong with V5. So I have no idea.

Dave

Dave, same here. My renders usually take place after weeks of editing sessions, no reboots, and 10 to 20 other programs open and active simultaneously. I think the "lack of reboot" issue can be discounted.

I think the "lack of reboot" issue can be discounted
========
Agreed. I have always rebooted before rendering using Vegas 2, 3, and 4.

John

John, did you mean "always" or "never"?

Amen to that thought, I'd add lack of proper A/V locking to the list.
I've had the problem, about twice now, last time:

I'm in PAL land.
Very simple project, apart from trim head and tail that's it, one track of vision and one of audio from the camera tape.
QTF definately ON
Ripple anything OFF
Vegas managed to encode one frame from earlier in the file into the mpeg-2 file which needless to say made the problem last more than 1 frame!
Things to consider:

Vegas is time NOT frame based. I'm suspecting that as Vegas renders out it doesn't advance by discreet frames and derives a frame, rather it advances using a very fine granularity and converts that into frame numbers. Except the odd error creeps into that conversion causing Vegas to pull a frame from the wrong location, either way past the end of the media (giving you a black frame) or from elsewhere on the T/L giving you a flash frame. This may be only happening due to process switching in Windows, when Vegas stops/starts running from the other thread a value is lost or corrupted.
This explains why the problem is totally random and you cannot see the problem on the T/L, worse still the problem is not reproduceable. It likely only happens when Vegas is interrupted at a specific line of code. To find that they'd need to run the code module against a check program that stops when an error is detected, simply running lots of projects will never find it and even if it did occur it wouldn't be reproduceable.

I have to agree, this is a major problem, it's been there probably since day one of Vegas. If the users cannot have confidence in the application reliably performing the most simple of tasks it does not bode well for the future of Vegas. We feed a HUGE amount of vision through Vegas, over 40 hours of vision per week at times, having to watch every frame of our final output to check for this error is a MAJOR COST IMPOST on us.

Bob.

I have found that even with Quantize frames turned on, if I drag a video file that was captured with SCENE detection ON to the timeline, the last frame of the scene will not end on a Quantized frame. I always have to clean it up. I feel this is the cause of the flashes. I don't think that the scene detection is actually creating a full frame at the end of each file.

Dave T2

Sorry no, see my post above. Sometimes the audio track end a little past the vision, it's an issue but not the cause of this problem.
Bob.

How can you be so sure? I don't have problems with audio, it is the video file that is always left hanging.

Dave T2

Dave, i also have to wonder why this is even an issue. How often do you use the entire clip after capturing with scene detection? Haven't you started the camera a few moments early and let it run a few moments after the scene? Wouldn't you almost always be trimming at least a fraction of a second from the ends? If you are trimming then it doens't make any difference if the first or last frames are messed up. If you aren't trimming, then you should be because the first & last frames are often messed up.