sony vegas 8 not responding

bkilburn wrote on 2/27/2008, 5:50 PM
Just built a great computer- 4GB MEM - 3.2DUEL CORE AMD PROCESSOR-750GB HARD DRIVE, 2 DVD BURNERS, VISTA 64BIT OS. GeForce 8400 video card. Everythings works wonderful but Sony Vegas Pro 8 trial. I am trying to find a new program to invest for my videos- switching from Mac FCP3. I thought that I would download the trial to see if I liked it before I bought it. I love it when it works but it will shut down "unexpected quit" or go to "not responding" about every 20 min. I don't know if it is a "trial" problem, 64bit Vista problem, or if Sony Vegas 8 will never function properly with Vista. Any suggestion would be greatly appreciate. Also, getting ready to build another and would like any recommendations for specs for video only system.

Comments

blink3times wrote on 2/27/2008, 6:13 PM
Well, I can tell you it's not Vista 64.

I've run Vegas on vista 64 on a quad core since version 7d and it works well. I have noticed however that Vegas has become increasing unstable since 7d.

Vegas is a great program and I love it to death but I do believe that it's undergoing some growing pains. There have been some fairly large under-the-hood changes in vegas since 7d in an attempt to stay on par with the ever changing video editing world (ie: smart render, bd burning, avchd editing, new titler...etc) and I don't think they have QUITE got all the bugs out of those changes. Although the crashes can be quite irritating (and you learn to save A LOT as a result), I am confident that they will get things running smoothly once again. In the mean time I find myself dividing the work up between 7d and 8b, taking notes on the crashes and creating work-around's for them.
bkilburn wrote on 2/27/2008, 6:34 PM
Which version is the most stable? I need it for teenagers with nooooooo patience.
blink3times wrote on 2/27/2008, 6:51 PM
I find versions 7b to 7d to be the most stable. Granted the new titler isn't there, nor is the smart render for HDV editing, but it works.
Laurence wrote on 2/27/2008, 8:00 PM
I can tell you exactly how to fix this:

Do a search for and delete any instance of "AJACaptureFilter.ax".

Yeah I know I mentioned it in several other threads, but not everyone reads all the threads. I am really confident that this will probably fix your problem.

Vegas 8 is every bit as stable as 7, but only after you get rid of this file.

The only reason you should keep this file is if you have the AJA capture hardware. If not it will crash your system big time!
blink3times wrote on 2/27/2008, 8:22 PM
That's the first time I've heard that Laurence... I'll give it a try... thanks

EDIT: Sorry Laurence... I searched my entire drive and the registry for "AJACaptureFilter.ax" and came up with nothing. :(
Laurence wrote on 2/27/2008, 9:34 PM
Blink:

Do you have Cineform Neo installed? Maybe the AJACaptureFilter.ax file is only with the paid version of Neo.

Also, in another thread Nick pointed out that the mpeg2 codec reader changed between 8a and 8b. Maybe going back to 8a would help you.
Darren Powell wrote on 2/27/2008, 9:40 PM
Laurence,

The 'AJA' file delete is not the 'quick fix' you think it is ... I don't have that file either, I completely stripped NEO HDV off my machine after ongoing problems last year ...

Vegas Pro 8b on Windows XP has major major problems which seem to be machine dependent at times, memory related at other times etc...

If the trial works on Vista64 without errors ... I'll jump off Trollveggen with a BASE chute strapped to my back ...

Darren Powell
Sydney Australia
Laurence wrote on 2/27/2008, 9:49 PM
...and I was so sure too. Darn! Have you tried going back to 8a?
Darren Powell wrote on 2/27/2008, 9:51 PM
Nope, it was just as bad first time round ... I'm back to 7 - it's going great ... and I'm not touching a thing for a long time ...
blink3times wrote on 2/28/2008, 4:10 AM
...and I was so sure too. Darn! Have you tried going back to 8a?

IMO Laurence....

This has more to do with the various avchd modules and subroutines that were added. Vegas was rock solid for me and crashes were almost unheard of right up until 7e, and that's when the unexplained and random crashing started. If you remember, 7e is where avchd edit was added. They were overdue with that too... an indication to me anyway that they were having problems making it work.
Darren Powell wrote on 2/28/2008, 4:40 AM
Interestingly blink3times, it's 7e is also where they packaged the MainConcept codec, mcplug.dll in a .cab instead of just in a directory ... could be something in that ... perhaps?

I don't know ... just noticed that when I finally got a render of my project out of 7d ...

Darren Powell
Sydney Australia
JJKizak wrote on 2/28/2008, 5:31 AM
With Vista 64 you have to go into "DEP" and select Vegas.exe as an exception.
JJK
Kennymusicman wrote on 2/28/2008, 6:50 AM
"With Vista 64 you have to go into "DEP" and select Vegas.exe as an exception"

No you don't. It works for some, sure. BUt it's not mandatory
kkolbo wrote on 2/28/2008, 12:24 PM
I did a straight basic install of Vegas Pro 8 (the most current version a) on a Vista 64 machine with a dual core AMD and it is as stable as always and works just fine. My machine arrived configured for Vista 64 with all the proper drivers and hardware. I have no complaints.
mobass1 wrote on 2/29/2008, 12:34 PM
I agree with kkolbo. I built the same basic machine and found that V8pro worked fine all the time. However, that being said; I mistakenly took advantage of the "free' upgrade to V8proB and discovered that I could no longer capture DV. I tried everthing imaginable, but came to the contusion that V8b sucked on my platform. Went back to V8a and everthing is happy once again.

I was informed by Sony tech support that a 64 bit interface would be out this year, but so far no such announcement ( or have I missed the boat somehow ). Moral of the story: "Just because its free, doesnt mean you should upgrade."

"Party on"
Steveo