Abandoning Build 511

warriorking wrote on 12/27/2011, 2:51 PM

Bulding and rendering the multicam project work great, no issues whatsoever, I just rendered a 1 Hour 40 Minute project without a single problem, its just when I choose FX corrections that vegas wants to lockup, or crash......mostly the crashes will occure after several FX corrections have been made in the timeline, so I always hit the save option with each correction just to be safe....other than that everything else in Vegas works great....

Arthur.S wrote on 12/28/2011, 11:33 AM

Giving V11 another chance with 511, I've found yet another bug. Whenever I open a saved project, ALL of my keyframes on a Gaussian blur change. This is on all of my text throughout, so it's a major PITA. Add to that, V9 is definitely not as stable as it was before 11 was installed. After this project is finished, I'm going to have to do a complete un-install then clean install of 9 to get things back. That means all of my plug-ins etc being uninstalled/reinstalled too. MAJOR waste of time, not to mention money. The cost of the V11 software plus a new graphics card to - LOL - get the best out of it. This is poor poor poor Sony. Why are so many things broke that worked fine in earlier versions??? Can I get a refund I wonder?

WillemT wrote on 12/28/2011, 12:58 PM

I can confirm the keyframe issue.

Add a Gaussian blur to a simple text event. Set keyframes along the event. Save, close down Vegas and then reopen. The keyframes are now at about halve the spacings where they were. Click save and close and reopen Vegas and they are at halve of the previous.

This is similar to the keyframe problems Rosebud, Gilles, found in a nother thread. I think we have a very serious problem with keyframes in VP11-511.

Edit: I just tried with a Levels on a secong Text event and then again with a Color Curves using a video clip in an event. All exhibit the same keyframe problem. The only position a keyframe stays in place is at the start - meaning events (I have not tried the other) cannot be keyframed.

I next turned GPU off and repeated the above - adding a Cooky Cutter FX to the video event. Same problem - all keyframes are repositioned. Adding a mask, and keyframing that, does not seem to have its keyframes moved.

This makes 511, for me at least, completely unusable - even though I do not see most of the crash problems.

Willem.

Paul Fierlinger wrote on 12/28/2011, 4:51 PM

Same here. Updated driver. T he result is unbelievable! Thanks to all for this thread; I was getting a bit desperate..

gripp wrote on 12/28/2011, 6:12 PM

Nvidia 290.53 has so far cured all my problems with build 511.

BUT, I found that the FM Baumann plug-ins were still causing green/blue flashings whilst rendering, so I have reluctantly abandoned them.

Made a simple 5 min vid today, with just a bit of Sony FX applied, and it was as stable VP10e

daryl wrote on 12/28/2011, 8:22 PM

Just got back from a trip. With all I've been reading about the latest updates, I'm surprised that theyhavn't been pulled. I'll wait for the next version, the current one has been working GREAT since installation.

Arthur.S wrote on 12/29/2011, 2:09 AM

Willem, do you also get this: Add a keyframe at say zero (could be any value). Add another with a different value. The first one changes to the same value as the second.

WillemT wrote on 12/29/2011, 3:28 AM

Arthur, do you mean add a keyframe at zero with Hold, then further down the timeline, one with Smooth Fade? If so, no, I do not see the first change, it remains Hold. Even after a save - which squishes them closer together, they retain their initial settings. Additional ones further down the line also all retain their settings.

Willem.

Erni wrote on 12/29/2011, 8:23 AM

Same problem with keyframes here.

Erni

Westside Steve wrote on 12/29/2011, 11:15 AM

Well, I never had version 10. I've just upgraded to pro from studio. I do not have the update 511 installed even though I see it exists. So far everything seems to be working fine so maybe I will let sleeping dogs lie and install the update when it gets perfected.
WSS

zmobile wrote on 12/29/2011, 11:27 AM

UPDATE to previous post....

