Rendering Not Matching What I see in Timeline/Monitor


john_dennis wrote on 11/24/2022, 3:09 PM

Assuming the frame before the defect is good and more or less equal to the defective frame except for the defect.

The Velocity Envelope at 0 holds the good frame until the Velocity Envelope returns to 100% after the defective frame. Instead of patching the bad frame, you use the preceding frame.

My main system:
Motherboard: Asus X99-AII
CPU: Intel i7-6850K
GPU: Sapphire Radeon RX480-8GB
RAM: Corsair Dominator (4 x 4 GB) DDR4 2400
Disk O/S & Programs: Intel SSD 750 (400 GB)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: Corsair Hydro series H115i
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Crystal Sound 3 on motherboard. Recording done on another system.
Primary Monitor: Asus ProArt PA248q (24" 1920 x 1200)
O/S: Windows 10 Pro 22H2, Build 19045.2130

Camera: Sony RX10 Model IV

prejto wrote on 11/24/2022, 4:07 PM

Thanks John, I think I understand now. Just to confirm that this is what I would do.

1. Split the video after the bad frame. 2. Place the cursor on the frame before the defect 3. Set that frame to velocity = 0 Done? Hopefully the video won’t be too jerky!

jetdv wrote on 11/25/2022, 8:12 AM

As I previously indicated (but I just used the "Freeze Frame option found in the newer versions). Manually set the two points on the velocity envelope.

prejto wrote on 11/25/2022, 1:44 PM

Thank you jetdv. All clear now. I will try this out ASAP!