Clips not snapping to grid perfectly

John-Rodgers wrote on 11/5/2025, 9:12 PM

Okay for some reason, I have my project set to Measures and Beats, I have Grid Spacing set to 16th Notes, I have Enable Snapping, Snap to Grid, Snap to Marker, and Snap to All Events turned on, and I have Quantize to Frames turned off. However, when I add a clip to the grid, it doesn't snap perfectly when I zoom in. It used to do that before, but now it does it for me. Any idea on how fix this? I'm using Vegas Pro 21.

Comments

Steve_Rhoden wrote on 11/8/2025, 2:24 PM

@John-Rodgers In that Default Layout, try it with Quantize to Frames turned on and see.

John-Rodgers wrote on 11/12/2025, 12:47 PM

Now it's doing it in both layouts again

John-Rodgers wrote on 11/14/2025, 8:31 PM

I just realized it only does it from time to time

DMT3 wrote on 12/5/2025, 1:32 PM

There is NO REASON to ever turn off QUANTIZE TO FRAMES when editing video. They should remove that option. Video always has to edit on a frame, period.

Howard-Vigorita wrote on 12/5/2025, 2:09 PM

There is NO REASON to ever turn off QUANTIZE TO FRAMES when editing video. They should remove that option. Video always has to edit on a frame, period.

@DMT3 They would need to exempt region-marking... video frame quantization is too course for accurate control over audio events. There's an option to not quantize audio-only edits but it doesn't apply to region-marking audio envelopes which is an essential part of my workflow. Only workaround I've found is to turn off video quantization while doing audio volume, mute, pan, and fx envelope edits. Without accurate region-marking, the only workaround would be to tediously insert 4-point envelope regions one point at a time.

DMT3 wrote on 12/5/2025, 2:16 PM

@Howard-Vigorita Yeah, I mentioned when editing video. It should be a video rule, with audio exceptions. But audio has its "frames" also. They are the samples. You cannot edit less than a sample in audio, but since a sample is so short, in most cases it is not an issue.

John-Rodgers wrote on 12/14/2025, 12:43 PM

I also realized that when I zoom in on an event, it aligns with the grid markers inconsistently when too close. It also does that when I scroll vertically while zoomed in at the max amount. So I don't think Quantize to Frames is the cause, since I still have it turned off.

John-Rodgers wrote on 1/1/2026, 2:12 PM

I figured out that there seems to be some codec that's causing this

John-Rodgers wrote on 1/7/2026, 6:15 PM

So I cleared my cache and that temporarily resolved it. But then it started happening again. I think it's the codecs that are making the timeline and cursor out-of-sync when I zoom in.

john_dennis wrote on 1/7/2026, 8:22 PM

Perhaps you’d like to name the codec that you’re using so we can avoid it?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

John-Rodgers wrote on 1/9/2026, 4:27 PM

@john_dennis Right now, I'm using the compoundplug.dll plug-in. The timeline occasionally messes up and I can't seem to find a way to fix it until it automatically does so. I don't know exactly what's causing it.

John-Rodgers wrote on 1/9/2026, 9:57 PM

Just wanted to show more:

John-Rodgers wrote on 1/11/2026, 3:04 PM

Here's another issue this bug's causing:

Thomas97 wrote on 1/11/2026, 3:47 PM

I can confirm the snapping issue and it's a known issue that happened also in Vegas 21 and 22, yet I don't know if they ever fixed it.
The bug is caused when importing any new file (image, video, audio) by dragging and dropping it from a folder, for example, in the Vegas timeline.
The Vegas timeline needs to be zoomed out by a X certain amount.

Gid wrote on 1/11/2026, 3:59 PM

I also realized that when I zoom in on an event, it aligns with the grid markers inconsistently when too close. It also does that when I scroll vertically while zoomed in at the max amount. So I don't think Quantize to Frames is the cause, since I still have it turned off.

@John-Rodgers I could be wrong but I bet that everyone on this forum has Quantize to Frames turned On, unless as Howard mentioned they need it Off for the occasional reason.

Turn Quantize to Frames On as mentioned then comeback & report.

Vegas Pro 18 - 22
Vegas Pro/Post 19
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
NewBlue TotalFX
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans
Dell SE3223Q 31.5 Inch 4K UHD (3840x2160) Monitor, 60Hz, & an Acer 24" monitor.

At the moment my filming is done with a Samsung Galaxy S23 Ultra 5G & a GoPro Hero11 Black

I've been a Joiner/Carpenter for 40yrs, apprentice trained time served, I don't have an apprentice of my own so to share my knowledge I put videos on YouTube.