I have a new Radeon ATI HD 6850 1 GB board with the latest drivers directly from ATI. Tried 511 and the video preview playback was very choppy. Rendering was extremely long. Checked all the settings. Didn't help. Reverted back to 425 and will wait until I see better posts about 511 or better. I did send in a trouble report. They seem to think that I should uninstall Pro 11 in my normal admin account and re-install 511 in a new admin account to establish a clean registry and see if that helps. I've reconfigured my computer with a set of extensive mirror drives and file server system to preserve the working environment. So, perhaps I'm ready to test 511 and be able to revert to 425. I cringe at the thought of actually doing this. More coffee. I did see a post in another thread (#88) about slow rendering being solved by using the 32 bit 510 build instead of the 511, 64 bit version. Might try that too. More coffee.

zman

Arthur.S wrote on 12/29/2011, 11:51 AM

No, not at hold Willem, I want the effect to change gradually from zero to whatever value I set. So say a Gaussian blur going from 'reset to none' to extreme blur (or visa versa).

Age of Reason wrote on 12/29/2011, 12:14 PM

And now you know why all software companies want cloud computing. Everyone will be upgraded and no one will be going back versions. They will have you trapped like a rat and they will never have to badger you into upgrading. This my friend along with hacking from overseas will kill technology over the next 10 years. Stuck with new and not improved software with horrible security and downtimes that dwarf the dialup days. Cloud computing is the answer! Sounds like all in one copiers, fax machines and printers. Oh wait Sony has never been hacked. I'm still on Version 7 and it works flawlessly and if I need something different then I use other software that also works flawlessly. Not one wasted penny on my part.

WillemT wrote on 12/29/2011, 1:05 PM

Arthur, the reason I thought you may mean the interpolation between keyframes is that I was already changing from, say non to blurred (and back), with the Gaussian Blur FX when testing the moving of keyframe positions. So, no, I do not get that problem - or at least I did not see it happen yet.

Willem.

Arthur.S wrote on 12/29/2011, 6:52 PM

Ten to one in the A.M. here. Just finished juggling/wrestling with 511 to get the job done. Tomorrow - or rather later today - V11 comes off my PC...and it aint going back!!! It's been the worst NLE experience I've had bar none! :-(

Frederic Baumann wrote on 12/30/2011, 8:24 AM

Hi,

@gripp:

I am replicating on this thread the answer I have just written on another thread (http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=793301&Replies=5), to help me fixing a bug, should this problem actually come from the FBmn Software plug-ins:

I am sorry to read your comment. I've never got such feedback reporting this kind of problem so far, so I would be pleased to reproduce this phenomenon and investigate.

Should it be a bug from the plug-ins, I would be happy to fix it and provide a patch for it. Please give me any detail that will help me reproduce the problem - ideally a whole Vegas project with minimum footage. I suggest that you contact me via the email contact details on my web site, rather than on this forum.

OFX integration has been subject to many changes in Vegas across 10a/b/c/d/e/11, especially keyframing. So if you have seen changes in the behaviour of the plug-ins between these releases, I am afraid the problem comes from Vegas and not the plug-in. However I will be pleased to investigate: I could still, possibly, find a workaround and implement it in the plug-in.

Best regards, and thanks in advance for helping me improving the plug-ins quality if appropriate,
Frederic - FBmn Software

dxdy wrote on 12/30/2011, 10:36 AM

I have been using the Bauman FX accelerated plug ins in build 511 without any green or otherwise damaged frames.

Win 7 x64, GTX 560ti with 1GB DDR5

Fred

ritsmer wrote on 12/30/2011, 3:33 PM

Quite interesting how several returning "names" here are "very unhappy" with Vegas 11 - venting loudly their unhappyness...

They are, however, hardly really interested in making Vegas better...:
I have made a couple of threads here with a plea for testing of what I thought might be an issue - but mostly these pleas remain totally unanswered...

I do recon, of course, that we paying users are not at all Beta-testers - and that the last released versions are certainly not 100% - but anyone having a serious interest in Vegas would have tried to test such defined issues and so have helped to find out if such issues were related to a single users set-up/ hardware or if they were real issues to be improved by SCS - and what I do believe that SCS will ASAP do if more users find the same problem - like also I participated in confirming the recent moving-key-frame-issue and others.

Against the meaning of several it is actually also quite Ok to answer: "I have tried to recreate the problem - but it does work OK on my machine"

What I mean is: why not get together and help each other to define and possibly confirm issues in Vegas in an orderly manner - This might result in a Vegas 11.0c/d or e as stable and reliable as good old 8.0c and for me, at least, the 10.0e.

When each and every issue is corrected in Vegas 11.0 xx - then we can only hope that SCS will maintain a steady and safe evoloution instead of trying further revoloutions with NEW!! 3D Badoom and NEW!! GPU assist Badoom...

If Vegas 12 comes with NEW!! 8K Badoom-Zap or whatever I will stick my -then-good-old Vegas 11.0f... :- )

