Interesting

I placed the files in created Documents\Vegas Application Extensions folder and run VP twice.

but I don't see it in my VP19 extensions...🙁

Looks very interesting and easy to handle, will give it a try.

Interesting

I placed the files in created Documents\Vegas Application Extensions folder and run VP twice.

but I don't see it in my VP19 extensions...🙁

 

Same issue here in VP20, extension doesn't show up.

@jetdv has created 8 similar tutorials. http://www.jetdv.com/?s=easing

I had wondered if he had built that based off of my tutorials. If he did - GREAT! The functionality looks very similar. The interface is cleaner but my purpose was to show the process, not make a perfect interface.

In my Vegas 20 and previous Vegas that friends of mine tested and it's working perfectly.

Thank you! I followed your video, now I have it .

I don't know what went wrong before.

*Now I need to learn how to use it.

@FayFen Great!
@3POINT Would following the video I posted solve your problem as well?

Like @3POINT, I too do not see it in Extensions. I had to create the folder in Documents, extracted to that folder 4 files, started VP20 B370 and it's not there. Decided to try VP18 B527, and it doesn't show up there either.

@Reyfox @3POINT Please try pasting the files in this path here to see if it works.

C:\ProgramData\Vegas Pro\Application Extensions\

To confirm, you're adding the folder into "My Documents" - wherever that happens to be.

If you're on Windows 11, there's a differences between [user name]\Documents (which won't be seen by VEGAS) and [user name]\OneDrive\Documents (which will be seen by VEGAS)

That's why I always say to put custom commands in:

[My Documents]\Vegas Application Extensions

and regular scripts in:

[My Documents]\Vegas Script Menu

To confirm, you're adding the folder into "My Documents" - wherever that happens to be.

If you're on Windows 11, there's a differences between [user name]\Documents (which won't be seen by VEGAS) and [user name]\OneDrive\Documents (which will be seen by VEGAS)

That's why I always say to put custom commands in:

[My Documents]\Vegas Application Extensions

and regular scripts in:

[My Documents]\Vegas Script Menu

Exactly, the extension has to be placed in your windows default documents folder, whatever you have defined. For example, I have windows installed on local disk C. However, for the windows library, I defined the folders on local disk D.

@jetdv your suggestion worked. I don't use OneDrive, but once I put the extensions there, it appears.

@Reyfox I don't either. But in Windows 11, that's where the "true" [My Documents] folder is located - even though there's still a folder with the same name listed under [user name].

So that's actually an error in his installation documentation. That used to be correct - until "one drive" happened. Now you have to literally specify:

[My Documents]\Vegas Application Extensions

@m3lquixd I put the whole extracted folder in the Vegas Application Extensions Folder. After putting just the .dll's in that folder, I have access in Vegas to the extension. Thanks.

@3POINT 👏👏

@m3lquixd After playing a few moments with this extension, some thoughts:

It generates between two existing keyframes a lot of extra keyframes to achieve a specific curve (same as Vegasaur Tweener), disadvantage is to change the generated curve you have to delete those keyframes before you can generate a new curve. The effect of the curve is visible only after applying it.

Generating curves is only possible for pan/crop or TrackFX, not for Event FX.(as far as I saw)

I can achieve same Bezier curves directly in Vegas, just between TWO keyframes when using Vegas Bezier curves, advantage you can make changes while watching/looping the effect of the curves changes in the preview:

A lot of image animations still feel 'easier to do' via pan/crop rather than, say, Picture in Picture FX.

So this tool can be helpful for 'smoothing' the pan/crop keyframes. - but agree with the disadvantage you mentioned.

@3POINT Your observations are true. However, the native vegas curves are not very good to work with, because when we apply very large parameters the keyframe goes out of our field of view, making it impossible to create the curve. The advantage of vegas flow is also being able to use the same curves without having to create them every time you animate.

disadvantage is to change the generated curve you have to delete those keyframes before you can generate a new curve. The effect of the curve is visible only after applying it.

@3POINT I also gave this feedback to the creator, it would really be interesting to be able to preview the animation before applying it.

@set I think PiP is extremely superior to Pan/Crop because we can animate the parameters individually. And worse, the vegas team still needs to add the anchor point parameter.

Probably they have to create something like 'dummy' reference for 'preview simulation' inside the UI interface of the plugin before really apply the keyframes to the VEGAS keyframe timeline.

Aside from that, make usage of 'undo' function as it only one command: