Dual Athlon 1900+MP, Tyan S2460 MB, 512 DDR Ram, 2 120GB 7200 HD, Win XP SP1, DX 9, ATI All In Wonder Radeon video card. Will not capture from video card, but that's not much of an issue for me. Pyro Firewire capture card works fine. Camera not an issue, capture OK.

System crashes whenever I begin to add effects or tansitions, audio or video. Anything other than plain vanilla playback/render causes it to stop responding. Playback with crossfades is OK. Trying to load .veg files saved in causes V4 to stop responding. All is well in VV3, SF6, Acid Pro 4, CD Architect 5.

Thanks

Thanks for the quick reply...

First I'd check the radeon drivers, they had to be fixed up, esp. 2.2?

Then I'd check the display settings and turn off HW accelleration.

Then I'd check for VIA chipset on the mobo and update to 4-in-1 drivers if needed.


Then I'd come back and ask for better ideas (unless they worked).


HTH, MPH

You can't load V4 veg files in V3 -- that was made clear at the time the public Beta was releaseds.

I'm a beginner, so take my advice with a grain of salt, but I've been reading about a lot of people having problems with XP's SP1... (not with vegas in particular, but with a few other programs)... they removed sp1 and started working againg.

-Josh

I'm using Win XP Pro with SP1, V4, transitions, effects, and even running 4 occurences of V4 on my computer to render sections all night. Using a Dell Dimension 4300, 1.6Ghz P4, 512MB SDRAM, Nvidia video card.

I've added the new Windows Media 9 Player and Encoder. I haven't upgraded to DirectX9, so I'm still on 8.1.

No problems here.

Crashing with Vegas 4 is MOST unusual. Probably another problem rather than Vegas. Keep trying.

Suggest you UNINSTALL Vegas, reboot, Defragment your disks, reboot, and then REInstall Vegas.

Then, defrag before and after each capture. That tends to level out any quirks in a system when there is nothing ELSE wrong.

Those problems are NOT actual Vegas problems, per se. It is just that NLE programs, including Vegas, notice problems more than some less demanding programs.

IMO sounds like a DX problem as that's what's involved with the filters. Removing and reinstalling VV4 should hopefully do it. Might want to reinstall DX9 whilest you're at it.

Otherwise:
A lot of video & audio related apps use files from the same source (ligos and mainconcept are two common ones that come to mind) and windows could be using one version whilst VV4 requires another. If the reinstall didn't set things right, could be an active x control in the system 32 folder (or another within the XP folder) with the same name as one in the VV4 folder. Had this happen once where even though winxp knew it should use the VV4 version, the presense of the file in the winxp folder over-rode it - had to remove the file itself from *all* locations in the winxp folder.

Have also seen a lot of complaints of misbehaving active x controls/files regarding winxp's moviemaker 2. I know you're not referring to problems there, but the underlying video code is still present in a winxp install with all the latest updates. Check out the forum or newgroup online at the MS site under moviemaker or winmedia and there's one fellow who keeps posting a running tab of known prob. files.

To follow through this route of diagnosis, you'ld use DXMAN to see what's installed where, removing a file from the winxp registry. If that didn't help, use REGDROP to re-register that file and proceed to the next [you need to be able to find the file to re-register it, hence why the added step of recording where the file exists in DXMAN]

mike

I'm not trying to open V4 veg files in VV3. I'm trying to open them in V4.
Lot's of help here. I'm working on it. Will keep you updated.

Thanks,

Bob