Paul Berk
Forum Replies Created
-
George .. This little bug is inconsistent .. Grazie can’t repo and there is no solid way of producing it on every test .. but it appears for too many of us to ignore. The “math” theory of a miscalculation (rounding error) when using a non-integer frame rate, like 29.97 might be the answer. I can’t get it to appear on integer frame rates like 25 or 50.
A bug report is being filed. Hopefully this goes away in the next Build.
-
Installed Build 361 .. Tested .. and could not repo the problem. This problem seems to only exist for some of us in VP16 Build 424 — but as far as I can tell, not in any other version or build of VP ..
-
I have quantize ON ..
I’m not getting this 100% of the time I test (even on a single frame) but most of the time on a single frame on Build 424. Sometimes it happens on the first test — sometimes it takes 2 or 3 attempts to appear.
Of course, how often do you cut out a single frame?
The OP on the Vegas Forum is getting it more often and with larger cuts that generate larger overlaps too.
Very weird. Something is up. Might be a math error in the Auto Ripple routine. I haven’t tested VP16 Build 361 yet.
But I’m not getting it at all on VP15.
-
Thanks George. Are you using VP16 Build 424?
-
Your preview screen says the Project is 1920 x 1080 .. but your Project details say 1280 x 720 .. ??? .. Which is it?
-
Vegas Post .. sounds like much more FX than I need .. but that does not worry me. It’s abbreviations.
Vegas Pro is abbreviated as VP .. so what’s the abbreviation of Vegas Post? V??
Seems like it’s going to take 3 letters. That’s one more letter added. Slows us all WAY down. Bummer.
-
I think that’s “blender.org”
-
Are you talking about the Chroma Keyer FX or some other form of compositing?
-
>>Rather than use pan/crop use track motion and set up 3 tracks and place the clips on the one with the zoom you want.
That should work. Brilliant Dimitrios
