Comments

jetdv wrote on 11/26/2003, 1:14 PM
Actually, only THREE of the functions were broken in 4.0e:

Video Wall
Rotating Pic
PIP

And THESE are only broken if you use the border or effects options.

I have updated the program and offered it to a couple of people for testing. The test results have not yet been given to me in one instance and were positive in another. So, at this point I "think" I have an updated version. I'd be willing to take on a couple more testers before getting the final fix posted.

Plus, technically I'm on "vacation" this week!

Edward
cyanide149 wrote on 11/27/2003, 4:30 AM
Thanks Ed...
jetdv wrote on 11/27/2003, 5:06 AM
cyanide, If you'd like to test the fix, send me a private e-mail.
donp wrote on 11/27/2003, 7:07 AM
I have the current version of Tsunami. I did not upgrade to 4.0e of Vegas, decided to wait for 5.0 whenever that will be. I will assume that whatever caused Tsunami to break in 4.0e will extend itself into the future releases from Sony-Vegas. So woud it be prudent for me to download and install the revised version of Tsunami when it gets done and will it be backcompatable with 4.0d. Forget that I just remembered the "Don't fix it until it's broke" thing.

I will be with 4d until 5 comes out or a ground breaking 4f or somthing like that.
jetdv wrote on 11/27/2003, 8:26 AM
If you are using 4.0d, there will be NO need to update Tsunami.

Once testing is completed, THIS update will work for 4.0d OR 4.0e.

A NEW version will be required for 5.0 anyway so don't worry about this update unless you are switching to 4.0e.
Nat wrote on 11/27/2003, 8:49 AM
Why is a new version needed for 5, are they changing that much things ? :)
jetdv wrote on 11/27/2003, 10:59 AM
According to the script posted by SonyPJM in the scripting forum, it appears that the "imports" statement and any direct references to "Sonic Foundry" will need to be changed.
johnmeyer wrote on 11/28/2003, 7:02 PM
According to the script posted by SonyPJM in the scripting forum, it appears that the "imports" statement and any direct references to "Sonic Foundry" will need to be changed.

Ed,

Are you saying that I have to change every instance of:

import SonicFoundry.Vegas;

in every script? I've already said my piece about what I thought of Sony wasting time with name changes, but to force this upon the very people trying to write plugins, add-ons, and scripts would be insane. The old call could still have been included, you know. This isn't the end of the earth, but I really wasn't looking for make-work to fill my hours.

Please say it ain't so.