Comments

mdopp wrote on 4/19/2005, 10:13 PM
Yep, same here. Looks like another broken filter/effect in Vegas 6a.
Zion wrote on 4/20/2005, 5:16 AM
Any word from Sony on this Problem?

Seems to be alot of problems with the transitions an FX that was
not there before in V 5.


ZION
SonyIMC wrote on 4/20/2005, 6:51 AM
We repro this. Unfortunanetly build 779 of the Video FX plugins slliped trough our hands with some very simple but far reaching bugs.

Known issues that pertain to this problem

1. Sharpen filter blurs instead of sharpens (fixed internally)
2. Film Effects Grain is static when keyframed (fixed internally)
3. Zoom out zooms in instead of out (fixed shortly)

Let us know if there are any more seemingly related issues.

Thanks
Ivan Calderon
Vegas SQA Lead

.Alex wrote on 4/20/2005, 7:03 AM
Thanks for the update Ivan.

Great to know that you have identified the problems and are working on a fix.

Do you have any timescales for when a release can be made that corrects these?

.Alex
BillyBoy wrote on 4/20/2005, 9:23 AM
Hey Sony....just wondering.... the competency of beta "testers" that let features working properly in previous versions to act in reverse and NOT BE NOTICED?

A sharpen filter that blurs?
A Zoom out that zooms in?
FX filters than don't track effects applied if keyframing enabled?

WHAT ELSE IS BROKEN?

These are things that shake the confidence of potential consumers. If you let the little things slip by after passing through endless beta TESTER cycles (you did do that right?) then what does that say about larger things still undiscovered by real world users?

I was on the fence if or not I would upgrade. With careless things like these showing up by what seems like the hour you helped make up my mind and I bet the mind of many. No upgrade for me. Version 6 seems badly broken.
Chienworks wrote on 4/20/2005, 9:31 AM
Ivan, i had had a chat with Matt about this already so i'm not sure if you've seen it yet, or if it's even related, but apparently there's a bug in Light Rays that calculates the "intensity" as a fixed number of pixels rather than proportional to the frame size. In other words, what looks good in a small preview window becomes almost unnoticeable in an HD frame because the effect is proportionally diminished.
Zion wrote on 4/20/2005, 9:50 AM
Thanks for confirming Ivan!

Fogive my ignorance Ivan but what do you mean fixed internally.

Is there and update already?

ZION
Chienworks wrote on 4/20/2005, 11:20 AM
"Fixed internally" means that they have the problem solved in the version that the programmers & inhouse testers are running, but that the fixes haven't been released to the public yet.

I think i've found another bug, this time with the height map. The compositing or fade level on the "height" track doesn't seem to have any effect throughout most of the range. At 0 it seems to be zero, but somewhere around 1% the effect jumps to 100%. This makes it impossible to smoothly fade in or out the height effect by fading the track. Also, when crossfading from one event to another, the effect remains constant until the end of the transition, then instantly jumps to the next event as if it was a bump cut rather than a crossfade.

It seems to me that Vegas should be computing the results of fades & such before using the result as the height map, but this isn't happening. I'm quite sure this works fine in version 5.

Ivan or Matt, is there somewhere i can send you folks a tiny .veg file that shows this problem?
Zion wrote on 4/20/2005, 1:13 PM
Thanks for the info chienworks.



ZION
chaboud wrote on 4/20/2005, 1:18 PM
I can reproduce it here and am looking into it.

Thanks,
Matt
Chienworks wrote on 4/20/2005, 1:43 PM
Matt, if you're talking about the height map thing, i've had a few emails back and forth with Ivan about it. Turns out i was mistaken and this is the way Vegas 5 worked too. On the other hand, i wouldn't mind seeing this fixed. :)

Thanks!