Bizzare gradual shift in the video

peterh337 wrote on 12/2/2018, 5:24 AM

I am editing a project, described here

https://www.vegascreativesoftware.info/us/forum/any-easy-way-to-speed-up-a-clip-10x-to-100x-i-e-more-than-4x--113924/#ca704141

and at the start this is the preview

http://peter-ftp.co.uk/screenshots/20181202212961811.jpg

and then during the clip (a few hours of video) it linearly shifts, eventually ending up like this

http://peter-ftp.co.uk/screenshots/20181202102972011.jpg

I can see that having some sort of animated track motion thing might do this, but I don't

http://peter-ftp.co.uk/screenshots/20181202022982111.jpg

This is v16. I now have to throw away the project so far and go back to v14 and try to get the $199 refund, or do manual track motion on each clip after editing (the resulting video will be many clips, total maybe 15 mins) and then dump v16. I went to v16 only to get the feature which allows text to track an object in the video.

Is there some other effect in Vegas which could cause a gradual track motion shift?

The problem is that I was obviously working on the video from the start and didn't notice this problem until I had done quite a lot of work.

v16 imports v14 .veg files but not the other way round.

I have done the 2-finger startup reset, clear cache, thing.

Many thanks for any tips.

Comments

Former user wrote on 12/2/2018, 8:40 AM

You have a keyframe set on Track Motion at about 3hours and 45 minutes. What are the values at that keyframe?

peterh337 wrote on 12/2/2018, 8:55 AM

Excellent, well spotted. I deleted that (by clicking on the cross next to it).

But I never set that. The only thing I ever do in that dialog box is 1.8 degrees of rotation (because the underwing camera is very slightly off vertical despite the mount compesating for the wing dihedral) and then I zoom in 2-3% to take out the resulting dark bits in the corners

It must have come in by itself, via some corruption of the config.

I have also figured out how to upload screenshot images here :) I like that because it saves me uploading a few MB to my ftp space every time :)

Musicvid wrote on 12/2/2018, 10:08 AM

t must have come in by itself, via some corruption of the config

That's an impossible scenario; more likely just a mischevious Muse in your day, but do please post steps to reproduce if this ever happens again

;?)

peterh337 wrote on 12/2/2018, 10:41 AM

Hardly impossible - see the other thread about the velocity profile.

OldSmoke wrote on 12/2/2018, 11:58 AM

Hardly impossible - see the other thread about the velocity profile.

This may have happened if you had sync to cursor active, moves the cursor on the timeline and then changed the angel; that would automatically generate a new keyframe at cursor position. That “feature” caused me also delays in my work.

Musicvid wrote on 12/2/2018, 1:00 PM

Hardly impossible - see the other thread about the velocity profile.

This may have happened if you had sync to cursor active, moves the cursor on the timeline and then changed the angel; that would automatically generate a new keyframe at cursor position. That “feature” caused me also delays in my work.

peterh337 wrote on 12/6/2018, 2:25 PM

I have some puzzling behaviour on v16, to do with these key frames I think. I must be doing something stupid...

Basically I use track motion on the video track, to achieve a 1.8 degree rotation and a small zoom factor.

But when I go into the TM for the video track I see this

where moving the rectangle does nothing at all, but this operation works

fixes the situation.

What is going on?

AFAICS it is adding those fx (deform, etc) which creates this problem.

I never saw this in previous versions.

peterh337 wrote on 12/6/2018, 2:54 PM

I also get this, where it thinks a loop region is defined

Former user wrote on 12/6/2018, 3:19 PM

On your first picture you have 2d Shadow highlighted, which is why nothing is happening to the picture. In the second picture, you have selected POSITION.

It your 2nd post, it does not think there is a Loop Region defined, it is a checkbox to render the LOOP region IF one is defined.

j-v wrote on 12/6/2018, 3:34 PM

I also get this, where it thinks a loop region is defined

Do you see mine? 😉

............................

.................................

...........................................

But there is one.........................................

