Per the following video:
Quantize To Frames = Active
Cursor set to literal location using Selection Start Window
Media event was split using "S" key
Media event was not cut at the expected selection point.
what setting are you using for the timeline ruler (smpte drop frame, non- drop, etc?)
Vegas Properties are set to Time and Frames.
I checked the camera settings and it is set to Drop Frame.
Media
General Complete name : E:\2022-04-22 Baseball Game\2022-04-22-003.MP4 Format : XAVC Codec ID : XAVC (XAVC/mp42/iso2) File size : 2.37 GiB Duration : 3 min 26 s Overall bit rate mode : Variable Overall bit rate : 98.4 Mb/s Encoded date : UTC 2022-04-23 00:36:08 Tagged date : UTC 2022-04-23 00:36:08 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L5.1 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 2 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 3 min 26 s Bit rate mode : Variable Bit rate : 96.5 Mb/s Maximum bit rate : 100.0 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.388 Stream size : 2.32 GiB (98%) Encoded date : UTC 2022-04-23 00:36:08 Tagged date : UTC 2022-04-23 00:36:08 Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : avcC Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 3 min 26 s Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 37.8 MiB (2%) Encoded date : UTC 2022-04-23 00:36:08 Tagged date : UTC 2022-04-23 00:36:08 Other Type : meta Duration : 3 min 26 s
Yeah, they need to match for accuracy.
@john_dennis Yep, same when the timeline is set at Time and Frames, 30fps media cuts/splits fine but i get the same result as you with 29.97fps, If i set the timeline to SMPTE Non-Drop (29.97fps Video) 29.97fps media cut/split fine, I haven't tried SMPTE Drop (29.97fps Video)
PS i was playing with this while you uploaded , watching your vid just learnt right click on the time shows the ruler 👍
@Former user that is because the math is wrong between time and frames and smpte. if your original is drop-frame, it is best for your timeline ruler to match (of if non-drop, it should match). Most cameras flag as drop-frame because that is the most accurate for 29.97 fps.
Engage Quantize to Frames
means the movement of cursor and/or video event goes frame-wise if enabled, i.e. when you wannna cut you'd firstly let your cursor snapping to a framehead/end, NOT a certain time point.
I always use Ruler Time&Frame.
@DMT3 Just been reading 🤯😂 good learning tho
Google searched - drop-frame vs. non-dropframe timecode - pdf quote - 'Also, when we talk about being 1.8 frames ahead or behind, we are referring to the frame numbering scheme being ahead of real time. It does not refer to the video track being ahead or behind the audio track; audio that drifts away from its video is a different issue,' 👍
https://www.connect.ecuad.ca/~mrose/pdf_documents/timecode.pdf
@Yelandkeil then you are sacrificing accuracy of timing, not editing but program length if your source/output is 29.97. This becomes more of an issue when the program is long (hour or so). Your program length could be off about 4 seconds over an hour. For a TV broadcast this is important, for youtube not so much.
@DMT3, yes.
A short advertisement in the TV broadcast could lost 4-10 frames that time. It WAS a NTSC problem.
In our PAL world never happened, though now I use 59.94fps for smooth motion.
@Yelandkeil one of the several problems with NTSC. 😉
This article on the subject is succinct.
"Sometimes people will refer to 29.97 fps as “30 fps,” which can cause confusion. Problems may occur any time source footage is captured at the wrong frame rate. It is better to be accurate and write NTSC (ND or NDF) than to refer to “30 fps.” Most professionals will know all NTSC is 29.97, but accuracy can prevent mistakes. PAL countries do not experience this issue since the video frame rate is always 25 fps. The high-definition (HD) formats follow the same rules as standard definition and are listed below."
I'm not completely certain there's not a typo in the text, though.
For many years, I've experienced video events sometimes missing the Quantize frame edge particularly after using the Ripple tool (all tracks etc). Quantize to Frames options were both checked 'on' and the ruler has always been 'Time & Frames'. A difference is that the projects have all been 25 fps so no drop-down issue is involved I would have thought.
I'm not completely certain there's not a typo in the text, though.
What typo are you referring to?
@Dexcon drop frame and drop down are different issues, and there is no DF in PAL. If you use TIME/FRAMES with 25fps footage how does it know? Put your cursor at a position on the timeline like 01:39:00 and switch between time/frames and SMPTE 25fps and you will get a different time.
Like I said, for accuracy the ruler should match your footage or else the math for rippling etc will be wrong.
“NTSC (ND or NDF)”
Yeah should be DF or NDF. heh, good catch.
Put your cursor at a position on the timeline like 01:39:00 and switch between time/frames and SMPTE 25fps and you will get a different time.
I've just tried that and the time stayed the same; however, there was a subtle difference in the time display.
Time & Frames 00:50:45.00
SMPTE EBU (25 fps, Video) 00:50:45:00
T&F has a full stop between 45 and 00, but SMPTE has a colon between 45:00.
I'll leave it on SMPTE and see how that works with rippling. Thanks.
If you stop in on a zero frame then they do match, my error in example. Stop it at frame 12 and see what happens.
Stop it at frame 12 and see what happens.
I'v tested that at 4 different points on the timeline using both odd and even frame numbers - no change at all in the time between T&F and SMPTE, only the full stop/colon display being different. I wonder if the change in time is an issue with NTSC but not with PAL.
My mistake. If the project is set for PAL then the ruler time/frame is correct. Curious to see if the SMPTE fixes your boundary issues.