@ALO

A similar issue was covered recently in this thread:

https://www.vegascreativesoftware.info/us/forum/unquantized-frames--135242/

John is there a version of that thread for dummies?

:)

You don't need to know the technical jargon, just what DMT3 asked... "what setting are you using for the timeline ruler (smpte drop frame, non- drop, etc?)"... you need that setting to match your media.

OK, let's just assume the GoPro footage is correctly 29.970 as indicated in media properties. If I ensure "Quantize to Frames" is checked and "Show Unquantized Event Edges", I expect Vegas to show me any event (clip) endings that don't fall on a frame line. Instead, when I put a GoPro clip on a 29.970 timeline with ruler set to NTSC drop, Vegas highlights *every* event edge with a red line -- even those that are quantized. So I can't use that to find non-conforming event edges, because it highlights everything.

What's going on here?

I don't think we'll know for sure until you upload a sample of your source to Drive or Dropbox.

OK, I was mistaken: the GoPro files are ending in between frames. It's just so close you have to zoom in all the way to see the misalignment. So Vegas is correctly flagging them with the red edge.

Any ideas on how to handle this? Having to manually micro-quantize every clip I put on a timeline would be a lot of work!

Here's a guilty file if you want to play around with it:

https://drive.google.com/file/d/1PPnH-SbBQk_SEn8iR_-GbdTIRCgdaZMX/view?usp=sharing

This can certainly be done using a script. I'll work on creating a tutorial that will show how this is done.

@ALO

I'm not seeing any black gaps or quantize warnings with the media that you uploaded. I do see that the last frame appears to Vegas as being one straw short of a full load per the location of the notch. Vegas Pro 19-550 appears to handle that without drama.

I downloaded the file, dropped it on the timeline, and the end of the clip is just slightly short of a frame (and shows the red border). My "Project Inspector" plugin was designed to check for one starting off frame and correcting it so I just now modified it to hand ending off frame as well and it does work well - just shortens it to the end of the previous frame. I'll pull some of that code out and create a new tutorial for a script that will fix this by making it the slightly shorter amount.

Here's an image with frame 9:08 to 9:09 highlighted and you can see the video is just short of 9:09 and the red highlight is showing (Options - Quantize to Frame - Show Unquantized Event Edges)

@jetdv

Are you using Vegas Pro 19-636? I'm using 19-550 and I'm not seeing your result.

@john_dennis - yes on build 636.It's "just slightly" shorter than the frame.

@jetdv

I looked at other GoPro samples at 29.970p that exhibit the same behavior. The ones at higher frame rates don't appear to have the issue for my small sample. The samples from my cameras have, so far, ended on a frame boundary when the ruler is set to match the file properties. With mixed media, all bets are probably off.

[Techno-Philosophical Poser]

With shutter press to start and stop, how many camera files never get trimmed by even one frame?

[/Techno-Philosophical Poser]

@jetdv

"It's "just slightly" shorter than the frame."

As shown in my demo video, I saw that behavior in Vegas Pro 19-550, but it wasn't flagged with a red warning and didn't appear to cause a black frame problem.

@john_dennis it also did not show a black frame problem that I could visually see on my system either but it *did* show the red line AFTER I went to Options - Quantize to Frames - Show unquantized event edges and turned that option on.

Yes, it's visible when you enable "show unquantized event edges". My guess is this doesn't cause a visible black gap until the alignment of a bunch of these clips together interact (randomly) to create a gap at a frame line. Ie, if you put a hundred such clips on the timeline, eventually somewhere the frame discrepancies add up to create a black gap.

It would be useful if Vegas could flag those gaps only, but I don't see any way to do that.

VideoRedo was designed to take care of things like this; instead, it just hangs.

My Project Inspector plugin handled ones that did not start on a frame boundary but not ones that did not end on a frame boundary. I've modified it so that now it does work for ending ones as well but it has not been uploaded. I will create a tutorial for this, though, on both how to detect and how to fix.

This is a malformation on the encoding end, right? My GoPro is, for whatever reason, producing a non-standard stream?

It appears, for whatever reason, that GoPro wants the video to quantize to exactly match the end of the audio stream. Not sure what logic led to that decision, as we usually find it the other way around.

Everyone thanks for the help!