peterh337 wrote on 12/6/2018, 3:35 PM

Gosh, ok, thanks. Very subtle!

I never highlighted the 2D shadow. It must come up like that. I also never selected anything like that...

Re the loop region, there is one defined *somewhere* because if I just do a render, it finishes it in a few seconds. I have to uncheck that box.

I know how to define a loop region; I have sometimes done that. It is very obvious when it is defined. In this case v16 thinks there is one defined.

j-v are you saying that having an event selected defines a loop region?

Former user wrote on 12/6/2018, 3:44 PM

You have region defined right under your Scrubber/Cursor. There is a heavy black line, it should be a white line. If you zoom in at your cursor you will probably see a selection.(it defines a region as a selection when rendering)

j-v wrote on 12/6/2018, 3:51 PM

j-v are you saying that having an event selected defines a loop region?

No, not an event but someting else (no matter what) a had deleted.

Look 1 with just the part of the timeline with events

Look 2 with the whole timeline, with also empty space and in it a small loop region

j-v wrote on 12/6/2018, 4:00 PM

Maybe this will help you ( but the overcome all your strange things: know the program you're working with)

Former user wrote on 12/6/2018, 4:04 PM

If you still have a problem rendering just a small selection, turn the option off. It does not need to be checked unless you specifically want a selection rendered.

peterh337 wrote on 12/6/2018, 4:22 PM

j-v I cannot see a loop region in your Look 1 pic but it is obvious in your Look 2 pic.

david-tu - sure, of course, but AIUI the option should not be highlighted unless a loop region has been defined.

I did zoom right out and could not see anything to the right of the end of the project.

j-v wrote on 12/6/2018, 4:33 PM

j-v I cannot see a loop region in your Look 1 pic but it is obvious in your Look 2 pic.

If you have read the texts I gave with the screenshot I hope you see that also a part of the timeline with nothing can be looped with certain settings of preferences/editing and with her own rights the program sees that as a loop region, which it is.
I gave in the next screenshot the possibility to overcome this, so nowhere you don't want it will stay a loop region.

Former user wrote on 12/6/2018, 4:34 PM

I don't know what AIUI means. That is a checkbox. It doesn't know if a selection is made. It is just saying that if a selection is made (which it calls a region but is not actually a region), it will render only that. Don't fight the software. Just uncheck it and move on. You are stressing over something that is easily remedied.

peterh337 wrote on 12/6/2018, 4:40 PM

AIUI = as I understand it

This is I think one of the problems:

It is quite subtle that the 2D shadow gets highlighted every time I start the program.

Either I was lucky with v14, or v16 has introduced various subtle controls.

I can see how this is working - it is just a very confusing user interface in that form.

j-v wrote on 12/6/2018, 4:50 PM

Like I said it before: Know the program you are working with and if you don't understand things : RTFM
Without 2D shadow

with 2D shadow

peterh337 wrote on 12/6/2018, 5:08 PM

You are right - I never read any manual for Vegas :)

It must be 1000 pages...

If there was a course (near Brighton, UK) I would probably do it. I did a 3 day Lightroom course... the 3 days just went over the obvious features.

j-v wrote on 12/6/2018, 5:29 PM

You are right - I never read any manual for Vegas :)

Sadly that this will be the reason this was my last comment as an answer to you. 😌

peterh337 wrote on 12/7/2018, 1:58 AM

We will just have to disagree on the intuitiveness of parts of the UI of this program :)

It also behaves a bit differently on my XPS13 laptop. I did sort it eventually but it took a few minutes. One has to use the pulldown menu

and select the Position option there, and then the correct form appears. The "delete fx" route I described above doesn't work - presumably due to auto-scaling of the UI layout (the laptop is 1920x1080; the PC is 1600x1200).

This is a common UI design challenge. As the complexity grows the programmers tend to collapse checkboxes into a pulldown menu because it takes up less space. But it is also easily missed - unless you use the program regularly. In v16 the pulldown menu symbols are miniscule. And everything takes longer to do...