Chroma keys on bezier masks

EarthGuest wrote on 8/11/2019, 2:10 AM



Using the bezier mask curve tool to cut out a part of the screen, I then cannot seem to be able to add any chromakeys to the "cut out"..

I tried to work around it by soloing the bezier masked channel and rendering to new track...


This renders the cut out with a black background and not a transparent one...

(and it renders without fx, and keeps the chromakey on the track.. lol-- also, I cant insert 2 chromakey fxs on one track... - even if they are different chromakeys from different companies... )

I wonder if there is a way to accomplish this... (I mean, there has to be, right;) )

something lilke:

Bounce clip , or, flatten all fx to clip... or , the most preferable thing would simply be to insert a chromakey after the bezier mask effect...

How do you do it?





Marco. wrote on 8/11/2019, 3:28 AM

What exactly is the problem when you use the Chroma Key FX after having applied a Bézier Mask? This works fine here.

EricLNZ wrote on 8/11/2019, 5:19 AM

Try placing the Chroma Keyer FX before Bezier Masking (i.e. to the left) in the FX chain.

EarthGuest wrote on 8/11/2019, 11:09 AM

Hey guys=)


Thanks for your help.


It does not work here....


I cannot put a bezier mask and a chromakey on a track simultaneously...


-I just updated vegas and cleared/refreshed settings/cache with ctrl+shift+start vegas...

(build 142)


Does seem a little odd :P

This update is not doing it for me... :/


This is on an updated windows 7 machine...

..Yeah , its kind of weird...oh, weird! hello! ummm... Oh my goodness! Hello! ew! Strawberries! um.... yeah.. it was weird...

Marco. wrote on 8/11/2019, 11:10 AM

"I cannot put a bezier mask and a chromakey on a track simultaneously..."

Why not? What exactly happens?

It's hard to help if you don't tell what's going wrong on your system.

EarthGuest wrote on 8/11/2019, 11:21 AM

Hold on, lemme make a quick "visual reference" bb in a shake of a lambs tail.. =)

EarthGuest wrote on 8/11/2019, 11:54 AM

um, nvm that quickness thing... I needed to blur out my email and rendering this thing is taking quite a long time (cpu render)...

um.. In like 20


edit: my system is updated, clean and all original... everything works.. I do not know why vegas is acting up in this way... everything was fine before the 142 update... it wont even close properly in the system...anyways... since this program is the only "bugginess" on the system, I shall use some deductive reasoning (thanks sherlock) , and deduce/conclude that the 142 build is the bug and that is what is wrong with my system ;) lol.. anywho... Ima post the vid asap ;)

EarthGuest wrote on 8/11/2019, 12:41 PM

ok, here is what it looks like:


-> about the two fx on one :

-maybe it is my fault because the settings were reset and I might have overseen something or am doing something wrong?... (all i am doing is inserting 2 fx after eachother - I noticed that this did not stop at the keyer, but also other fx.. - everything was fine in the last build i was using.. (since i am an audio guy, i only use it when i must)

->about the long loading on creating windows - clearly vegas bug

->about the process not closing in task manager and making new dupe processes as I open/close vegas - clearly vegas bug.


I will give Vegas the benefit of doubt though, and I will reinstall the whole shebang.

(I was updating windows as I was installing the new build the other day)


bb after a re-install..


Thanks for all your help =)




EarthGuest wrote on 8/11/2019, 1:03 PM

yep. Vegas build 142 should not have been released.

Vegas is the bug here. everything else just works... except vegas.

(host process not closing, long "creating windows", cannot open multiple fx in sequence)

(while it is "creating windows, nearly all of my cores are at complete "idle" and no cpu is being used btw)


I mean, this is surface stuff... basics...I do not wanna know what all does not work when one goes in deeper :/


I will gladly accept "user error" , but I am sure this is Application error....


"sigh"... Was to be expected though, right? ;)

Marco. wrote on 8/11/2019, 2:32 PM

I think it is because you miss to click "Add" before you click "OK" in the Plug-in-Chooser window..

EarthGuest wrote on 8/11/2019, 2:55 PM

Hi Marco =)


Great, thanks =) You got it!=)


- I did not realize that one had to press "add" for additional fx... - I just thought that one can use "FX+" and "ok"...

phew =)


ok... 1 user(n00b) error, 2 application errors at this point...


Remaining errors:

-Vegas processes not being closed in task manager (vegas not shutting down properly - every instance sucks lots or ram mind you;) )

-Long wait time while "creating windows" on load


Thanks again, everybuddy =)


edit: i will edit this thread and make a new thread for the application errors;)

Marco. wrote on 8/11/2019, 3:40 PM

These application issues are know ones.