I get the feeling that most Vegas Pro bugs crop up in the 64-bit version. My problems with the 32-bit version are next to nothing.

Lou

I have to say that I have had absolutely no problems with Vegas Pro 11 (64 bit). It was my first 64 bit program and I was a bit aprehensive, but no worries. And I do work it pretty hard (Indie level screenplays, mostly).

So, how do I do it? I have absolutely no idea! All I can say, is I have a moderately powerful computer with appropriate video cards which render fast and accurately.

I do use the computer exclusively for editing and I don't fiddle with Cineform or anything. I edit my AVCHD-PH files from a Panasonic AF-102 directly, but adding other files from different cameras makes no difference. I can only feel for those who, for some strange reason, struggle.

I wish I could say the same as you guys. Right now I am working with alot of green screen and since the vegas plug is not very good I use After Effects and this is where my problems occur.

AE will take just about anything you throw at it, but Vegas is being picky. MP4 import, crash, H.264, crash, the only thing that would work was a .mov H264 which is hellish slow to render out of AE.

Then I try and do some simple compositing in Sony. Problem is they are mixed frame rates. With GPU, on play and crash. Turn off GPU and it works but the quality has to run very low. Yeah I could do a work around and render individually to same rate, but there we go with another work around.

Also, just the basic performance issues. Have only one clip on the timeline, no problem, add sound performance hit, do an edit and things just get progressively worse. Touch the video slider and omg, tell mom we're going to be very late for dinner.

I use Avid's DNxHD codec to go between Vegas and AE without problems although that's only been between V9 and AE CS3 to date. H.264 is a pretty lossy codec that I would not use for such interchanges anyway.

Aggregating the aggrevation that V11 users are suffering there does seem to be a common set of issues e.g. adjust a slider and good night and goodbye. Other seem to have no issues at all.

I think it would be a worthwhile exercise for those who have issues to try running their projects on the system of those who don't have issues. Perhaps then we could narrow it done to either what is being done or what it is being done on. Given that Dropbox can handle 2GB of data this shouldn't be that hard to do.

Bob.

Tim, check out Edius 6.5. It doesnt even need a GPU and its as fast if not better than VP.

Well there's no telling when v12 will come or whether it will be any more stable than v11. Just have to see.

Paul.

Tim, check out Edius 6.5.
==================
That's what I have been pointing to as the core of the problem all along - GPU dependency.

I'll guarantee that Vegas 12 will be GPU dependent as well.

John

Farss I tried that codec. Exported out of Vegas fine, closed out Vegas restarted brought it back in and locked that puppy up inside of 10 seconds. Took same file and opened in AE no problems.

"That's what I have been pointing to as the core of the problem all along - GPU dependency.

After all these years of users screaming for GPU. Gimme my GPU! Everyone else uses the GPU, I want mine, etc.

I warned then, be careful what you ask for.

Back to my exile......

Oh, YES, Paul - Edius is incredibly efficient!

Grass Valley doesn't talk CUDA or OCL, and yet - at both playback and rendering - my GPU is actually working very hard... I wonder what it would be like if I had a more basic graphics card - would the CPU suffice for all this speed?!!

Piotr

Got a chance to run another test. Put sony on low quality settings 10 seconds and crash. Turned off GPU and it worked, however @ good auto I take a frame rate hit.

Tried in Premiere and it ran fine on high resolution @ full frame rate. btw I have GPU accl turned on there.

I'd recommend looking at this thread:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=822273&Replies=9

I was using the "compatibility" hack to get Vegas 11 stable but found that my WACOM tablet driver was actually the culprit. Once I uninstalled those drivers, I have had no crashes and no need to change the compatibility settings with Vegas 11 version 682/683.

Before you bail on it, it might be worth running through all of the possible issues cited in the thread.

Mike

I tried Premier and thought IT was junk.
On my particular system after trying a a bunch of different software for editing HD: adobe, corel, magix, sony, cyberlink, roxio, pinnacle and a few I'm forgetting, VEGAS 11 rocked my world and I haven't looked back. Never tried any previous versions of Vegas.
Not a fan of Final Cut either, but that is a story for another thread. ;)

so... yeah.... things just depend

All my drivers are current. All my software is current. I have tried doing a fresh Vegas install. Tried compatiblity mode. Tried going back to 8 bit video (only improves performance) Turning off the GPU provides the best results, meaning fewer crashes. Don't use a wacom, but use a Tascam interface controller and have tried turning it off. Nothing matters. Crashes happen all the time.

I just took a wmv and went to compress it down to a smaller wmv. Two seconds into render CRASH. I mean whats the sense in using Vegas if you have to disable what they claim are the best features.