YouTube videos - https://www.youtube.com/c/Gidjoiner

 

John-Rodgers wrote on 1/11/2026, 4:14 PM

I can confirm the snapping issue and it's a known issue that happened also in Vegas 21 and 22, yet I don't know if they ever fixed it.
The bug is caused when importing any new file (image, video, audio) by dragging and dropping it from a folder, for example, in the Vegas timeline.
The Vegas timeline needs to be zoomed out by a X certain amount.

Ahh, I see now.

John-Rodgers wrote on 1/11/2026, 4:15 PM

I also realized that when I zoom in on an event, it aligns with the grid markers inconsistently when too close. It also does that when I scroll vertically while zoomed in at the max amount. So I don't think Quantize to Frames is the cause, since I still have it turned off.

@John-Rodgers I could be wrong but I bet that everyone on this forum has Quantize to Frames turned On, unless as Howard mentioned they need it Off for the occasional reason.

Turn Quantize to Frames On as mentioned then comeback & report.

Well, even with Quantize to Frames turned on, the timeline still shakes. So it's definitely not that which is causing the timeline to mess up.

Thomas97 wrote on 1/11/2026, 6:16 PM

I also realized that when I zoom in on an event, it aligns with the grid markers inconsistently when too close. It also does that when I scroll vertically while zoomed in at the max amount. So I don't think Quantize to Frames is the cause, since I still have it turned off.

@John-Rodgers I could be wrong but I bet that everyone on this forum has Quantize to Frames turned On, unless as Howard mentioned they need it Off for the occasional reason.

Turn Quantize to Frames On as mentioned then comeback & report.

Well, even with Quantize to Frames turned on, the timeline still shakes. So it's definitely not that which is causing the timeline to mess up.

Yes, the quantize to frame is not what causes the problem. Even if, it should not!

There isn't any magical way to fix this. What I do now is to work on Vegas 20 and then render on 23. However, I keep finding bugs that alterate the project in Vegas 23... Bugs that the previous version did not have.

 

Anyway, let's hope they will fix this snapping thing, again!

Thomas M.

1. Custom PC, 4090RTX, i9 13900K, 64Gb RAM 6000MT, Win 11.
2. Custom PC, 4070RTX, i7 12700KF, 64Gb RAM 6000MT, Win 11.
3. Alienware Area51-m2, 2080Super Mobile, i9 10900K Desktop, 32Gb RAM 3600MT, Win 11.

john-brown wrote on 1/12/2026, 9:14 PM

Hi,

I was lost at the beginning with:

I have my project set to Measures and Beats, I have Grid Spacing set to 16th Notes, I have Enable Snapping, Snap to Grid, Snap to Marker, and Snap to All Events turned on, and I have Quantize to Frames turned off.

I may be way off on this, but:

First off, do you not have to define a BPM? What did you use?

Secondly, what is your project setting for fps (frames per second)?

If it's 30fps, then the normal time grid is in frames of 1/30 of a second. If your BPM is not set up such that a frame falls on the Measures and Beats grid, then you can't align the video to this grid. The time grid and the Measures and Beats grid have to match somewhere, do they not?

Turning to audio, the sample rate for video is 48 kHz, or 48,000 samples per second, or 1/48000 of a second. If your BPM doesn't match a multiple of that, then I don't see how you can align audio to the grid.

For example, if your BPM is set to 120 or 2 beats per second, then 1 measure in 4/4 time would be 2 seconds. A 1/16 note would be 1/8 of a second, if I'm not mistaken.

For audio, 48000 is evenly divisible by 8, so you should be able to align the audio to the grid.

Assuming that I've figured this out correctly, for video, the closest time grid line (frame) to 1/8s (0.125) would be at frame 4 (2/15s or 0.1333333s), however, the grids coincide at 1s intervals.

Now, try this with BPM set to something else, like 100.

Thirdly, what is the purpose for you to use the Measures and Beats grid in a video editing program? (I know, I know, Vegas started off as an audio program, etc.)

In your tests, did you use different BPM's and thus the red line showing that the event edge was not quantized shows up with some BPM's and not with others?

John CB

Vegas Pro 18 Edit, Vegas Movie Studio 16 Platinum, Magix Video Pro X17 Ultimate, Magix Vidéo Deluxe 2026 Plus, Xara Designer Pro X19, Samplitude Pro X8 Suite, Music Maker 2025 Premium, SF Audio Cleaning Lab 4, Sound Forge Pro 16 and more.