Comments

Chienworks wrote on 10/21/2012, 11:39 PM
On the Options menu, there is a little icon to the left of the command "Quantize to frames". It will look a little darker and more "pushed in" when it's active.

Personally i don't know why the difference between active and inactive is so incredibly minimal. I find myself having to click on it several times to see it change before i can figure out which is which. Those icons really ought to have their state a lot more obvious, more like the track solo and mute buttons.
NickHope wrote on 10/21/2012, 11:53 PM
I customize my toolbar to have the quantize icon there where I can see it easily.

Also, in the internal preferences (accessed by holding <shift> when clicking preferences) you can set "Show Unquantized event start" and "Show Unquantized event end" to TRUE. Then the end of an event will be highlighted in bold red if it's unquantized. Since V10, unquantized audio has been permitted (which is a good thing), so if you have this preference set then you're likely to see these red lines a lot on your audio events. But it's an absolute godsend for video events, especially if you're working with mixed framerates on your timeline, like I often do. I wish I had found it years earlier.

I would be interested to know if this internal preference is still available in V12.
john_dennis wrote on 10/22/2012, 12:04 AM
Show Unquantized event start and Show Unquantized event end are both still in Internal preferences in Version 12. They are set to FALSE by default.
NickHope wrote on 10/22/2012, 12:05 AM
Thanks John. I'm glad they're still there :)
essami wrote on 10/22/2012, 6:08 AM
I _almost_ know the answer to this but must confirm, what does unquantisized event cuts cause to happen?
MUTTLEY wrote on 10/22/2012, 11:50 AM

Funny you should ask essami, just ran into an issue with this over the weekend, though it took a bit for me to figure out what was going on: V12 Event Pan Crop Weirdness?

Essentially, as was the symptom in that post, when not enabled you can loose precision in your edit as cuts, moving media, or changing the length of a clip may land them in between frames. As Sony puts it in the help file: "Edits that do not occur on frame boundaries can produce an undesirable visual result. For example if you split two events and move them together to create a cut, splits that are not at frame boundaries can produce a short dissolve in your rendered video."

- Ray
Underground Planet


essami wrote on 10/22/2012, 12:05 PM
Cool! Thanks for the answer! Good to know about them affecting keyframes as well. I think I might've actually have had this problems way back when... Don't have that old project anymore though but I remember solving it by redoing the whole timeline.... :)
musicvid10 wrote on 10/22/2012, 1:06 PM
Small gaps in the timeline that are caused by missed frame boundaries are one major cause of the "random frames" effect in Vegas.

The only time qtf should be turned off is when one is making precision audio edits, and then only temporarily. Then its time to lock the track to keep the audio in its place.
Former user wrote on 10/22/2012, 1:17 PM
There is an option to keep audio only edits based on samples without having to touch quantize.

Dave T2
musicvid10 wrote on 10/22/2012, 1:30 PM
Yeah, I'm still working in the dark ages (8.0c).
Former user wrote on 10/22/2012, 1:40 PM
Come on musicvid, join the darkside and upgrade to 12. :)

Dave T2
JackW wrote on 10/22/2012, 2:07 PM
Thanks, everyone.

Musicvid, like you I'm still using 8.0c. Vers. 12 in the future? Maybe.

What prompted the question was the need to slide an audio track slightly to align camera mic audio with audio coming from a house board. I got to looking at the Quantize to Frames icon and couldn't see any real difference between the "on" and "off" position.