Matt Crowley
Forum Replies Created
-
Those dashed borders you’re seeing on the preview window are the “Safe Area” indicators. They show the (estimated) part of the frame that you will see on a typical TV screen. TV’s tend to chop off the outer edges of the picture due to overscan – the TV slightly enlarges the picture to ensure you don’t see any blank areas at the edges of the set. Check the Vegas help on safe areas for more info.
You can turn off the safe area indicators by clicking the grid button on the preview window toolbar.
-
Try applying the Pinch/Punch, Deform or Spherize video effects to the generated media event. None of them really makes a decent fishbowl effect, but they might get you on the right track.
-
You can get the latest updates for all versions from the Sony software updates page at https://www.sonycreativesoftware.com/download/updates
-
As far as I can tell (and this is in Movie Studio 10) the dynamic RAM preview system caches all frames that get rendered to the preview window/device. So, playing a short selection of your project in loop mode will go a bit sluggish at first, but the dynamic RAM preview cache will accumulate rendered frames and after a couple of loops, the selection will play smoothly. Each pass will add as many frames to the cache as can be rendered in real time, and the rendered frames from the previous passes will be used to speed up playback. This happens in normal (non-loop) playback too.
If you do a “build dynamic RAM preview” then loop the selection, it should immediately play smoothly because you’ve forced Vegas to do a non-realtime render of ALL selected frames.
Any normal preview playback while editing adds to the dynamic preview cache but, as soon as you make an edit, the corresponding cache contents become obsolete and get binned, forcing re-render of that part of the timeline when you preview.
If you set the cache size to zero, all previewing will be done in real-time, or as fast as the CPU allows. Complex sections may be stuttery/sluggish because the renderer can’t keep up. If you set the cache to a modest value (say 256MB) you’ll only be able to create a small dynamic RAM preview (at 256MB at 1/4 size preview, I got a max of 20secs). If you set the cache size too big, Vegas sucks up RAM that would otherwise be used for media and other apps.
I noticed that if I try to create too large a RAM preview, the selection gets shortened and the preview doesn’t always play properly – as if the preview cache gets lost/corrupted and I’m back with not-so-realtime preview. Maybe that’s what Chloe was seeing. Forcing Vegas to build a new dynamic RAM preview (with the adjusted selection) usually sorts it out.
-
It sounds like you’ve got some rogue keyframes in your video events (clips).
When you open the pan/crop window for an event, you’ll see a strip along the bottom with one or more diamonds on it. Those are keyframe markers, and at each one the pan/crop parameters can be changed.
In your case, you only want ONE keyframe at the start of each event. Click on that keyframe diamond to edit its settings as required, and delete (right-click on) the others.
As for the slipping/de-syncing of multiple audio events… that shouldn’t happen just by opening a project. Might you have nudged one of more events by mistake, or had Ripple edit enabled (that makes later events also move if you move one event)?
-
Yeah, best to try the Internal settings first on a non-critical system to test. The Internal tab setting are probably hidden for a reason! These are the settings that are either still in development or are not expected to be changed. Think of it as like tweaking the Windows Registry.
-
I notice that in Movie Studio 10, there are a number of internal/hidden prefences relating to project, render, media etc paths. I haven’t tried changing any of them but that may be a start for tweaking the defaults. You can see these by shift-clicking Preferences on the Options menu and clicking the Internal tab. Browse the parameters, or type “path” into the filter box at the bottom of the dialog. There are quite a few even in Movie Studio.
-
In Movie Studio there’s no audio plugin automation/keyframing so you can’t change effect parameters during or between audio events on a track. You only get pan and volume automation. Video tracks get effect automation though…
You cannot apply different effects to each audio event on a track either – effects are only at the track level.
You must either use a separate track for each effect setting, or apply non-realtime effects to individual audio events (right-click the audio event and select “Apply non-real-time event FX”.
-
Depending on your preview settings, the output video may appear a bit blurry when you are editing/previewing your project. When you render your project at Good or Best quality the output should be cleaner and sharper, unless the source footage isn’t particularly sharp to start with.
-
In Movie Studio you don’t get velocity envelopes but you can still reverse a video event (clip). I guess you can do the same in Vegas Pro.
Simply right-click the event, and click Reverse. A check mark will appear next to Reverse to indicate the event is reversed, and it will play backwards at normal speed.