Plus my gut tells me something is amiss at Sony software. No fixes for 3 months now just a message that says try this, blah blah blah see ya. A good company would say we know the problems, we have catalogued the top offenders and will have a patch in the coming weeks. Most likely the attempt to write a 32/64 bit package has failed and so their strategy to go to 64 bit only.

What a company doesnt say is just as much an indicator as what they do say.

Problem would seem to be that GPU accel is such a fragmented and moving target. May or may not be at the core of the fundamental problems.

geoff

"Problem would seem to be that GPU accel is such a fragmented and moving target"

I suspect the problem is that SCS have tried to be too egalitarian. Other vendors don't seem to have the same issues and seem to wrangle more performance boost from the use of the GPU as well. They oftenly also limit the range of supported GPUs and cards.

Bob.

I am absolutely not a pro with video software at all, but rereading your specific issue descriptions, sounds like it could all be "Codec" based?
Try a new, clean install of Windows and vegas without installing ANY other video systems like quicktime, vlc, media player classic, real, veoh, winamp, codec packs, etc and see if it is more stable.

I can admit when I first got it, there were certain formats I would try to render that crashed, but I just thought I was doing something wrong. Then found out, it crashed for many and they fixed it. Meanwhile, I just used a different format to render to.
Still, I tend to install lots of other players with codecs that infect Windows and cause issues.
Maybe that is happening to you also?

I would have to disagree that it is codec based. Premiere and After Effects are rendering just fine. Doing a fresh install of Windows is not an option considering the amount of work I have to do and that I can work in Adobe just fine. Plus I have many failures that are not specific to rendering.

These issues with Vegas have been going on since last yr when I bought the program and at that time my Windows 7 64 was a fresh install. They only propagated when I went to an Nvidia based card to take advantage of CUDA in my other programs.

BTW I just ran the Microsoft Codec checker and repair tool and it said all is good.

I just bought a brand new Nvidia card, 680, I think, and it seems fine. You could try to do some clean up with revo uninstaller, ccleaner, advanced system care freeware...
granted I have not done much big rendering with it yet, and I know Vegas can hiccup, but I have not had all the issues you are having. Might jsut be awkward concoction of components in your specific system working against vegas.

I have been able to get better performance out of Vegas by going into my bios and manually setting the FSB and DRAM timings. They were set to auto. Now able to run Vegas on Best Full resolution.

No idea yet if this will help random crashes.

Tim,

Can you explain what the FSB and DRAM settings should be manually set to?

Thanks, Marc

To do that you have to know your processors front side bus speed and and your ram speed and CAS timings.

Ram should be easy to find out but you have to open up your computer and pull out a stick and check the label which would read something like SDRAM 1600 8-8-8-21. So you would set the DRAM in bios to a speed of 1600 and CAS timings to 8-8-8-21

For FSB check your system info and get the model # and check with Intel/AMD to see what the FSB speed is. In my bios when I pulled it out of "auto" it defaulted to the CPU's FSB speed


Hope that makes sense. Easier for me to do than explain :)

<<I have been able to get better performance out of Vegas by going into my bios and manually setting the FSB and DRAM timings.>>

I appreciate your explanation of how to do this, very clear and well written. Thanks!

Has the crash situation improved for you since making the changes? Vegas 11 is definitely a mixed bag, but for me it's been mostly OK and overall I much prefer it to VP10 which was darn stable. Yeah it crashes and has other ROW (random occasional weirdness) behaviors, but after editing with Premiere for years Ctrl+S-ing became a nervous tick, I think I may even do it in my sleep...

Bottom line, losing 20 sec to an occasional crash doesn't even register as annoyance. Well, mostly...

Yesterday it was freaking out again over seemingly nothing. I just wanted to do a p-i-p on top of a Photoshop title background. But Nooooo. Vegas thought it would be better to apply a quasi-random psychedelic green/static lines/black flashing effect to the video.

I have six other clips with this effect (and they have a mask overlaid to boot) with no ill effects. So maybe because it's because the problem clips were copied/pasted from an earlier project done in Vegas 10? Or maybe it was the clips themselves? Sometimes VP11 is like that; I'll change the edit ever so slightly and poof, problem gone. Other times I'll need to open the occasional problem clip(s) (AVCHD 720p, GH2) in VP10 and render them to .mxf (that ALWAYS solves the problem). In this case I turned GPU acceleration off and that was enough.

I can handle the inevitable bugs and workarounds that any program will have, but I say a nightly prayer that the management weenies at Sony will get their act together and properly support the product so that folks will stop jumping ship. I've even resorted to animal sacrifice (chill PETA, it was a stuffed animal).