plug-ins causing Vegas 10 to crash

crocdoc wrote on 7/26/2011, 9:07 PM

Vegas has been crashing for me when I try to add a filter or plug in to an event. At first I thought it was just the trial version of Neat Video, which seemed to be sorted out once I made some adjustments to the settings on my anti-virus program. Now I've come to realise it's happening with any of a number of plug-ins, both within Vegas and third party. It doesn't happen every time, even if I perform the same steps, nor with the same frequency for each plug in, but the end result is the same - while trying to either install or remove a plug-in, Vegas will hang and I'll get an error message saying "Vegas has stopped working", at which point I do a force quit and start again.

It's happening with an alarming frequency, to the point that I have to save after every step/edit/keyboard stroke if I want to get anything done at all.

Has anyone experienced anything remotely similar to this and, if so, any idea what the problem might be?

Comments

Grazie wrote on 7/26/2011, 11:37 PM

Crocie, you still on your 1.87gHz laptop? - I'm starting to appreciate the value of faster RAM and clock. Maybe there is a pachyderm in the chamber? Maybe VP10 >> is just too intense on lowlier clock-speeds? But that's just this poor grunt's opinion. There is something choking Vegas, I agree. You/me/others would like to place at the feet of SCS - and why not.

However, IMHO it maybe that we've seen the last of anything under 2gHz being feasible?

Can o' Worms well and truly prized open. [Elephants, worms? starting to sound like a Zoo!)

Grazie

farss wrote on 7/27/2011, 12:35 AM

"However, IMHO it maybe that we've seen the last of anything under 2gHz being feasible?"

Low clock speeds shouldn't cause a crash. Running out of RAM, for sure.
I suspect the confusing thing here is that users running more than 4GB of RAM are also running fast CPUs.
One thing that might help Crocdoc is to reduce the amount of Preview RAM.

Bob.

Kimberly wrote on 7/27/2011, 2:51 AM

What version of Pro 10?

I had a lot of lock-ups in 10b. It occurred mainly when I was previewing and the timeline played past the end of the last event on the timeline. If I clicked back to the timeline or clicked "Save" or anything, the Vegas locked up.

If I waited, say, 20 seconds, Vegas would return to the last cursor position. I could tell when Vegas was ready because the cursor would flash. My problem was that I was always impatient or distracted and clicked on something right away, hence many lock-ups.

I have 10d now and have not seen that problem. I've always had plug-ins from NewBlu, VASST Mayhem, and VASST Ultimate S Pro.

crocdoc wrote on 7/27/2011, 5:34 AM

Thanks, Bob, I will certainly give that a try. I had it set on 1000mb and have halved that. It probably doesn't help that I usually have a few programs open at once.

Grazie, I'm planning to get a new desktop machine at some stage in the near future and have bookmarked your thread on building your monster to read through the replies for ideas on hardware and specs. I've always been a desktop person but picked up the laptop last year for a number of reasons and have come to rely on it, knowing that eventually I'll probably go back to doing most of my work on a much gruntier desktop.

Kimberly, I've been using 10e since it was released. The odd thing is that this problem has only started occurring in the past week and I'm pretty sure I've tasked this machine much more in the past, running multiple RAM-hungry programs at once while editing. I've always found Vegas to be very stable, but somethings going on with my machine at the moment.

When I have a quiet few days in August I think I'm overdue for a hard drive format and starting afresh with a clean install of operating system and all software.

gwailo wrote on 7/27/2011, 6:29 AM

since upgrading to 10e - i've had plugins cause problems as well, but my problems are from audio plugins.

I copied and pasted (paste even attributes) to copy an effect on events between 2 different projects. It basically caused an error on loading the project, the next time the file was opened. To clear the error I had to erase all the effects, save the project and add them in again... this time without copying.

I'm also getting another freaky error. Sometimes my soundcard gets picky and doesn't play any events with plugins, or events with vegas pitch or time shifting.

Other events play fine. Changing preferences in the audio device section back to windows default, then close, then open, then setting back to my ASIO drivers worked to get rid of that bug.

I submitted a ticket over a week ago...

no response