Happy editing in 2012
ritsmer

PS: It would work wonders as to user satisfaction if "Forum Admin" would come forward at these occasions and say: "Thank you, guys, and yes: we can confirm the keyframe issue - or xxx issue - and we will improve them ASAP" or "Sorry, but, that issue is a tough one - could other users please test that also?" - instead of the famous chilly silence - which has made at least me refrain from from asking about an issue or two...

Hulk wrote on 12/30/2011, 3:54 PM

ritsmer brings up a good point. If there are no big changes with 12 perhaps there is a chance there will be time to just refine 11.

What BIG changes are left to make with Vegas 12?

I'm just looking for AVCHD smartrender.

- Mark

SamAt wrote on 1/1/2012, 5:38 PM

I agree with ritsmer's sentiments; reporting bugs is good, and having others report no-repro is also good; the contention I see appears to be the result of reactions to comments that might appear to be blaming the victim e.g. insinuating that someone their fine admin skills are responsible for them not experiencing reported issues. If we stay away from that nonsense we're good.

But also, people will have to learn to create meaningful Subject lines, the way a dev/test team would. i.e. The subject line should make it obvious what the issue is at a glance, but that's not a habit most end-users would have. What should be happening is that people in the product teams should be opening bugs, with titles and bug numbers, and referencing those back in these threads.

Meanwhile, I'm happy to report that I'm productive again back on the 425 build with Crash reporting disabled.

zmobile wrote on 1/28/2012, 9:28 PM

I had done a major upgrade from XP Pro 32bit to Win 7 64bit. Everything seemed stable, so I went ahead and upgraded from Pro 8 to 11. And that's when the random crashes started all the way to BSOD. I thought build 525 would fix it, nope, made it worse. Went back to 411 and got by for a while.

Then I read a thread about not only replacing memory, but testing it first. Ah, I have been there before!

So, I got memtest86 from the web (Google it), tested modules individually and in combinations to extend the range of the address bus on the mother board; found a bad 1 GB module in 20 minutes and replaced it. This also verified it was not a mother board problem. In fact, I replaced them all so, from 3 GB to 8 GB.

Another point to make, is that I went from XP Pro in 32bit mode to Win 7 in 64bit mode. The same with Vegas, 8 in 32bit to 11 in 64bit. Folks, sometimes this is NOT plug and play. You may have to set your BIOS to extend the memory addressing to use that 64bit OS. You have to look carefully at your System in the Control Panel to see that it not only sees you full memory install, but actually has it in service! You don't want to see, x number of GB reserved for any other purpose. See your Resource Monitor that will show you how your memory is being used.

So far, the machine is stable and appears to be a little faster, but too soon to tell and too late in the day to take measurements. I still have to test 411 more, finish the current project, then try the new just released build.

In the old days, the "new" programs were the best memory and CPU testers. They "found" all the weak silicon, so to speak. I guess this law is still true.

So for those that have upgraded in a big jump especially, and you are scratching your collective heads... make sure your hardware really is passing all the tests and replace all the bits that are not. I never thought that would happen to me.

Sometimes, although rare (but this has happened to me once), the mother board may have an issue trying to address or read and write to memory. Just putting in new memory does nothing in this situation, the problem may actually be on the mother board.

Total cost to fix my machine crashing $130 USD, but could have done it for $39.

chuck z
zman Productions