VEGAS and playhead position

Comments

gary-rebholz wrote on 8/4/2020, 4:02 PM

I'm hesitating to jump into this discussion because I may only make things more confusing. Marco has explained the reason for Quantize to Frames perfectly. We give you the option to turn it off and cut as freely as you want against the best advice.

The reason to be very careful cutting with Quantize to Frames turned off is that the result of your cut will be unpredictable and could result in a bad edit. When you cut between two video frames, you don't know whether that cut will be interpreted during render to happen at the frame before the cut or the frame after the cut. As Marco points out, there is no "in between frames" cut in the final video. The cut has to be pushed to one frame or the other in the final render. So, in short, when you cut video between frames you simply don't know what you're really going to get, and you could get an unexpected hole in your video or some other (unpredictable) problem.

Now, OP has been happy with his results cutting that way, and if that's the case, keep doing what you're doing. It's just better for you to do it with the full information that Marco and others have given. Your results are unpredictable, but it's up to you to decide to live with that unpredictability or not.

And in the end, the thing you initially posted as a problem is not a problem. VEGAS always shows you the frame you are on in the timeline. If Quantize is off and you are between frames, VEGAS considers you (rightly) to be on the current frame (which you interpret as the previous frame, but it is not because a frame lasts for the duration of time between its beginning frame boundary and the next frame boundary). This simply will not change because the behavior you're asking for is incorrect behavior where VEGAS would be showing you something other than the frame you're actually on.

Good news: you are free to edit just as you want! Bad news (for OP): VEGAS will continue to show the right thing (the current frame), not the next frame.

Finally, just for the record, if you are making an audio-only edit (that is, you're editing just an audio event) VEGAS automatically ignores Quantize to Frames and lets you edit freely. So, even with Quantize to Frames on, you can hold your Shift key as you trim the audio event. The Shift key temporarily overrides grouping and you are now able to edit the audio event to any location in between video frames.

pierre-k wrote on 8/4/2020, 6:00 PM

Thanks to all.
It is clear to me. You can delete or lock the entire discussion.

vkmast wrote on 8/4/2020, 6:34 PM

This discussion has given valuable information and should not be deleted.

adis-a3097 wrote on 8/4/2020, 6:38 PM

:) There was a time when scientists believed the atom was the smallest thing!

Oh yeah? When was that? When they were believers? :)

A-tomos never meant the smallest nor thing, just partless. Atom, in Greek, is kinda what individuum is in Latin.

 

BTW: http://dydaktyka.fizyka.umk.pl/Wystawy_archiwum/z_omegi/atomos1.html

:)

Yelandkeil wrote on 8/4/2020, 7:17 PM

the most beautiful thing is, nobody holds up pierre-k to mockery but wanna help him with warm-hearted words. 
I'm touched. 

ASUS TUF Gaming B550plus BIOS3202: 
- Thermaltake TOUGHPOWER GF1 850W 
- ADATA XPG GAMMIX S11PRO; 512GB/sys, 2TB/data 
- G.SKILL F4-3200C16Q-64GFX 
- AMD Ryzen9 5950x + LiquidFreezer II-240 
- XFX Speedster-MERC319-RX6900XT <-AdrenalinEdition 24.12.1
Samsung 2xLU28R55 HDR10 (300CD/m², 1499Nits/peak) ->2xDPort
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

Lumix DC-GH6/H-FS12060E: HLG4k60p, AWBw, shutter=100, ISO=auto (250 - 6400)
DJI Mini4 Pro: HLG4k60p, AWB, shutter=auto, ISO=auto
HERO5: ProtuneFlat2.7k60pLinear, WB=4800K, Shutter=auto, ISO=800

Win11Pro: 24H2-26100.4351; Direct3D API: 12.2
VEGASPro22 + XMediaRecode/Handbrake + DVDArchi7 
AcidPro10 + SoundForgePro14.0.065 + SpectraLayersPro7 
K-LitecodecPack17.8.0 (MPC Video Renderer for HDR10-Videoplayback on PC)