7.4 and Vista x32 problems

[Felix Aux]

I'm starting to think that eighter I just blew a lot of money right down the drain, or my configurations is way of.

I have used Windows XP on a P4 1GB ram SATA disk for several years now. Updated my protools to 7.1 about 1 year ago. I like Windows, and have been waiting for 7.4 for a long time so I could use Vista.

All the time I've been troubled by buffer underruns and had understood that this was the result of running Windows, PT LE an 1GB ram.

So when I upgraded my computer now, I went all the way.

Vista Ultimate 32-bits
MSI P35 NEI-FI Mainboard with Intel P35 Express / Intel ICH9 Chipset
Intel C2Quad Q6600 @2.40GHz
4GB DDR2 memory (Dualchannel)
Gainward 8600GT
Two ViewSonic 19" screens
ProTools 7.4
Command 8
Digi002 Rack (firewire)
NEC based firewirecard (PCI)

And what do you know. After installing Protools 7.4 and Command8, I've never had so much buffer underruns, even with settings on 1024. My system even crashed when running PT.

I have to say I use my system disk for recording and playback. But this was with two mono tracks.

What have I done?
Is it the CPU with 4 cores?
Is i Vista?
Is it the FW-card?

There should be quite enough power in this machine.

[toun]

I have the same issues but i discover that the problem is my uad1 card . Try to disable your pci firewire card.

[sunburst79]

Its probably not your Q6600, At least they are fine under XP. I can't tell you about Vista-It shouldn't be the problem.

The most likely culprit would be the FW card. I would replace it with A SIIG card from the Approved Fire Wire cards list. Are you getting a specific Error code? Knowing what it was would help. Lastly are you using Hitachi or Samsung HDD with a Gigabyte P35 board? There is a know issue there.

[SeedGuy]

I've been using XP with a Core 2 Duo, 3GB DDR2, Asus P5W Deluxe for almost a year, runs perfect, can have the full 48 tracks, plus up to 20 Virtual Instruments, the moment I upgrade to vista I can't even run 2 stereo audio tracks while moving a parameter on a comp without a buffer error. I quickly reformatted and went back to XP, and yes, it works perfect, just as before.

I have Mbox 1, no firewire, no network cards, no UAD cards, and yet vista still moaned at me for no reason.

[sunburst79]

I've been using XP with a Core 2 Duo, 3GB DDR2, Asus P5W Deluxe for almost a year, runs perfect, can have the full 48 tracks, plus up to 20 Virtual Instruments, the moment I upgrade to vista I can't even run 2 stereo audio tracks while moving a parameter on a comp without a buffer error. I quickly reformatted and went back to XP, and yes, it works perfect, just as before.

I have Mbox 1, no firewire, no network cards, no UAD cards, and yet vista still moaned at me for no reason.

This is why I recommend that people dual or triple boot... PT on VISTA is well, New... and there will be "Interesting" things becuase of that. Lots of interesting things

[Felix Aux]

I have a Samsung SATA SP2504C disk.

I'll try with a new fw card. I see that the SIIG use TI chipset. Have another fw-card with TI chipset.
Next up, will be the HD.

PS: I'll note the error code when I see it, and post it here.

Thanks.

[Felix Aux]

New development.
Inserted the TI based FW card. At first it looked like everything was okay. But

Got an buffer underflowed error.

"The audio device buffer underflowed. If this occurs frequently, try decreasing the "H/W Byffer Size" in the Playback Engine panel or remove other devices from the audio firewire bus. (-6085)."

When I changed the setting to 64, it almost instantly at start of playback got the error. But this time with the message to increase the H/W buffer.

For the record, i have no other devices attached to the firewire card.

(Also tried at 256 and 512)

[sunburst79]

Felix there was a problem with Gigabyte boards and Samsung HDDs, I presume that it holds true for other P35 boards and also Hitachi Drives (which are made along side Samsungs in the same factories)

If I recall correctly the solution was to jumper the drive in SATA 150 mode and disable AHCI in BIOS if it had been turned on. I'm not saying this is your problem But it could very be part of it. Its seems to be limited to Samsung drives.

[Felix Aux]

Felix there was a problem with Gigabyte boards and Samsung HDDs, I presume that it holds true for other P35 boards and also Hitachi Drives (which are made along side Samsungs in the same factories)

If I recall correctly the solution was to jumper the drive in SATA 150 mode and disable AHCI in BIOS if it had been turned on. I'm not saying this is your problem But it could very be part of it. Its seems to be limited to Samsung drives.

Do you mean ACPI? (Powermanager)

Didn't find any jumpers for SATA150 mode. Is it on the MB or the HD ?