Qauntize to Frames - It's there for a reason Folks!

Grazie wrote on 11/18/2016, 2:50 AM

How long have I been using VP, and then all the way back to VF? - Don't answer . . . .

I've just spent 10 minutes of panic-enriched angst trying different FXs to get the darn thing NOT to rip my 50i fields apart and do stoopid things!

I had, of course, QtoF OFF . . . . fool. Now back ON and everything is working as should and I can NOW see just where the poor Vegas was trying to help me out. I had an Event spilling over/on the Frame Event-Horizon. Now corrected and all is good.

TAXI!

Comments

NickHope wrote on 11/18/2016, 3:17 AM

My favorite 2 internal preferences:

Dexcon wrote on 11/18/2016, 5:09 AM

Thank you, Nick, for highlightng this feature.  I didn't know about it and have now changed the internal preferences to your recommendation.  Wow!  It's great!

I recently scanned a 110 mins project using Vegasaur Audit to identify unquantized video clips, but then had to use Project Media in VP13 to go to the problem clips as identified by Vegasaur in order to do a fix.  It worked really well but was time-consuming.  Your recommendation would've been so much quicker.

BTW, the Vegasaur/Project Media method did identify all the problem clips - changing preferences didn't identify any more unquantized video clips (lots of audio clips identified though, but they don't need fixing as far as I can see because mosty they are not linked to video clip start and end points).

Thanks again.

Cheers

Conrad

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

wwjd wrote on 11/18/2016, 1:49 PM

is this all only for "interlaced" stuff?

winrockpost wrote on 11/18/2016, 6:36 PM

Grazie...you using 14 ?  If so how goes it.

ushere wrote on 11/18/2016, 7:35 PM

yes, me 2 grazie - how you finding it?

NickHope wrote on 11/19/2016, 12:40 AM

is this all only for "interlaced" stuff?

If you mean "Are these quantizing issues and preferences only relevant to interlaced video?", then no.

Grazie wrote on 11/19/2016, 1:07 AM

I'm almost certain I had QtF OFF because I wanted to do some Audio manipulation, meaning slipping across the Event horizon.

NickHope wrote on 11/19/2016, 1:21 AM

You probably know this, but it's not really necessary to turn QTF off in recent versions to edit audio if you have this preference enabled: