![]() |
Precise cuts don't maintain accuracy when speed is changed
I've found that precise cuts don't maintain their accuracy when the clip is slowed down. For example my source footage has a shot of a beach that cuts to a shot of a house. I zoom in really close (1:1..frame by frame) and splice the clip on the exact frame where the beach footage stops and the house footage starts (with quantize to frames enabled, mind you). If I use this house footage clip in between others in an edit I find, once rendered, the clip will retain a single frame blip from the beach footage that preceeded it on it's original clip. Yet I took extra care the cut was made precisely with not even a single overlapping frame from the footage prior to it. Why is this? Is this normal? Do you have to always go at least a few frames in on a new sceen to avoid getting overlapping frames from the last?
|
So, you cut first and then slowed down? And now you say it has one additional frame?
HOW did you slow it down? |
Yeah cut it then slowed it down- via ctrl+drag.
|
Can't say that I've seen that happen and couldn't quickly duplicate it. Even if it has happened, for me it would be the last frame of a dissolve an wouldn't be visible anyway (although it would certanly be visible on a "cuts only" program!). So, I don't have a quick answer for you other than trim it again.
|
I'm guessing here.
Suppose Vegas is trying to match a certain number of frames to whatever your timeline is set to? Have you tried this with your timeline set to time and frames or absolute frames? |
Tor, I have the timeline set to 29.97 drop, and quantize to frames is enabled. Don't know if this is specifically what you were referring to.
It's odd because it doesn't show up when I'm reviewing the footage on the timeline. It's only after it's been rendered out to MPG1. |
Zoom in so that one second is about 1 cm. Press right or left arrow on the keyboard a number of times. Your cursor should move one frame each time you press, but not every time! Ever so often Vegas needs to take up slack. I suppose if you cut at one of these points you may get unlucky and end up with one frame too many.
|
But would it only show in the outputted MPG1 and not in the preview window prior to rendering?
|
With the approximation neccessary to make these things sum up right I suppose it's possible, but I do not know.
|
Glen. I run into the same problem and here is my workaround. I cut out a piece I want to slow down and render it to a new track. I than take the newly rendered clip and slow it down. So far it has always worked as planned.
|
I think I've had this "problem" as well. In and out-points change
when speed is changed. Also I've had major problems when a clip was reversed and I wanted to set in and out-points. Not workable. |
<<<-- Originally posted by Rob Lohman : Also I've had major problems when a clip was reversed and I wanted to set in and out-points. Not workable. -->>>
It works just fine as long as you do the following: Put the timeline at the END of the segment you want reversed and split at that point. Delete the part to the left and add the velocity envelope to the part on the right. Add the proper negative percentage and then find the proper end of the reversed clip. DON'T trim and then reverse - reverse and then trim but START at the END. |
I'll try that and keep it in mind. Thanks Edward!
|
One feature that would be very nice with velocity envelopes is to pin an event at a node. This would make all adjustments to the envelope pull or push video for the event, centered on that node. Sometimes with complex velocities on an event that needs to match for a cut, this would save considerable time. You would line up the clip, pin it, then adjust the edges and velocities.
|
All times are GMT -6. The time now is 01:41 AM. |
DV Info Net -- Real Names, Real People, Real Info!
1998-2025 The Digital Video Information Network