I think you know what I'm talking about - when you mix frame rates on a timeline, everything isn't always "cut" right on the frame - which you can fix manually by grabbing the edge of the clip and snapping it to the proper cut line.
My question is this: is there a script that will fix instances of this - clips not "starting or ending" on a precise frame?
Also - would that kind of an issue (if one clip was overlapping the other) cause something to look like a double frame in QC?
My question is this: is there a script that will fix instances of this - clips not "starting or ending" on a precise frame?
HappyOtter Free Tool--Quantize to Frames
Here's the direct link. https://tools4vegas.com/quantize-to-frames/
Make sure you implement the setting in Internal Prefrences which places a red bar at the start and end of events that do not coincide with a frame boundary. It's discussed in the thread that John referenced.
Project Inspector - free but installed with Excalibur - will also detect and fix these issues.
Thanks guys! I appreciate that.
Here is another thing:
So, this project has RF clips in it, so not everything is at the same frame rate. But here are my two questions, still:
1- Even if my media doesn't match the project frame rate, wouldn't you think that any cuts/splits you do to that media would at least fall on the frame point in the timeline? How is it "cutting" within a partial frame if quantize and snapping are both activated?
2- How is a Generated Text event not landing on a frame point?
It sounds as if "Quantize to Frames" is not ticked under Options. When "ticked", text events are inserted on frame boundaries so that no red bars will appear.
Yeah, it's ALWAYS checked. I never touch it, never CNTL+F8, and have the icon hidden on the tool bar.
That's why this is so weird.
The only quantize feature I have turned off is on audio events when there is no associated video (I think that's even a default setting).
I've encountered this on and off for years now, just chalking it up to an occasional "thing" - or an artifact after changing the timeline frame rate on a particular project. Never knew about the red bars option, so that will help a lot. Still doesn't answer how this keeps happening.
I would try toggling the Quantize to frame and see if it fixes. There been issues in the past when an update was made and even though settings indicated one operation, they were not actually active. I have never gotten frame errors on generated media regardless of frame rate.