My System is Win XP Pro 32bit, my card has 640MB, board has 2GB, CPU is E6850 not overclocked or so. Also the graphics is still in default since I don't want to mess around with that.
I'm a little bit confused about the max RAM of XP but I think with 2GB and this card I'm still fine and can use every Bit of the RAM. The thing is, that I have even tried a way smaller 7200GS and the trouble is the same.
What kind of influence can I get from the page file? Is it good to have one on each hard drive or only on the system drive? All my clips and later the rendered video is on different drives.

Axel

I wonder if it has somthing to do with having a Quad core? I have one as well and it can not capture in 8a. I had to use 7e to capture. In addition Both 7e and 8a were crashing with HDV (24p shot with the A1 captured with the hv20). It seemed to work fine until I was about 70% done with the project I was working on then it would crash. I also think it has somthing to do with a file being corrupted( using dv tape instead of HDV), but it is real hard to pinpoint which one or ones is causing the crash. somtimes a certain file will cause it to crash and at other times it will not. I am going to try to see if i can repeat the problem with my laptop.If it is a corrupted file vegas needs to have a way to identify it at capture so I can recapture at the time and not waste days trying to figure it out. I was upset too - I almost lost one of my favorite clients. I did loose about a weeks worth of sleep working around the clock to get the job done. What finally worked was splitting the project into smaller veg files and rendering them out to a new file that I was able to stitch together in a new tiime line. I have a radeon X1650. Anyone know if this video card has caused any problems?

ReneH says (Since TeeJay never replied to any of the posts, I am assuming that he is a shill or a troll.)

ReneH, what is this, high school? I'm sorry that i have more important things to do other than sit on the computer to reply to the likes of your infantile comments!

As a matter of fact, i have supported Vegas for many years without any serious problems. My primary editing machine is not on the net and it is not overclocked. I work in Audio Visual, i am not just a hobbyist. The fact that this particular Exception Error happened whilst i was demoing the progress of the project to my Client was incredibly embarrassing!

These aren't big Stills. It is a simple 200 frame image sequence exported from P.I. at standard PAL 720x576. I have done this same process for years with previous versions of Vegas so for people to site "user error" here is simply absurd!

Teejay,

My sincerest apologies. Sometimes I get too defensive about all things Vegas.

Wow, I am finally seeing people that are having the same issuea as I am. Pastor Dave is fixing his crashing problems by sizing the veggies down then stitching the files together, just what I need to do to keep from crashing. I decided it is due to memory allocation/usage. Too much stuff in memory, and poof...
I have opened up a ticket many weeks ago with Sony, but they are unable to duplicate. Just to keep all the Vegas fanatics at a distance I am not even blaming VP8 completely for this problem, It may very well be the hardware we use Quad core 6600 top of the line graphics card 8800 GTX, Vista etc... but it seems this problem is affecting more people than just me, and I sure would love to find out who, what, why it is doing this.

Ted

How can identify a clip which has dropped frames? If I capture clips with HDVSplitt and have activated the "Stop at dropped frames", the software should stop the capturing of the tape?! It never stopped at all of my tapes coming from the HV10 and I'm not using extra HDV tapes because there are no HDV tapes out on the market if you take a look at the specs.
In Vegas I can see the frame counter which running up during preview and I think this frame counter is more toy rather than a real counter. because this counter counts continuesly up and sometimes jumps back to 0 on one and the same clips. So how can it be that one and the same clip has shows frame issues and sometime not?
Under properties in Vegas for clips I never found a dropped frame marker, it was everytime = 0

John Cline: You asked, "How could Sony Media screw this up?" Perhaps they didn't. Considering that thousands of people (including myself) are using Vegas Pro v8 with no problems whatsoever, I would suspect that it may have something to do with your machine and its configuration and not something inherently wrong with Vegas itself.

What sort of exception errors are you getting? Have you reported this to Sony using the "Support" option link above?

