Strange behavior with plugins in video bus

aversis wrote on 1/26/2012, 5:22 AM

Hi,

I had a full project, where I added some levels correction to the overall video bus (or whatever it's called). All was fine untill I noticed I was working with the 32 bit vegas while I am on a 64 bit machine.

I downloaded the latest version in 64 bit, and installed it.

Suddenly when I opened the project, I noticed some strange colors in my footage. After some testing, it had something to do with a filter in the master bus.

I wanted to reproduce it, so started with a fresh project with one clip. It's a very short clip, which I simply faded. I then applied a levels filter to the master video bus, note that I didn't even touch the levels settings for it to go wrong!

Here is the clip without the effects on in the master bus:

It just fades to black.

And here is the same clip with levels filter without any tweaked settings (so it should look the same...):

The fade happens on the last 2-3 frames, and is completely messed up.

I already went back to my old 32 bit installed version, but that doesn't help... I am very sure that this wasn't the case before my new installs, because in the project I was working on, this strange behavior is very noticable so I definately would have seen it. (i also already rendered that project and there is nothing wrong with that file).

Any idea what could cause this?

Thanks,

wouter

Comments

farss wrote on 1/26/2012, 5:49 AM

"Any idea what could cause this?"

Not directly but I found a post on another Vegas forum that suggests that installing both the 32bit and the 64bit version of V11 can cause problems. In the posters case it related to crashing but other things could go awry if the code is getting tangled.

Bob.

megabit wrote on 1/26/2012, 5:57 AM

This looks to me like the same bug Paul is describing in this thread here:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=796824&Replies=23

Does it occur when you turn GPU acceleration off?

Piotr

aversis wrote on 1/26/2012, 6:18 AM

Ok that is exactly what is happening here. I now deinstalled every instance of vegas I had. It was fine this morning with my older, 32bit version of vegas 11, the only thing is I am not sure which version that was.

Will try to install again and see what happens.

Thanks for the help!

aversis wrote on 1/26/2012, 6:30 AM

Just went back to vegaspro11.0.424_32bit, and the problem is gone.

Also tried vegaspro11.0.510_32bit, which had the same problem. Turning off GPU helped, but not completely. There still were issues, altough not very apparant.

megabit wrote on 1/26/2012, 6:34 AM

Please file a bug report!

Piotr

farss wrote on 1/26/2012, 6:44 AM

So by that can we assume that having both the 32bit and the 64bit version installed could have been the problem?

Sorry to hassle you over this but if that is the case it appears to confirm what others elsewhere have found and it needs to be reported but the report needs to be very specific. This kind of bug which may be something as simple as a DLL being overwritten when it shouldn't is something that could easily be missed by SCS.

Bob.

paul_w wrote on 1/26/2012, 7:35 AM

Yes we have the same issue here as pointed out in my other thread.
However, i have not tried rolling back to a previous update yet so thats my next action.
Note however its not just in the main video buss, it also happens to track FXs too. Only the actual clip event FX on the TL seem to be ok (see video).

Please do submit a ticket to SCS. I did but the more the better. You may have some information that i dont.

Paul.

paul_w wrote on 1/26/2012, 7:37 AM

Bob, well its true i do have both 32 and 64 versions installed, i could try removing the 32 bit? Maybe then a reinstall of the latest 64 to correct any possible DLL overwriting?

[edit: and that would also explain why rolling back to a previous driver would work.]

Paul.

aversis wrote on 1/26/2012, 10:21 AM

No it's not related to having them both installed.

In the end of my install tests, I only had the latest 32 bit version installed, and still had the exact same issue.

Then I deinstalled, and installed one version older. Same issue.

Deinstalled again, and installed vegaspro11.0.424_32bit, which solved it.

Before the last installs, I also deleted anything I could find in the registry and windows folders to make sure vegas was completely gone before installing again.

That will teach me for updating to the latest version if nothing is in fact wrong... For example I also use 3sd max, they also release new versions every year. I'm usually 2 years behind with their upgrades, which is the only way to make sure everything works as it should...

WillemT wrote on 1/26/2012, 10:29 AM

I have confirmed the problem, plus some other, in the other thread.

I only have the 64bit version installed. The last 32bit version I have installed is version 9. That at least eliminates the intallation of the 32 bit VP11 as a possible cause.

Willem.

paul_w wrote on 1/26/2012, 10:47 AM

thanks guys, going to try the build rollback when i get back to the computer. And will leave the 32bit version on the machine.

paul.

paul_w wrote on 1/26/2012, 12:07 PM

Okey... its also confirmed from me, build 425 works (64 and 32 bit)
then go to build 511 - failure, and build 521 also failure.

So in short, it got broke in build 511 and has remained broken in 521.

Im going to copy this both to my other thread and to SCS on my existing ticket.

Aversis, thanks for finding this, saved me the trouble!

Paul.