Motion blur affects preview capacity?

farss wrote on 7/16/2009, 8:28 AM

Steps to repo, most obvious in HD project:

1) Set Preview to Best / Full
2) Enable Video Bus Master. Add MB envelope.
3) Create large loop region and create RAM Preview. Loop region should adjust to amount of video RAM can hold.
4) Increase MB to 24 frames by dragging MB envelope to max.
5) Create another RAM preview. Loop region will be much smaller.

With 1GB of RAM Preview I can only get 10 frames of preview with 24 frames of symetric MB. Don't know if this is a bug or expected behavior. It seems that Vegas is buffering all the frames involved in creating the preview (24 + 10 + 24) instead of just the frames needed for the preview.

Bob.

Comments

Steve Mann wrote on 7/16/2009, 9:44 PM

Doesn't motion blur effect every pixel on every frame?

Grazie wrote on 7/16/2009, 9:50 PM

I had this last night. I didn't give it further thought .. but now .. gonna try a repro with a simple veg.

Hmmm....

Grazie

farss wrote on 7/17/2009, 2:43 AM

"Doesn't motion blur effect every pixel on every frame?"

In general yes.
The number of frames involved in determining the current frame is set by the MB envelope. The MB type setting in the project determines how the adjacent frames fade and if both previous and next frames are involved. I find asymmetric gaussian the closest to the natural MB of a camera.

Bob.