Which FXs to Avoid when in 32-bit?

MH_Stevens wrote on 2/25/2008, 12:08 AM

Glenn says at http://glennchan.info/articles/vegas/v8color/v8color.htm

"The 1.000 mode will break many of the existing video FXs. Video FXs will deliver different and possibly undesirable or weird results. For example, the "Studio RGB to computer RGB" preset will no longer do what it says.

2.222 will give you the old school Vegas behaviour that you are used to. In most cases, I would stick with 2.222 so that nothing wacky will happen. "

So I ask that if to avoid nesting a 1.000 project in a 2.2222 one to get optically correct composting which Vegas8 FXs should be avoided?

Comments

farss wrote on 2/25/2008, 1:27 AM

They're blue. Beware the blue FXs.

Bob.

MH_Stevens wrote on 2/25/2008, 7:57 AM

Thanks Bob: I never noticed that. As you say though, we need less science and more just how the picture looked. I think semi-amateurs like me would have been better if they had never seen V8. So much undocumented and with so many pros confused it brings with it a paranoia that is maybe not justified.

GlennChan wrote on 2/25/2008, 10:21 AM

So I ask that if to avoid nesting a 1.000 project in a 2.2222 one to get optically correct composting which Vegas8 FXs should be avoided?

Ack, I don't think I was that clear in my article. I did not mean to suggest that you shouldn't avoid those particular FX. Do use them. And in 2.222 projects, those effects will behave in the same way as previous versions of Vegas.

What I'm saying is that in 1.000 projects, FX will behave differently and in some cases that behaviour is probably not what you want. To say that the filters are broken is probably misleading. Sometimes 1.000 is a good thing, sometimes it is a bad thing. I would simply prefer to work in a 2.222 project... it's safer, nothing wacky will happen, etc.