Gaps in timeline. Still having issues with black frames/gaps in video when using diffrent framerate media on the timeline. What it the easiest way to remove these gaps? Why doesent vegas know to "snap" the clips together.
SOLVED. Couldn't figure out why my "close gaps" function wasn't working I had to click on and highlight the track I wanted to be selected.
I am not sure it has to do with different frame rate. I have been using VP14 up to this summer when 18 was released. Last year coming back from vacation, I compiled a few timelapses using the footage of my Garmin dashcam. This dashcam produces a .mp4 file every minute. For a few hours of driving, I would insert couple hundreds of small .mp4 clips in the timeline and I would apply a velocity envelope. I did that countless of times in VP14 without any issues.
After my summer vacation this year, having purchased VP18, I wanted to create the timelapses using the same workflow but in VP18 instead of 14. While playing back the timeline, I found out that multiple clips had a 1 frame gap between them. Thy are not different framerate, they are coming from the same camera. I think it has to do with the audio being slightly longer than the video for some clips. In VP14, the video was given priority and the clip would be inserted without gaps in the timeline but the audio would receive a crossfade. VP18 seems to avoid overlapping completely and insert gaps when needed.
Thankfully, I found that 18 at least now has the Close Gap in the right-click menu. Doing so on the video track produce the same results I had in VP14, video have no gaps and the audio are crossfade.
Anyone else experienced this?
Yes; close gap is the workaround. BUT as always SHOULD do this by default. Even with snapping enabled it will show the clips snapped together. But if you zoom allll the way in on the time line; you can see the 1 frame gaps. I to get this issue more pronounced when using speed ramps/slowdowns and velocity envelopes.
An extremely useful tool is the ProjectAuditor in Vegasaur which checks for a myriad of problems including short gaps.
How does "Close Gaps" fix the problem? I find the same issue on a film I am editing - it's not even a full frame. It's as if quantize is off (but it isn't). But if the "solution" is to just move the next clip back to the "next frame" (as opposed to "grabbing the edge" and filling the gap by extending the next clip back (or the previous clip forward), it could do a lot of sync damage.
I'll look into the the Vegasaur Auditor report. Hopefully that will point all of them out - but I still think that I would need to go and fix them manually.
I think this has happened throughout Vegas' history. It's probably why, on occasion, when you bring two tracks together that already have fade in/fade out transitions, those fades "disappear" when you snap the two tracks together. The only way to fix that (that I found) was to manually lengthen one or the other, so they actually "connect" on a frame mark (as opposed to in the "middle" of a frame).
Like I said, the gaps show black on playback, but they aren't even a full frame in length. Not sure how this happens, but it is annoying - and shouldn't be an issue when you have quantize and snapping activated.
@Jessariah67 ... yes, I have struck the same thing with Vegas Pro over many years. Though sync/lip sync isn't so much an issue for me, I do trawl along the timeline to check each and every video event edge in the project before rendering because, every so often, there is an event edge that doesn't perfectly align with the next/preceding event - and always the 'miss' is always just a 'fracca' less than a frame. The only way to solve it is to zoom the timeline view in to around a frame or so in order to be able to shift the edge - or move the event forward - so that it exactly meets the preceding event. Often this adjustment doesn't affect the trailing event edge maybe because the actual event is longer than used on the timeline. Not doing this results in a black frame in the render.
Like in your case, quantize is active. - and always has been throughout the edit.
I ran the Vegasuar Auditor - LOTS of gaps on a 90 minute timeline with clips that are all 23.97, and have never been on a timeline (scene or master) that wasn't 23.97. This just shouldn't happen - unless it's the "23.97 vs. 24" that causes this phenomenon (kind of like the reverse of an extra day in a leap year...) - Vegas having to "deal" with that little bit of under fill.
I just spot checked the Auditor report (waiting till I have a final edit before going in and making all those adjustments), and one of the edit points had the events actually butt up against each other, but in the "middle" of a frame. So, even though there was no black being displayed, it still read as a timeline gap because they came together on an "off beat," so to speak.
There's a tool in the HappyOtterScripts Free Tool library that may be of some use to you--Quantize to Frames. It enables the user to select which "edges" to "quantize" to the nearest frame boundary. Here's a screen grab.
It can be downloaded here. https://tools4vegas.com/quantize-to-frames/
Vegas Pro has a handy method of identifying events that are not quantized to frame edges. In Internal preferences, search 'quantize' and 2 fields are filtered: 'Show unquantized event start' and 'Show unquantized event end'. Changing the Value to 'True' and hitting Apply results in the R and/or L edge of any unquantized events - video or audio - being highlighted in red.