“freeze frame at cursor” doesn't work completely

Momsy wrote on 9/24/2024, 9:47 AM

Hello,
This is the first time I've posted here, and I came to ask a question related to the video function: “freeze frame at cursor”.

I've encountered a problem with the latter. I know how to use this video function and I've already used them successfully.
But lately the freeze frame doesn't work completely.

When I create a freeze frame tape, a few minutes later, an extra frame is added to the tape that is supposed to remain frozen.

I don't know if I've made myself clear, but for those who have, the problem I've described doesn't sound like much, but when you're a maniac like me, an extra frame on an image that's supposed to remain frozen is very unattractive.
So there you have it, those of you who took my comment seriously, if you have an answer for me that would be most welcome.

Thank you for reading.

Comments

Steve_Rhoden wrote on 9/24/2024, 6:27 PM

Is this happening in the latest version of Vegas Pro 22 ?

Also check and see if the Quantize to frames feature is enabled and if that affects it or not.

EricLNZ wrote on 9/27/2024, 5:46 AM

When I create a freeze frame tape

@Momsy I'm puzzled but it's probably my ignorance. What sort of tape are you producing?

Dexcon wrote on 9/27/2024, 6:46 AM

I've been unable to repro so far in Vegas Pro 22 build 122. This includes using a video event deliberately set as unquantized at both start and end frame edges, changing the project properties to a different fps rate than the media's fps, as well as using variable frame rate media from a phone, and setting the freeze-frame at cursor at the beginning of the video event and alternatively mid-event - as well as waiting several minutes to recheck the event's end frame.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

jetdv wrote on 9/27/2024, 9:08 AM

@Momsy, could you please share a screenshot showing the envelope as well as the VEG file itself (no media should be needed.) I have not seen any issues any time I've used the "Freeze Frame" option.

Robert Johnston wrote on 9/27/2024, 2:25 PM

@Momsy I suppose that could happen if your project frame rate doesn't match the media's frame rate, and possibly also if resample is on. If you step backwards, you might see the what looks like the same frame. So for example, if at 9;12 you freeze frame, then when you step backward, you see 9;12 in the preview window, but the timeline cursor is at 9;11. It would look like 9;11 and 9;12 are the same frame. This happens if project frame rate is at 24 fps but the media frame rate is 29.97 and optical resample is on.

Intel Core i7 10700K CPU @ 3.80GHz (to 4.65GHz), NVIDIA GeForce RTX 2060 SUPER 8GBytes. Memory 32 GBytes DDR4. Also Intel UHD Graphics 630. Mainboard: Dell Inc. PCI-Express 3.0 (8.0 GT/s) Comet Lake. Bench CPU Multi Thread: 5500.5 per CPU-Z.

Vegas Pro 21.0 (Build 108) with Mocha Vegas

Windows 11 not pro