Bill Burnette
1
COW Coin
Forum Replies Created
-
The little gaps — check them to see if any of your “events” are not an exact number of frames long. It happened to me that a Canon camera produced clips that would show up with fractional lengths on the timeline. With “snap” on, it is impossible to remove the gaps except by trimming each such event at frame boundaries.
-
Another clue would be the original pixel size of the picture. Also, still wondering why the borders don’t show in the preview.
-
When you say “fills the screen in editing” (in the OP) do you mean you are using a separate monitor for preview? If so what kind & is the monitor cropping a bit (overscan)?
When you added the picture to the timeline, how did you ensure that the picture would fill the frame? E.g. one way is to go to the pan/crop parameters and set the cropping to match the output aspect ratio, first being sure your project output aspect ratio matches your rendering (DVD) aspect ratio (for the whole image, not the pixels).
-
I interpreted Graham’s post to mean he would be willing to take a shot at producing an example, using the OP’s own source material as a starting point. Maybe someone else might not understand his post the same way.
Given the difficulty sometimes of interpreting what people really mean in forum questions and answers, it seems the “How could anyone …” response is inappropriate. Imagine if someone were to answer “what’s a still” by saying “How could anyone on this forum not know what a still is?”
As far as a moving camera point of view is concerned, that requirement has not been spelled out at all. With a background still and a green screen foreground, your tricks come from panning, zooming, tilting (distorting a still to simulate a change of perspective) and relative motion of fore and back. Fancier tricks might come from lighting or focus variation. Even fancier tricks come from carving up an image so that different parts are panned-zoomed-tilted individually.
How far is someone willing to go to simulate camera movement? If the original still is not wide enough, some people might go to some photoshop effort to build out the image to one or both sides using elements already in the scene or elements taken from other photos shot near the same location at the same time. Sometimes the best photo compositions are not the best source material for video just because they leave no room for panning or zooming.
-
Little gaps happen to me with QTF on only for certain cameras. Apparently the video segments from those cameras are interpreted by Vegas as having a non-integral number of frames, i.e. a fractional final frame. With QTF on, newly inserted events will not line up to the end of these fractional frames. Easy enough to find using a high timeline zoom, QTF on, and the ‘]’ key to jump to the ends of events, and fix with the ‘1’ key to trim.
-
Hi Randy,
I’m a fellow Sonar user (bvideo). Nice to see you here.
There’s a setting in Options->Preferences->General that says
“[] Close audio and MIDI ports when not the active application”
and another one that may contribute to your 8 seconds (or more with a larger project):
“[] Close media fles when not the active application”
Another consideration (for purposes of comparing with Sonar’s behavior) is whether your version of Vegas is using ASIO or not (mine is Movie Studio Platinum 12.0 and doesn’t support ASIO).
Bill B. -
It’s worth a try to delete the .sfk files for those events.
-
In VMS 11 when you insert an audio track into a 5.1 project it already has the panner. For any audio track already in the project, when you right click to the right of the fader, like where it says “front” in your (Peter’s) screen shot, you get a menu that lets you choose the role for that track — choices include the panner.
-
To clarify: I posted “…I have heard the recommendation NOT to install KLite or any other “rogue” codec pack. So I ignored the recommendation.” Not properly worded.
What I meant to say is I “ignored” Mercalli’s offer to install the latest update. So I did not ignore the recommendation NOT to install KLite.
-
Yikes! Thanks for that heads up, Dale!