Masking Questions for Vegas

NS · Post by NS » Sat Aug 11, 2007 6:31 pm

Well.. Instead of chroma keying, you could just feather the Mask itself.

Kero777 · Post by **Kero777** » Sat Aug 11, 2007 6:53 pm

NerdStrudel wrote:Well.. Instead of chroma keying, you could just feather the Mask itself.

That idea is better than chroma keying, but I was thinking more of like a solid black border, or close to it (hopefully?).

*Knows she's going to have to resort to Photoshop*

NS · Post by NS » Sat Aug 11, 2007 6:55 pm

Not sure....... You could play with some settings.. or putting solid black color with it.. or something Idk.

Kero777 · Post by **Kero777** » Sat Aug 11, 2007 7:34 pm

NerdStrudel wrote:Not sure....... You could play with some settings.. or putting solid black color with it.. or something Idk.

Hey, that doesn't work too bad at all! Thanks, NerdStrudel!

What you have to do is: put solid black color underneath your mask, copy the key frames from your mask onto the black color picture underneath it. Then just feather the black out on the black picture.

Does anyone know of any easier methods? I have a tendency to go through with something and then someone will tell me that there is a way that is a lot easier. Lol.

Kero777 · Post by **Kero777** » Sat Aug 11, 2007 8:08 pm

Oh no!

Not this again. My old computer used to pop up with this message if I did more than one key-frame mask. I just got it for the first time on my brand new one. Please tell me someone knows how to fix this/what causes this. I get this error when I try to mask and then Vegas shuts down:

Does anyone know? *Crosses fingers*

Kero777 · Post by **Kero777** » Sat Aug 11, 2007 8:14 pm

Another one... How could I have forgotten this ugly one?

I don't know if I can work on this project anymore now... It just shuts out...

BasharOfTheAges · Post by **BasharOfTheAges** » Sat Aug 11, 2007 8:20 pm

Those are memory access violations... I don't really know vegas that well, but if there is a way you can delete the cached renders that might fix your problem.

Kero777 · Post by **Kero777** » Sat Aug 11, 2007 8:28 pm

BasharOfTheAges wrote:Those are memory access violations... I don't really know vegas that well, but if there is a way you can delete the cached renders that might fix your problem.

I'm not sure how to do that. To be honest, I'm not even sure what that means.

You said you used AE, right? Do you know how to do it in AE?

BasharOfTheAges · Post by **BasharOfTheAges** » Sat Aug 11, 2007 8:54 pm

There should be a project file folder with lots of rendered viedo streams that are somewhere other than where your video is stored (adobe programs do it in their folder system on the drive you installed the software on - not on their instalation directory, but another directory that houses project files). Delete those and rerender the video in vegas.

Kero777 · Post by **Kero777** » Sat Aug 11, 2007 9:15 pm

BasharOfTheAges wrote:There should be a project file folder with lots of rendered viedo streams that are somewhere other than where your video is stored (adobe programs do it in their folder system on the drive you installed the software on - not on their instalation directory, but another directory that houses project files). Delete those and rerender the video in vegas.

I really appreciate your help. Unfortunately, I'm unable to find these files.

Do you think if I lowered my Dynamic RAM Preview it could help? I might try that...