[Silviu Negoita]

This can happen in VEGAS Pro, usually because of the audio render settings.I’d check:* Project audio: 48 kHz, stereo* Render audio: AAC, 48 kHz, stereo, ideally 256–320 kbps* Make sure you aren’t accidentally rendering in mono* Check the Master Bus for compression, limiting, or other FX Make sure the audio isn’t clipping or being normalized.A good test is to render a short section as both WAV and MP4. If the WAV sounds good but the MP4 doesn’t, the issue is probably the MP4/AAC settings.If you tell me your VEGAS Pro version and the MP4 template you’re using, I can tell you exactly what settings you should use.

[Silviu Negoita]

Hello! I’d first check the render settings, especially the bitrate and resolution. Make sure the render resolution matches your project/source, and try increasing the bitrate if it’s currently low.
Also check that the footage isn’t being unnecessarily scaled and that resampling isn’t causing the softness.Hope that helps!

[Silviu Negoita]

Hey Johnny, it seems that your text is a little bit bugged(It shows <div>)Anyways, I had a similar problem in VEGAS. What fixed it for me was using Ctrl+drag to adjust the event length first, rather than relying entirely on the velocity envelope. With velocity envelopes, VEGAS can end up calculating the audio/video timing differently after multiple speed changes. I split the event at each point where I wanted a different speed, adjusted the playback rate of each section, and then made sure “Lock audio to video” was enabled before making further edits. After doing it this way, I stopped getting the gradual drift. So I don’t think Long-GOP is necessarily the cause here — it seems more related to how the velocity changes are being applied.

[Silviu Negoita]

Hello there!I’ve run into similar issues when mixing frame rates with slowed-down footage. One thing I would check first is how the Optical Flow clip is being handled inside the nested sequence. Since your project is 29.97 but you’re using 59.94 footage, I would try keeping the 59.94 source at its native frame rate and doing the speed change within the nested sequence rather than changing the project/timeline frame rate. I’d also try rendering one of the problematic nested clips to an intermediate file first, then replacing the nested version with the rendered clip. If the sync issue disappears, that would point toward the nesting/Optical Flow combination rather than the original footage. Also make sure the audio isn’t being time-stretched along with the video when you’re changing the playback rate. If the audio is supposed to remain at normal speed, I’d separate/lock it before experimenting with the video speed. If you’re still getting the drift after rendering the clip separately, I’d check whether the source files have variable frame rate (VFR), since that can cause some strange timing issues in VEGAS. Hope that helps!

[Silviu Negoita]

You’re very welcome! I would watch this video, it easily explains how frame rate affects the video.https://www.youtube.com/watch?v=WxH23dxDIsQ

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Silviu Negoita]

Hi Andy, Happy to help! And don’t worry, you’re asking exactly the right questions. Looking at the screenshots you attached, the good news is that your clips are actually very consistent. The main things I look at are: Frame rate: All four clips are 29.97 FPS, so there isn’t a frame rate mismatch between them. That’s good news, and yes, 29.97 is still a very common frame rate, especially for phones and consumer cameras. Field order: All of your clips are Progressive Scan, which is what you want. You don’t need to change anything here. Pixel aspect ratio: They’re all 1.0000 (Square), which is also exactly what you want for modern HD and 4K footage. The biggest difference I noticed is the resolution: Three clips are 1920×1080 (Full HD). One clip is 5312×2988, which is a high-resolution recording (likely from a newer smartphone). That’s perfectly fine. VEGAS will automatically scale the larger clip down to fit your project. In fact, having a higher-resolution clip can be useful because it gives you room to crop or zoom in without losing much quality.
If you have one more question after this, I’d be happy to help.

[Silviu Negoita]

You’re very welcome! In VEGAS Pro, the easiest way to check your source footage’s frame rate is to right-click the clip in the Project Media window, choose Properties, and look for the frame rate (for example, 29.97, 30, 59.94, or 60 FPS). You can also right-click the clip on the timeline and select Properties to see the media information. As a general rule, it’s best to set your project frame rate to match the footage that makes up most of your project. For example, if the majority of your clips are 60 FPS, use a 60 FPS project. If most are 30 FPS, use a 30 FPS project.

If you’re unsure what frame rate to use for a specific project, feel free to ask. Let me know what types of cameras or phones the footage came from, and I can help you choose the best settings.

[Silviu Negoita]

Hi Andy,What you’re describing is usually caused by not having enough frames in the original recording for the amount of slow motion you’re applying.For example:If your footage was recorded at 30 FPS and you slow it to 50% speed, VEGAS has to “stretch” those 30 frames to fill 60 frames’ worth of time. Since there aren’t enough unique frames, the result looks choppy or like it’s skipping. If the footage was recorded at 60 FPS, you can slow it to 50% speed much more smoothly because there are twice as many original frames available.Here are a few things to check:1.Match your project frame rate to your source frame rate. If your footage is 60 FPS, set the project to 60 FPS as well.◦ 1.Enable Resampling◦ Right-click the event → Switching → try Smart Resample (or Optical Flow in newer versions). This can generate intermediate frames and make slow motion smoother. 2. DONT slow footage beyond what its frame rate can support◦ 60 FPS is ideal for moderate slow motion.◦ 120 FPS or higher is much better if you plan on heavy slow motion.If you let me know:• what frame rate your original footage was recorded at (30, 60, 120 FPS, etc.)

• how much you’re slowing it down, and which version of VEGAS you’re using,I Can give more specific recommendations

[Silviu Negoita]

Hi Johnny,

Since your source footage is already 1080p at 60 FPS and your PC specs are more than capable of handling it, the issue is likely related to your project settings or the source footage rather than your hardware.

Here are a few things I’d check:

1. Make sure your project frame rate matches your footage.

Go to File → Properties and verify the frame rate is set to 59.94 FPS (or exactly 60 FPS, depending on how the footage was recorded). If the project is set to 30 FPS, your final render can appear less smooth even if you export at 60 FPS.

2. Confirm your render settings.

Double-check that you’re actually rendering with a 1080p 60 FPS template. Some templates default to 30 FPS, so it’s worth opening the template settings and confirming the frame rate before rendering

If you’re still having the issue, could you let us know:

<ul data-start=”1958″ data-end=”2156″>

[Silviu Negoita]

Hi Brent,

VEGAS changed the workflow a bit compared to older versions, so the old “Border” option isn’t where many longtime users expect it to be. If you’re trying to add a white border around a photo, here is what i’d do: Put your photo on the top track. Add a Solid Color (White) media on the track below. Use Event Pan/Crop or Track Motion to make the photo slightly smaller. The white layer underneath becomes the border, and it automatically stays perfectly aligned with the image. If you’re finding that the border isn’t resizing with the image, check whether you’re resizing the event or the Pan/Crop frame. In most cases, using Pan/Crop or Track Motion to scale the image while leaving the white background underneath is the easiest way to get a clean, even border.