John
-------------------------------------------------------------------------------------------
So John, are you honestly telling me that EVERYTHING is functioning properly for you (as well as the other 1000s of users) in V8? 3D Track motion in 32bit mode? All good?

Click on a posters name to see a list of their past posts. TeeJay has been around for quite a while. Do your homework.

Teejay, could you point me to a good recipe to crash Vegas? I'm having a hard time doing it. The system I'm on is a:
--P4-HT, 2.? GHz
--2.5GB RAM
--ATI Radeon 9600
--WinXP sp2
--Vegas 8.0a
--16MB RAM Preview, 4 threads
--No external or secondary display
--NTSC SD project template.

Rob Mack

I can't answer for the thousands of others, but I can say EVERYTHING in V8 is functioning properly here, not a single glitch. I've done enough application writing in my life to know that NOBODY is going to get an app to work on every PC in the world, or even in the city, way too many variables in hardware/software. It's like trying to cook a dinner for just a hundred people, a dinner that everybody will like with no complaints.

"So John, are you honestly telling me that EVERYTHING is functioning properly for you (as well as the other 1000s of users) in V8?

I haven't used every possible option in Vegas Pro 8, but for those functions that I have used so far, I haven't had a single issue with 8.0a. 8.0 was a different story, although not surprising. The way Vegas has worked for the last four or five releases, there are some problems with the first version of a new X.0 release and they get resolved in the X.0a release which follows several weeks later. Vegas is still the most bug-free app that I use.

John

Rob, I guess there is no single thing that is causing it but it is definately happening with Image Sequences exported from Particle Illusion, to the point of the project not opening. I wound up having to import it as a nested project and then used it as a template to re-create the project from a previous restore. My gripe here is that it has never been a problem with V7. This problem i can work around. I'm more disappointed with 3D Track Motion not working in 32bit mode. Sure, i can just use 8bit mode but it's kinda like being given a sports car and not being able to use top gear............

Daryl: Well, it is encoraging to know that maybe there are Users not having issues. If this is the case, i am prepared to explore the possibilities that it is an anomaly with the Quad Core and/or the graphics card. I installed the latest drivers for the GPU with no improvement.

A little testing here on some NTSC SD footage with Vegas in 32-bit/2.222 mode.

I can put it into 3D Alpha mode and apply some 3D track motion to it but the result is totally unusable. But it doesn't crash.

Same with PNG image sequences. Unusable, but Vegas doesn't crash. Memory usage is a little high. with a 16 MB preview setting Vegas peaks at about 400MB in RAM, probably has the same amount in the page file.

If you were working in an HD format (are you?) I'd think it'd be more of a challenge.

But the main thing is that 3D track motion is unusable in 32-bit mode anyway. The image is fairly scrambled for me. I'm still considering 32-bit float to be a bit of a beta feature at this point.

Rob

I've actually had quite a few issues with Vegas8 - Most of the issues are consistently replicable on 2-3 of my machines.

Examples - I was doing a photo montage and it gave an exception error (had to redo it all...). I've seen Canon 24f footage lock up vegas multiple time. I can't capture 24f footage in v8 but can in 7. 32 Bit float is problematic. I've had numerous rendering lockups for what ever reason... even right now my bottom scroll bar has turned to solid black.

I really like vegas - but I now also own adobe and it seems to handle "problematic footage" just fine...

Those who have had no problems - count your blessings. But know that there are issues out there.


Notes -

All footage is captured and edited in HD as mpeg2 or m2t.

Primary machine:
Windows XP Pro
Q6600 Quad Core
Ram: 3 GB
OS Hard Drive: 300GB
Editing Drive: 300GB x 2 in raid0
BackUp Drives: Seagate External 750GB
Power Supply: 850watt
Video: EVGA 8600GTS

We have PPro at work and it's a scream fest, but that's probably because we also have Axio cards. PPro is a memory pig and Axio compounds it to the point where it just crashes a lot.

I've heard tech support responses of "Well, you've got a lot of PSD files and Premiere titles on the timeline, that's probably the problem, they use a lot of memory."

It seems like you're naming the two most common problems - V8a seems to hate Canon footage, and 32-bit is still a beta feature.

The photo montage...don't know what's going on with that. It used to be that anything handled by Quicktime (Tif files, mainly) would bring Vegas to its knees, and that's probably still true. I'm kind of suspecting that part of Teejay's problem is in the way that Particle Illusion is writing PNG files. Just a guess, though.

Rob

We have PPro at work and it's a scream fest,
In a good way (it's screaming fast) or in a bad way?

The photo montage problem sounds a lot like a memory problem to me. I've said it before and I'll say it again. There is some inherent problem with VP8 and memory handling.
It is very interesting to see the Q6600 Quad processor pop up yet again of people who are having problems.
Anybody out there running rock solid with a Q6600 ??

Ted

Hi Ted,

not only the Quads are affected, I have a Duo and I could figure out that even with 2GB as DualChannel and huge graphic card the memory handle is a farce. I figured out that a small project of 2minutes, 40 seconds HDV and SD mixed is filling the memory under Pro 8.0 up to 1.72GB PF Usage (according Task Manager) and everything stops and Vegas crashes.
Based on this I have tried to bring clips in the time line in HDV in Pro 8.0 and also the smaller brother Movie Studio Platinum 8.0. The same amount of clips fill the PF Usage way different. Pro seems to waste memory.
The point is, that I have tried the same project in Vegas Movie Studio 8.0 and it fills only 1.2 GB. I have used in both cases the same files.
The other thing is, that even with only 1.2 GB PF Usage in Pro8 I get a "Not enough Memory to render" message?! Can someone explain this?
The PF Usage of the system alone after reboot is 300MB, just as a side note. With Pro 8 it's 328MB.
It seems like (in my case) that 1.72GB of PF Usage is a magical number. Who can explain this? I'm realy frustated that I spend $300 for the upgrade from Movie Studie Platinum to Pro and can not use the software . Does someone sell still the old Vegas 7 Versions?

Axel

There's got to be something wierd going on here. Clearly some are having serious issues and others not. I've rendered out several hours of HDV from V8.0 in 32 bit to 16:9 SD on a Core Duo with 1GB of RAM without a glitch. It took DAYS, so long the estimated time to complete reset several times, the source and output were on a firewire drive. Pont though is dispite a clearlt under resourced system it kept slogging away and got there so whatever is wrong it's got to be somehow either hardware related or else related to software outside of Vegas.

I'd really urge everyone whose having these issues to start banging away at tech support, and make very certain they get the point that yours is not an isolated case. It's very easy given the way tech support is setup to miss picking up commonalities across various support calls.

Bob.

I have had the same issues as the other guys have. Crashing during opening projects, crashing on closing, crashing on rendering. Troubles with 32bit (the 3d motion track is completely different from 8bit V7 version, expecially if I open V7 projects).

8.0 version on my systems is REALLY unstable, maybe the most unstable I've ever seen. I must admit, I'm not used to see such an unstable version of Vegas, which historically was a rock-solid application, one of the most reliable on Windows platform.

8.0a is for sure much more better, more stable and in some cases faster than V7. But it still crashes in some circustances, expecially with 32bit projects...

I think the best thing to do is NOT to open older V7 projects with V8, but creating new ones from scratch. I'm still waiting a more stable version of V8. I still love it and consider it my primary editing application, either at home and at work, so, Sony, don't leave me disappointed !!!

Massimo.

Another weird thing that i just discovered. This happens for me regardless of whether in 8bit or 32bit mode.

Take a standard text event and apply a glow in Track Motion, and then add a keyframe to make the glow larger. The glow disintegrates!

Hmmn, anyone else get that?

Eh....stupid question. Where do you turn 32 bits on or off within Vegas? I checked the options but could not find such setting, only for building 8 bits peaks.

Go to file menu, open up properties.
JJK